-
Notifications
You must be signed in to change notification settings - Fork 3
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
Define and implement workflow for updating Datacite DOIs #255
Comments
|
A findable datacite DOI can indeed be updated using the metadata intake form, which as we discovered is fraught with danger because the current DOI metadata and any manual edits are overwritten. |
Here's a draft of the workflow for DOI creation that Tim worked up: |
hmm seems like the 'update a published record' workflow needs some adjustment then. Should an update to a published record require another review? |
Good questions. Just talked about this with the DM crew and 1) no we don't think updating a published record requires another review. Another question we have is whether or not a manually entered DOI can be updated. I can test this. |
A manually entered DOI can not be updated using the metadata intake tool . So, all the records that have DOIs that pasted in after manually creating the DOI using the Hakai Datacite client can not be updated. This is problematic in that it if any changes to records that had DOIs manually created are made, those changes wont be automatically updated in Datacite. We may need a function the check if a manually entered DOI exists in the Hakai Datacite client and if so then it should be updated. DOIs created outside of the Hakai Datacite client can not be updated automatically like this and would require a different manual workflow from the provider to update both at the same time, or have the two metadata records go out of sync. |
Is it not possible to update it on Datacite, or just not via the form? I ask because it could be that we are not storing the doi properly in the form if it's pasted in and that with more info, properly parsed, we could update from the form. |
Its possible to update on Datacite no problem, just not from the Hakai metadata intake form. I agree it probably just needs to be stored differently in the form if it's been pasted into the form manually |
Upon some further reflection I might be leaning more towards auto-updating the DataCite record when saving changes made to a published record. When a record is published in the Hakai Catalogue it'll already have gone through a round of review with Jessy/Brett/myself, and we'll also verify contents in DataCite when we change the status from Draft -> Findable. If people have the option of not updating the DataCite record when saving changes to a published record, don't we run the risk of having the metadata content in the Hakai Catalogue record be different from the metadata content in DataCite (and what if people simply 'forget' to sync the contents eventually?). Auto-updating the DataCite when saving changes in the form keeps the metadata record in the Hakai Catalogue as the single source of truth and keeps it simple? Once a record is published in the catalogue and Findable in DataCite, we can't change it back to 'draft' in the metadata record anymore because this unpublishes the record and breaks the URL? So any changes would have to be made to a published record, where saving changes in the content also gets reflected in CKAN. I would imagine that we'd want to make sure those same changes are then also implemented in DataCite. |
Here's a suggestion that could handle updates to published metadata records and DOI. A metadata record can be in the following stages:
Once a record published, the DOI is also published. Once this stage achieved, a metadata record can be modified via the form and saved locally. This record is then in the modified stage. Any changes to the form can only get reflected to the CKAN record and published when an update button is clicked within the form. We can perhaps implement a check in the form that Here's a diagram to summarize it all: |
#273 present the broader workflow which includes the CKAN record workflow at the same time. |
edit - nevermind, steps already outlined in issue 273. |
I believe this now fully implemented, my only question when is DataCite updated?
|
Right now it's only when the |
|
When the version element is updated by a user, it needs to be updated in DataCite as well as the Hakai Catalogue… How to do this? Can we dynamically update Datacite records automatically?
The text was updated successfully, but these errors were encountered: