You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DOI Plugin's main benefit, in practice, was that it would auto-populate the DOI so depositors knew what their DOI would be once the dataset was approved and could copy it for whatever purpose. The plugin was creating other problems, so I requested it be removed (#2686). Since DataCite DOIs follow a standard pattern, Research Data Services would like to have the assigned DOI be auto-populated directly by ScholarsArchive when someone first deposits a dataset.
Details
The pattern for DataCite DOIs is https://doi.org/10.7267/{pid}.
This feature is only available on Datasets.
When the depositor is creating their Dataset record, they would select one of three options:
"Automatically assign a DOI for this dataset." --> Will create a DOI value with the pattern above plus the PID that is generated when the record is saved.
Include help text: "Your DOI will be available after you submit. While this DOI won't change, it will not be active until the dataset is approved."
"This dataset has an existing DOI." --> The depositor enters a DOI in the text field.
"Decline DOI: This dataset will not be assigned a DOI." --> No value for the field.
If possible, ideally the above options would only be available when first submitting a dataset. Subsequently when editing, the DOI field would appear as normal.
Either way, curators/admins must be able to edit or delete the DOI after the record has been initially saved.
If automatically assigning a DOI, the deposit notification email includes the DOI.
This feature DOES NOT interact with DataCite (curators will create DataCite records manually).
Related work
#2686 -- Conflicts with existing DOI plugin so this work can't be done until the plugin is removed. #2286 -- Could the pertinent pieces of code be borrowed from the DOI Plugin?
The text was updated successfully, but these errors were encountered:
Descriptive summary
The DOI Plugin's main benefit, in practice, was that it would auto-populate the DOI so depositors knew what their DOI would be once the dataset was approved and could copy it for whatever purpose. The plugin was creating other problems, so I requested it be removed (#2686). Since DataCite DOIs follow a standard pattern, Research Data Services would like to have the assigned DOI be auto-populated directly by ScholarsArchive when someone first deposits a dataset.
Details
https://doi.org/10.7267/{pid}
.Related work
#2686 -- Conflicts with existing DOI plugin so this work can't be done until the plugin is removed.
#2286 -- Could the pertinent pieces of code be borrowed from the DOI Plugin?
The text was updated successfully, but these errors were encountered: