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

Not possible to remove/update re3data record DOI in Fabrica #259

Closed
MaryHirsch opened this issue Nov 26, 2019 · 3 comments
Closed

Not possible to remove/update re3data record DOI in Fabrica #259

MaryHirsch opened this issue Nov 26, 2019 · 3 comments
Assignees
Labels

Comments

@MaryHirsch
Copy link

MaryHirsch commented Nov 26, 2019

Expected Behaviour

The re3data record DOI can be removed/updated in Fabrica

Current Behaviour

The re3data record DOI reappears after it has been removed after hitting update DOI.

Steps to Reproduce

See example: https://doi.test.datacite.org/repositories/delft.jrc/settings

Context (Environment)

Fabrica production

Hypothesis

Detailed Description

Possible Implementation

Front logo Front conversations

@MaryHirsch MaryHirsch added the bug label Nov 26, 2019
@mfenner mfenner self-assigned this Nov 26, 2019
@mfenner
Copy link
Contributor

mfenner commented Nov 26, 2019

Issues

  • REST API ignores null value, so re3data_id is never reset.
  • issues with updating re3data because of recent code changes (requiring A and capitalizemethods)

mfenner pushed a commit to datacite/lupo that referenced this issue Nov 26, 2019
@mfenner mfenner closed this as completed Nov 26, 2019
@MaryHirsch MaryHirsch reopened this Nov 27, 2019
@MaryHirsch
Copy link
Author

Thank you but it seems that some further correction is needed. Although in the 'Settings' page at https://doi.test.datacite.org/repositories/delft.jrc/settings the re3data URL is updated correctly, at https://doi.test.datacite.org/repositories/delft.jrc/dois the re3data record that is displayed still corresponds to that of the JRC Data Catalogue.

@mfenner
Copy link
Contributor

mfenner commented Nov 27, 2019

Not an issue with the code, but external re3data API.

@mfenner mfenner closed this as completed Nov 27, 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

2 participants