Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No way to remove "SeriesInformation" from JSON metadata even when removed from XML #168

Closed
MaryHirsch opened this issue Mar 26, 2019 · 0 comments
Assignees
Labels

Comments

@MaryHirsch
Copy link

MaryHirsch commented Mar 26, 2019

Expected Behaviour
If an item has "SeriesInformation" as a description type in the XML metadata, the value is mapped to the container field in the JSON metadata. If the xml is updated, the corresponding container field is also updated in the JSON metadata.

Steps to Reproduce
Update the xml to remove "SeriesInformation" present in the description
View the JSON metadata, the value remains in the container field in the JSON record
There seems to be no way remove a value in the container field (the v2.0 JSON API doesn't allow you to post to this field).
There should be a way to clear the container field in the JSON metadata.
https://doi.datacite.org/clients/caltech.library/dois/10.26206%2Ft76e-re09

Context (Environment)
REST API/Fabrica

Hypothesis

Detailed Description

Possible Implementation

Front logo Front conversations

@MaryHirsch MaryHirsch transferred this issue from datacite/homepage Mar 26, 2019
@MaryHirsch MaryHirsch changed the title "SeriesInformation" remains in JSON metadata even when removed from XML No way to remove "SeriesInformation" from JSON metadata even when removed from XML Mar 26, 2019
@mfenner mfenner self-assigned this Mar 27, 2019
mfenner pushed a commit to datacite/lupo that referenced this issue Apr 10, 2019
@mfenner mfenner closed this as completed Apr 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants