As a service provider, I'd like improved ways to find my submissions (mostly in troubleshooting submission errors with Crossref support)

Atypon has asked us if we can either include:

  • the BatchID and/or filename (generated from their system) in the search area of the Administration area of doi.crossref.org (note: this has been proposed to support by other members who do not use notification callbacks, so this change has the potential to accommodate more members)

OR

  • the submissionId somewhere in the API HTTP response of the notification callback

Why

Identifying submission IDs so that support can assist in troubleshooting submission problems is a complication for most of our service providers.

How urgent

Low urgency.

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
    • Respond to and close Zendesk 393394
    • 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.

Notes