As a member of the support team, I'd like a DOI checker that I can run URL updates through to check DOIs and avoid errors
To avoid another major issue like https://gitlab.com/crossref/issues/-/issues/1366, we'd like to create a simple checker that we can run URL update request files through to check that all DOIs in the requested file are:
- already registered with us
- are currently owned by the username who is requesting that update
Paul Davis is working on a prototype. Geoffrey Bilder has offered his help to review/refine.
What
DOI checker for resource resolution URL updates to eliminate manual review of files and errors.
Why
To avoid errors like: https://gitlab.com/crossref/issues/-/issues/1366
How urgent
Depends on #650 (closed), but if that longer-term fix is going to take some time, this issue would be more urgent.
Definition of ready
-
Product owner: @SaraBowman -
Tech lead: @davispj and @gbilder -
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.