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

Button to verify what is held in Datacite MetaData Store (MDS) against a current GigaDB dataset info #114

Closed
only1chunts opened this issue Jan 19, 2017 · 1 comment

Comments

@only1chunts
Copy link
Member

only1chunts commented Jan 19, 2017

User Story

As a site administrator
I want to be sure that our DataCite metadata is always upto date
So that we always leverage Datacite to its full extent

Given a dataset DOI is registered in DataCite
And I navigate to a dataset page
When I click the "Verify" button
Then a report "showing" the differences between DataCite data and our generated schema is produced

OR (a new idea added Apr2024)

Once a quarter (i.e. every 3months)
An automated script is executed that performs a serial check on all current dataset metadata vs datacite metadata
and reports any differences to the GigaDB curators to investigate and update as required.

Additional information

Note: This assume the "mint button" code is using latest schema

having found an old dataset that at some point got rolled back to an outdated version of author list we need to ensure that all datasets remain correct. One way to do with is to check whats in GigaDB against what we sent to DataCite MDS for minting the DOI.
Also by checking datacite matches GigaDB we can be sure we dont forget to update datacite with any changes we make in GigaDB. @jessesiu is writting this script and adding to the weekly report

This is related to #549

@only1chunts only1chunts changed the title script to check MDS against current GigaDB info Button to verify what is held in Datacite MetaData Store (MDS) against a current GigaDB dataset info Oct 31, 2022
@rija rija added the mint-doi label Mar 11, 2024
@rija
Copy link
Contributor

rija commented Jul 29, 2024

this is not required, so closing

@rija rija closed this as completed Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants