Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOI minting for the Data & Code Pathway #1492

Open
EricDurante opened this issue Feb 19, 2024 · 2 comments · May be fixed by #1584
Open

DOI minting for the Data & Code Pathway #1492

EricDurante opened this issue Feb 19, 2024 · 2 comments · May be fixed by #1584
Assignees
Labels
incomplete Needs additional information to be actionable

Comments

@EricDurante
Copy link
Collaborator

EricDurante commented Feb 19, 2024

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:

  • How exactly should this behave?
@EricDurante EricDurante added the incomplete Needs additional information to be actionable label Feb 19, 2024
@bdezray
Copy link

bdezray commented Mar 14, 2024

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
Copy link
Contributor

ajkiessl commented Sep 4, 2024

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.

@Smullz622 Smullz622 self-assigned this Sep 9, 2024
@Smullz622 Smullz622 linked a pull request Sep 12, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
incomplete Needs additional information to be actionable
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants