sfu.ca
Home/PKP Hannover Sprint Notes Released: Stamping journal & press identity metadata on article publications
  • News, News for Developers, News for Hosted Clients

PKP Hannover Sprint Notes Released: Stamping journal & press identity metadata on article publications

By PKP Hannover Sprint Working Group "Stamping journal & press identity metadata on article publications" / PKP Communications

The sprint notes from the PKP Hannover Sprint, hosted by the Leibniz Information Centre for Science and Technology in September 2023 are now available.

PKP HANNOVER 2023 SPRINT NOTES RELEASED: Stamping journal & press identity metadata on article publications The picture shows three participants of the "Stamping journal & press identity metadata on article publications" working group at the PKP Sprint Hannover 2023. The blog post is a summary of the work of this group.

Sprints involve PKP community members joining diverse groups to work on PKP software and support. The Leibniz Information Centre for Science and Technology (TIB) hosted six working groups at the PKP Hannover Sprint in September. This is a summary of one such group’s work.

Group members 

  • Antti-Jussi Nygård, The Federation of Finnish Learned Societies
  • Nils Stefan Weiher, University Library Heidelberg
  • Bozana Bokan, Public Knowledge Project
  • Tom Granroth, The Federation of Finnish Learned Societies
  • Jesper Boserup Thestrup, Royal Danish Library
  • Christian Marsilius, University Library Heidelberg
  • Radek Gomola, Masaryk University Press

Background

Currently, the PKP applications fetch journal/press/server identity metadata from the current context settings when showing metadata for a single submission. This causes a problem if the identity metadata, for example, ISSN and Journal title, is changed because the change will affect the metadata of all published publications. Also, if old publications with different identity metadata are imported into the system, there is no way of using the old versions of the Journal title and ISSN in the metadata. This leads to a situation where PKP applications are creating bad metadata.

Existing issues:

Goals

To fix the issue with bad metadata we need to make the context identity metadata (i.e., journal title, ISSN, publisher) part of the publication metadata and have a process where this data is stamped to the publication object and fetched without using data directly from the context settings.

This group will

  • Consider what metadata needs to be taken into account and document the requirements.
  • Consider what areas in the applications need to be changed.
  • Consider how the change affects how the applications interact with other services and how plugins use data.
  • Deliver guidance/documentation for journals on how to proceed when changing the title or ISSN and what the user needs to consider.

Results

Stamping data to publications and issues workflow

  • When the submission is made and the publication is created (ensures that the data we rely on is there and things like citation plugin in article preview works)
  • Again, when the submission is published for the first time (to make sure the current journal name and ISSN are used if the name has changed during the editorial process)
  • If a submission has been published before, unpublished, edited, and published again, we keep the existing journal name and ISSN. Possibly can use the publication date field to check if
    • Context identity metadata is stamped when submission/publication is created using the current context metadata
    • Context identity metadata is stamped when the issue is created using the current context metadata
    • When the issue is published, the context identity metadata is stamped to publications using the current context metadata
    • When the issue is published, the context identity metadata is stamped to the issue using the current context metadata
    • If an issue or submission is unpublished and published again, we do not restamp the current identity metadata

Extending schemas: publication and issue schema, native XML DTD

Draft the migration process 

Draft the command line tool for batch stamping 

Research and use cases & documentation 

  • Describe UI for making the title and ISSN change a two-step process
    • During setup: 

The editor should be informed to apply for an ISSN number if the journal does not have an ISSN. This should not require any action of the system administrator. However, the editor should be informed that if the journal has changed the title and ISSN over time (see the case of Landbohistorisk Tidsskrift), the editor must contact the admin to ensure the journal is set up correctly. 

Suggestion for text: “ You need to add an ISSN number. If your journal does not have an ISSN number, you need to register the journal at the ISSN office. Please visit the ISSN Portal (provided by ISSN International Centre): https://portal.issn.org/ for more information about ISSN. An ISSN (International Standard Serial Number) is an international number system used to identify publications. If your journal has changed its title or ISSN number since its first publication, please contact the admin who will help you to set the journal correctly. Please describe these changes in the “About the Journal” field in the journal setup”.

  • After setup:

If the editor starts to change the title and/or the ISSN, the editor has to contact the system administrator. The editor must be informed about the problems this will create for the journal and that the admin must handle the changes. And that the editor/publisher must contact the local ISSN office in order to register the changes. Contact the publisher of your journal to get more information about the National ISSN Center.

Suggestion for text: “You seem to be changing the title of the journal and/or the ISSN number. This can create problems for the correct indexing of the journal in search engines, databases and with persistent identifiers like DOI’s. Contact your publisher, who must contact the local ISSN office in order to register the changes. Contact the system administrator who will help you to set the journal correctly. Please describe these changes in the “About the Journal” field in the journal setup”. 

  • Workflow with Crossref
    • The name of the journal is connected with ISSN. When you start using a parallel name with your ISSN (if you change the journal title, but keep the ISSN), you should get an error during DOI registration “The ISSN is used by another journal”. You can ask Crossref support to update your journal-title and/or use the Crossref Metadata Manager (only for journals) to update the name of the journal by yourself: https://www.crossref.org/metadatamanager. If it is changed on the journal level this will affect all registered DOI under its ISSN. When you change the journal title and ISSN it is for Crossref a new journal.

Research and use cases

Other questions to consider

Changes to context settings handling

  • Possibly have a warning when the journal is trying to change journal name / ISSN kind of fields to make sure they understand the implications
    • UI?

Documentation needed:

  • Good practices of changing your journal name and ISSN, what are the consequences when you do it, and who needs to be informed
    • When you are changing the name you have to register the new title in the National ISSN center for your country
    • You could add a parallel title for your journal without any consequences
    • When you want to add a co-publisher, you have to contact your National ISSn center to do that, you can even change the main publisher without any problems
    • When you are changing the publisher, which is in a different country, the National ISSN center postpones the ISSN to the National ISSN center of the new publisher country
    • When you change the journal name and then get a new ISSN you can keep the history in your national ISSN center systems: https://issn.techlib.cz/Record/000014478 (Klinická Psychologie a osobnost -> Annales psychologici)
  • Note: PKP Docs Hub’s Journal Policies and Workflows guide has a section on best practices when journal title, ISSN, or abbreviation changes 

Services to consider:

  • Crossref
    • The title of the journal is registered with DOI, it throws an error when you change the name in XML. You have to change the journal title through metadata manager: https://www.crossref.org/metadatamanager/ 
  • Datacite
  • DOAJ
  • mEDRA
  • vgWort (Germany specific)
  • Scopus
    • With the new ISSN, you have to go through a new evaluation process

Check also:

  • OAI (Metadata plugins)
  • GoogleScholar
  • DC Plugin (Meta Tags in HTML Landing Page)
  • Citations
  • DNB Plugin (German National Library Archiving)
  • CSL (CitationStyles) Plugin
  • RSS/Webfeed Plugin
  • API
  • Sushi API

Special considerations for OMP

  • Should we stamp the series name and ISSN also in OMP for the book series. If we did not, would there be problems, e.g. how data is used in PKP-LIB?

Overview of the code

References of press name in OMP
(stable_3-4-0, commit 4d37d1bed124d8e090a80960d90023eed9193ac6)

\APP\submission\Submission::_getContextLicenseFieldValue

\APP\search\MonographSearch

\APP\plugins\generic\dublinCoreMeta\DublinCoreMetaPlugin::monographView

\APP\plugins\generic\googleScholar\GoogleScholarPlugin::monographView

\APP\plugins\metadata\dc11\filter\Dc11SchemaPublicationFormatAdapter::extractMetadataFromDataObject
References in OJS and pkp-lib

 (OJS/main, pkp-lib/main) Results

Next Steps

  1. Contact some central service providers and find out how these changes affect their systems (i.e…. Crossref, DOAJ, Datacite, etc.).
  2. Decide which release we are aiming for.
  3. Christian Marsilius will work on implementation after the current projects are finished.
  4. Inform plugin maintainers: write release notes describing the technical changes & point to the issue
  5. Enjoy