Skip to content

[Implementation] Different DOIs for different article versions #10553

@bozana

Description

@bozana

The DOI backend allows assignment of different DOIs to different article versions. This option currently only exists in OPS. For the project OSS ORE an assignment of different DOIs to different article versions is needed also in OJS.

The decisions made:
All JAV will get a DOI, so that preprints can get a DOI.
The minor versions in the same version stage and same version major will have one and the same DOI. This requires changes in the current code.

Only current publication is displayed in submission listing on the DOI management page (as it was till now). The link 'View all' opens a modal where the last minor version for all major versions will be listed. This is slightly different as till now (in OPS, where all versions are listed and all versions get a DOI).
We cannot display all versions i.e. also all minor versions, because each version can be edited, which could lead in wrongly editing minor versions (so that it could happen that they have different DOIs) i.e. we would need to consider this logic also in the edit function in UI (so that when editing a minor version all sibling minor version would be edited in the same way). This is a bigger task (for me) and I think does not need to be implemented right now.

Tasks to do:

  • Add setting for a journal to define if each article version will get a new DOI
  • Consider it on the DOI management page
  • Consider it for display on the article landing page. If a minor version does not have a DOI, we check if there is a sibling minor version, to display the DOI from there, because all minor versions (of a submission and with the same version stage and major) have the same DOI. This is considered also for chapters, but not for galleys, publication formats and files, because it is not possible to find out the sibling minor version of them. Currently we do not display DOIs for galley and files, and DOIs for these object types are not much used.
  • [ ] Consider it in native import export plugin -- The DOIs will be exported for publications (and other objects) that have a DOI in the DB. Differently to the DOI display on the landing page, if a minor version do not have a DOI, it will not be searched for a DOI of a sibling minor version for export/import.

PR:

s. comment regarding development notes: #10553 (comment)

Fix marking DOIs stale:

Another fix marking DOIs stale:

Sub-issues

Metadata

Metadata

Labels

No labels
No labels

Projects

Status

Ready for Testing

Status

QA in progress

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions