Show 'Accepted' if DOI is registered with conflict in Metadata Manager
What
If a DOI is registered with a conflict in Metadata Manager, the status in the journal workspace and in the Deposit History should say 'Accepted'
Why
Currently, if a DOI is registered with a conflict in Metadata Manager, the status on the journal workspace and the Deposit History say 'failed,' even though the DOI has been registered. Users see 'failed,' assume the records were not registered, and create more DOIs in conflict. This generates lots of cases for the Support team to untangle:
Members cannot resolve conflicts in MM; they need to do so in the Admin tool. They will receive a conflict report to alert them of the conflict.
How urgent
As soon as possible. Support is overburdened and MM produces a disproportionate number of cases for them to manage.
Definition of ready
-
Product owner: @SaraBowman -
Tech lead: @myalter -
Service:: label applied -
Definition of done updated -
Acceptance testing plan: staging MM (crossref.org/mmstaging) -
Weight applied
Definition of done
-
Unit tests identified, implemented, and passing -
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 -
If a DOI is registered in conflict in MM, the Journal workspace should indicate the status is Accepted. -
If a DOI is registered in conflict in MM, the Deposit History should indicate the status is Accepted, but continue to display the warning icon with the alert that the DOI was registered in conflict.
-
-
Acceptance testing passed -
Deployed to production
Notes
Edited by Patrick Polischuk