As an OJS user, I'd like to change the status message that is returned when a DOI is updated and moved from one journal Cite ID to another, as it can help flag potential problems

After some back and forth with Mike Nason at PKP, we both agreed that modifying the logic in our content registration process to flag DOIs using a warning status that are moved from one journal cite ID to another in a submission could help OJS users identify potential metadata problems.

As Mike rightly points out, "Journal articles do not commonly swap publications entirely, and a warning would probably be useful." I agree that this could help avoid problems for OJS users and other members. Sometimes members do make mistakes and register journal articles against the wrong journal, but flagging submissions with a warning would be a good step to alert members to a potential problem.

What

As it stands, when OJS users update a journal title in their settings, it can result in a redeposit/update of all previous journal articles - that should retain the historical journal title and ISSN(s). This can lead those legacy journal articles to have their title-level metadata overwritten. Changing our status message to a warning can help PKP flag this to OJS users as a potential problem.

Why

Alert OJS users and other members to an inadvertent journal-title-level metadata updates.

How urgent

Lower urgency.

Definition of ready

• Product owner: @SaraBowman
• 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
  • Follow up with PKP and respond to issue on Github: https://github.com/pkp/pkp-lib/issues/7527
• 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.

Notes

It would be ideal if all the backfile articles published up to that point could remain associated with the old title/ISSNs on OJS, not just in their Crossref metadata, and the new title/ISSNs would only apply to articles within new issues published from that point going forward.