search

psu-libraries / scholarsphere

Penn State's next generation institutional repository
MIT License
12 stars 6 forks source link

DOI minting for the Data & Code Pathway #1492

Closed EricDurante closed 1 week ago

EricDurante commented 7 months ago

DOI minting is on the work settings page, but it might be nice to have the request for DOI minting be during the deposit process or be displayed as recommended just after publication. We also should require DOIs to be minted by ScholarSphere.

Open Questions:

bdezray commented 6 months ago

I think an ideal set up would be to have data &code pathway users be redirected to the work settings page after successfully publishing and having the DOI field be recommended for this pathway.

ajkiessl commented 1 month ago

WDLL

Another optional field at the final step of the work upload process for a user to opt in to have their DOI minted when published. Similar to the request curation, but in this case there will be a boolean field (maybe a checkbox). This field could be right after the request curation field:

Image

The actual minting of the DOI should not happen until the submission is published. So, if they save it as a draft, the DOI should not be minted yet. Also, as the title of the issue states, this should be for the Data & Code pathway (and soon to include instruments).

Refer to app/controllers/dois_controller.rb to see how DOIs are currently being minted.

bdezray commented 1 week ago

@Smullz622 Here is the help text:

A Digital Object Identifier (DOI) is a unique identifier that ensures your work can be easily cited and reliably located. We recommend minting a DOI unless your work already has one from another publisher or repository.

Note: It may take a few moments for the DOI to be minted after publication. Please refresh the page if it does not appear right away and do not request an additional one.