As a Crossref Member who registers Datasets, I want to supply checksums and checksum generator information in their metadata records
As a Crossref Member who registers Datasets, I want to supply checksums and checksum generator information in their metadata records
What
A member contacted us with this suggestion.
From my point of view it would be very helpful if a checksum could be stored in the XML schema, together with the indication which checksum generator was used. It could be in the custom_metadata which located in the crossmark container. By this any user could check if the used data has not been changed in respect to the published data. As there are several hash algorithm (like MD5, SHA256,...) available one would also need to add the name of the has algorithm.
Why
As a means to ensure data integrity
How urgent
Definition of ready
-
Product owner: -
Tech lead: -
Service:: or C:: label applied -
Definition of done updated -
Acceptance testing plan: -
Weight applied
Definition of done
-
Unit tests identified, implemented, and passing -
SONAR on merge request branch checked by tech lead -
SONAR on merge request branch checked by reviewer -
Code reviewed -
Available for acceptance testing via a staging URL, or otherwise -
Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed -
Knowledge base reviewed and updated -
Public documentation reviewed and updated -
Acceptance criteria met -
AC 1 -
AC 2
-
-
Acceptance testing passed -
Deployed to production
Prior to and during Backlog Refinement, consider the potential impacts this user story may have on the following areas:
- Billing/costs
- Internal documentation
- External documentation
- Schema
- Outputs
- Operations
- Support & Membership experience
- Outreach & Communications
- Testing
- Internationalization
- Accessibility
- Metrics, analytics, reporting
Additional details about the above items can be found here.