As a Crossref member, I want to register DOIs for thematic collections of journal articles which are sources from a variety of issues

As a Crossref member, I want to register DOIs for thematic collections of journal articles which are sources from a variety of issues. And I want the relationship between articles and collection to be surfaced in the articles' metadata records.

What

The member who requested this describes their collections as follows.

By article collection I mean a collection of (usually thematically) related articles published (usually) in the same journal but in different volumes/issues. The article collection has its own landing page which would be the URL to which a DOI is resolved.

Why

Journal articles can exist within multiple 'containers' (in this case, both an issue and a collection), but our schema only structurally supports a single hierarchy: journal > issue > article.

Additional Issue DOIs could be registered without volume or issue numbers to refer to the collections, but Issue metadata can't contain relationships, and relationships can't be asserted from an article to an issue DOI (confirmed by @pfeeney).

How urgent

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

Edited by Patricia Feeney