RSE Wiki Archive

User Tools

Site Tools

Trace:
doi

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
doi [2013/12/25 11:09]
rsewikiadmin 		doi [2014/01/10 18:54] (current)
rsewikiadmin
Line 6: Line 6:
  
  
-Problem Statement:  When documenting authored publications, academic researchers rely on Digital Object Identifiers ([[http://www.doi.org/]]) assigned to their publications.  In order to encourage the reputation and value of the Series to academic researchers, adding DOIs to all published RFCs is being considered as a possibility.  Using DOIs to uniquely identify publications is considered a standard best practice among the scientific, technical, and medical publishing community.+Problem Statement:  When documenting authored publications, researchers often rely on Digital Object Identifiers ([[http://www.doi.org/]]) to find, cite, and report on their publication activity.  In some cases, publications do not count as professional publications if a DOI is not assigned.  In order to encourage the reputation and value of the Series to academic researchers, adding DOIs to all published RFCs is being considered as a possibility.  Using DOIs to uniquely identify publications is considered a standard best practice among the scientific, technical, and medical publishing community.
  
  
Line 12: Line 12:
   * Determine cost and potential value   * Determine cost and potential value
   * Present business case and high level project plan to RSOC   * Present business case and high level project plan to RSOC
 +  * Work with John Levine on DOI draft (see [[http://datatracker.ietf.org/doc/draft-levine-doi/]])
  
  
Line 19: Line 20:
  
 RFC Production Center & Publisher Actions: RFC Production Center & Publisher Actions:
-  * Create project plan+  * Determine what programming will be required 
 +  * Help create project plan
   * Code changes to include information in database, create necessary APIs to register DOI numbers with CrosRef   * Code changes to include information in database, create necessary APIs to register DOI numbers with CrosRef
 +  * Adjust Procedures Manual accordingly
  
  
Line 28: Line 31:
     * "An annual subscription for a non-profit organization is $2,500 per year. This entitles the organization to up to 1 million identifiers per year, both DOIs and ARKs. You would have a unique prefix assigned to your organization"     * "An annual subscription for a non-profit organization is $2,500 per year. This entitles the organization to up to 1 million identifiers per year, both DOIs and ARKs. You would have a unique prefix assigned to your organization"
   * From CrossRef - http://www.crossref.org   * From CrossRef - http://www.crossref.org
-    * Annual membership fee: $275, $1 per RFC for all RFC published between 2011 to present and $.15 per document for earlier works (determined from website; confirmation from vendor in progress)+ 
 +   CrossRef Fees, initial 
 +   Annual Fee = $275 
 +   Deposit Fee (2012-2014) = (610 * 1.00) = $610  
 +   Deposit Fee (pre-2012) = (6491 * .15) = $973.65 
 +   Total est. for of January 1, 2014 = $1913.65 
 +   Ongoing = $330 (annual fee) + $350 (total yearly deposit fee)
  
 While a subscription service is possible for $2500/year, given the number of RFC's published (approx 350/year) a per document service like CrossRef.org makes more sense for the Series. While a subscription service is possible for $2500/year, given the number of RFC's published (approx 350/year) a per document service like CrossRef.org makes more sense for the Series.
doi.1387998551.txt.gz · Last modified: 2013/12/25 11:09 by rsewikiadmin

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki