We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.

Bug 7163 - Custom DOI assignment doesn't work with continuous publishing model
Custom DOI assignment doesn't work with continuous publishing model
Status: NEW
Product: OJS
Classification: Unclassified
Component: Submissions and Publishing
All All
: P3 normal
Assigned To: PKP Support
Depends on:
  Show dependency treegraph
Reported: 2012-02-21 09:22 PST by James MacGregor
Modified: 2013-07-16 01:59 PDT (History)
2 users (show)

See Also:
Version Reported In:
Also Affects:


Note You need to log in before you can comment on or make changes to this bug.
Description James MacGregor 2012-02-21 09:22:22 PST
Choosing the "Custom Identifier" option under Setup Step 1.1 in conjunction with "Custom identifiers will be used to identify published items" in Setup Step 4.3 works poorly when the journal publishes continuously, ie. creates and publishes a container issue, and subsequently publishes articles within that issue. 

If the journal is using the "Public ID" (custom identifier) field in the issue's Table of Contents to create the article's DOI, that ID is only used as the DOI when:

-- the issue is published;
-- the "Reassign DOIs" button in Journal Setup Step 1 is pressed. 

If the issue is already published, and the article is scheduled against that issue and given a Public ID, the ID won't be used as the DOI without reassigning all DOIs -- something Editors won't necessarily know how to do, or have access to do, as it is in the JM domain. 

Possible solutions:

1) add "use as DOI" button next to public ID field in Table of Contents which, when pressed, will (re)assign the current Public ID as the DOI (clunky, UI-wise); 
2) maybe add something to the scheduling section in the submission's Editing interface, although I can't possibly see how this would be less clunky than 1); 
3) automatically assign the DOI if the Save button on the ToC page was pressed, and the value for the Public ID previously was null.
Comment 1 Marc Bria 2013-07-16 01:59:27 PDT
Please James, take a look to the last part of this post:

The questions are relevant, at least for us.