As a Crossref member I want to expand Pending Pub so that it applies to all types of content

As a Crossref member I want to expand Pending Pub so that it applies to all types of content.

Currently, standalone works, which do not have a parent publication are not supported. For example, reports which are not part of a report series and dissertations. What

The current version of the schema for pending_pub has <publication> as a required element, and within the parent publication's <issn>, <isbn>, and/or <doi> is required.

In practice, this means that works without a parent publication cannot be registered.

Member USDA would like to use pending pub for their reports, but because the reports are not part of a report series, they cannot do so.

Registering a placeholder series-level DOI for their reports is not a suitable workaround, because the schema also requires an ISSN for report series.

The same would be true for dissertations. Theoretically, it would also apply to books and conference proceedings that are not part of book or conference series, as they don't have parent publications either. But, as a workaround, you could basically assert that the book is its own parent by adding its ISBN into the <publication> tag in the pending pub metadata.

Why

To make the benefits of Pending Pub registration available to all members.

How urgent

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
    • 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 Patrick Polischuk