Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
doi [2025-07-11 05:15] – [The mechanics of registering a new DOI with crossref membership] kate.richdoi [2025-09-28 08:19] (current) – [partial automation] nik
Line 42: Line 42:
  
 ====metadata schema==== ====metadata schema====
 +  * [[https://www.crossref.org/documentation/schema-library/|Crossref schema library]]
   * [[https://www.medra.org/schema/onix/DOIMetadata/2.0/ONIX_DOIMetadata_2.0.xsd|ONIX for DOI Metadata Schema v2.0]]   * [[https://www.medra.org/schema/onix/DOIMetadata/2.0/ONIX_DOIMetadata_2.0.xsd|ONIX for DOI Metadata Schema v2.0]]
  
 ====generating DOIs==== ====generating DOIs====
-  * https://datacite.org/blog/cool-dois/+ 
 +The [[https://github.com/datacite/cirneco|cireno]] tool can be used to generate & validate DOIs 
 + 
 +via https://datacite.org/blog/cool-dois/ 
 + 
 +  * opaque without semantic information 
 +  * work well in a web environment, avoiding characters problematic in URLs 
 +  * short and human-readable 
 +  * Resistant to transcription errors 
 +  * easy to generate 
 + 
 +valid suffixes match ''/^10.d{4,9}/[-._;()/:A-Z0-9]+$/i'' 
 + 
 +====partial automation==== 
 +  * https://juliapackages.com/p/pitaya 
 +  * https://github.com/fabiobatalha/crossrefapi 
 +  * https://github.com/prsull/CrossrefTutorial
  
 ====The mechanics of registering a new DOI with crossref membership==== ====The mechanics of registering a new DOI with crossref membership====
Line 55: Line 72:
   * Suffixes must be unique, contain numbers and/or letters and -._;()/ are case-insensitive and ideally are short string, easily typed yet “dumb” meaning that they contain no obvious information. A best practice DOI would be 10.3390/s18020479   * Suffixes must be unique, contain numbers and/or letters and -._;()/ are case-insensitive and ideally are short string, easily typed yet “dumb” meaning that they contain no obvious information. A best practice DOI would be 10.3390/s18020479
   * On submitting the form, you are asked for your crossref login, and an email address where the deposit results should be sent.   * On submitting the form, you are asked for your crossref login, and an email address where the deposit results should be sent.
-  * Once the DOI is confirmed you then create a landing page for the DOI. It's usually enough to add the DOI information (title, author and https:// DOI URL as an html link) at the top of the page of the referenced object, however if the item is a PDF it's advised to make a separate page.+  * A DOI string can’t be changed once registered, and DOIs cannot be deleted. 
 +  * Once the DOI is confirmed you then create a landing page for the DOI.  
 +  * For the landing page it's usually enough to add the DOI information (title, author and/ DOI URL as an html link) at the top of the page of the referenced object, however if the item is a PDF it's advised to make a separate page.
   * You also receive a copy of the xml. If changes need to be made to your metadata record, you can edit and submit the XML instead of re-entering your metadata into the form.   * You also receive a copy of the xml. If changes need to be made to your metadata record, you can edit and submit the XML instead of re-entering your metadata into the form.
- +  * Other metadata that might be added include funding an license metadata 
 +  * To add, change, or remove metadata from your existing records, you generally just resubmit your complete metadata record with the changes included. 
 +  * You can add funding and license metadata to multiple DOIs at once by uploading a csv file to the web deposit form using the supplemental metadata upload on crossref site. 
 + 
  
  

User Tools

Page Tools

Site Tools