As a Crossref support and membership team member, I'd like a clearer method within Metadata Manager to indicate that a member has been suspended

comment: # When a member is suspended and that member, after suspension, attempts to use Metadata Manager, they are logged out of the tool or receive 500 errors when they attempt to save and deposit articles using their account. Often times the individuals working with the tool are unaware of the account status and are confused by the continual loop of being logged out (or, receiving 500 errors). We'd like to provide a clearer process for alerting users that the account they are using is suspended (or, does not have the correct privileges to accomplish the task in the tool).

What

comment: # A method of alerting MM users that their account has been suspended in the interface.

Why

comment: # Confusion from members and toil for the support and membership teams. Also, a clearer notification process within the tool could help us get suspended accounts paid, since often times the individual doing the registering is disconnected (yet, motivated) from invoicing of their account.

How urgent

comment: # Middle of the road. Quite a lot of toil/confusion currently.

Definition of ready

  • Product owner: @SaraBowman
  • Tech lead:
  • Service:: 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

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

Edited by Patrick Polischuk