Uploaded image for project: 'ERM Platform'
  1. ERM Platform
  2. ERM-1649

Strictly enforce ISSN and ISBN vs eISSN/pISSN and eISBN/pISBN

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      ERM Sprint 120, ERM Sprint 121, ERM Sprint 122
    • Development Team:
      ERM
    • Release:
      R3 2021

      Description

      Currently we allow the assertion of identifiers in the eISSN and eISBN namespaces. However, these are not real identifier namespaces but rather shorthand labels for identifiers in the ISSN and ISBN namespaces which are used to identify electronic versions of resources.

      Example: The journal "Acta Anaesthesiologica Scandinavica" has an ISSN for the print edition of "0001-5172" and an ISSN for the electronic edition of "1399-6576"

      Since we store the medium (i.e. Print vs Electronic) in the titleInstance subType property, when a resource is added to the internal KB, if an ISSN or ISBN is stated we try to correctly assign to a titleInstance with the appropriate subType. For example using the package import JSON:

       

      {
        "header": {
          "dataSchema": {
            "name": "mod-agreements-package",
            "version": 1
          }
        },
        "records": [
          {
            "contentItems": [
              {
                "coverage": [
                  {
                    "startDate": "2003-01-01",
                    "startIssue": "1",
                    "startVolume": "1"
                  }
                ],
                "depth": "fulltext",
                "platformTitleInstance": {
                  "platform": "SpringerLink",
                  "platformUrl": "https://link.springer.com/",
                  "titleInstance": {
                    "identifiers": [
                      {
                        "namespace": "eissn",
                        "value": "1614-2411"
                      }
                    ],
                    "name": "4OR",
                    "publicationType": "Journal",
                    "subType": "electronic",
                    "type": "Serial"
                  },
                  "url": "https://link.springer.com/journal/volumesAndIssues/10288"
                }
              }
            ],
            "name": "Springer Nature DEAL: E-Journals | ZBW-1-SND",
            "packageProvider": {
              "name": "Springer Nature"
            },
            "reference": "zbw-1-snd",
            "source": "EZB",
            "trustedSourceTI": "true"
          }
        ]
      }
      

      The presence of an identifier in the "eissn" namespace here is correctly interpreted as "the issn for the titleInstance with subtype == "Electronic"

      However we don't currently stop the use of the namespaces eISSN, pISSN, eISBN, pISBN.

      To prevent these namespaces being used in the future we should ensure that

      • We do not allow the creation of identifiers in the eISSN, pISSN, eISBN or pISBN namespaces (upper or lowercase versions of these namespaces)
      • On data import
        • eISSN should always be interpreted as "issn for titleInstance with subType == "electronic"
        • pISSN should always be interpreted as "issn for titleInstance with subType == "print"
        • eISBN should always be interpreted as "isbn for titleInstance with subType == "electronic"
        • pISBN should always be interpreted as "isbn for titleInstance with subType == "print"

       

       

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                ostephens Owen Stephens
                Reporter:
                ostephens Owen Stephens
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases