As a member of the support team, I'd like to run the bulk title update tool

As part of issues#1492 (closed), we included in the AC: 'Support team can run Bulk update tool', but the example in that ticket proved to be less straightforward than we would have liked, which has required @jonmstark and support to rethink this request. We all felt that breaking that AC into its own ticket was the preferred next step.

In issues#1492 (closed), the service provider gave us a list of chapter-level DOIs and their 13-digit ISBNs. Complications arose because the only ISBNs that were previously registered for these chapter-level DOIs were 10-digit ISBNs, which, coupled with the fact that these DOIs were originally inadvertently registered as chapters, required Jon to tweak the logic of his existing tool. Given that in the last several uses of this tool that members provided us with a variety of inputs (e.g., chapter-level DOIs and 10-digit ISBNs), we thought a dedicated ticket in order here.

What

A bulk title update tool that the support team can use themselves.

Why

Members make mistakes and register incorrect titles or incorrect metadata in their titles that need to be updated. This tool will have the most utility for book title updates. Like in example issues#1492 (closed), a bulk title update of that magnitude would require hours and hours of manual work by the support team to correct.

How urgent

Moderate urgency. Remove toil.

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.

Notes