As a Crossref member I want ISSNs to be optional, rather than required, in series_metadata
As a Crossref member I want ISSNs to be optional, rather than required, in series_metadata What
User feedback from a member Lund University Library:
Are there any plans to change the requirement of ISSNs for book series? The Swedish National Library do not give ISSNs to book series since many years back.
Why
They're going to register the books within their series as standalone books. They would like to register them as books within a series, but cannot do so because their series do not have ISSNs. They would be fine with registering a series-level DOI to server in lieu of the ISSN.
We've heard from other members in similar situations as well.
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.