LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  April 2011

CODE4LIB April 2011

Subject:

Re: DOI's for bioinformatic/bioscience

From:

Jonathan Rochkind <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Wed, 13 Apr 2011 13:20:06 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (111 lines)

So, yeah, I learned a little bit about this recently, the overall DOI 
environment is a bit confusing to understand exactly what the options 
and trade-offs are.

So there are various DOI top-level registrars that can register DOIs. (I 
don't know if "registrar" is actually the name DOI uses for em, it's 
what I'm calling them).

For scholarly publications, CrossRef is the one that's typically used.  
But to register a DOI through CrossRef, a "publisher" needs to have a 
relationship/membership with CrossRef, which has some non-trivial 
expenses and obligations (such as being _required_ by CrossRef to look 
up DOIs for any works cited in the published work, and include those in 
the published work).  And I'm not entirely sure what tools CrossRef 
gives you for managing your DOIs.

I am not sure how an individual dude who wants a few DOIs would best go 
about getting them through CrossRef, might be worth asking CrossRef is 
there is any feasible way to do this.

Any DOI registration through any registrar will get DOI forwarding 
resolution. That is, for instance, http request to 
http://dx.doi.org/something gets redirected to your destination URL.  
Any DOI through any registrar gets this.

When you register a DOI through CrossRef, you also get a 'metadata 
lookup' service, where a person or machine armed with a DOI can look up 
article metadata such as author, title, journal, etc., from a CrossRef 
service. This is not part of the central DOI architecture, but something 
through CrossRef.  Some library-sector software (such as SFX) is set up 
to do these metadata lookups from CrossRef on any DOI -- if the DOI 
wasn't registered through CrossRef, they won't get any info back.

Now, in addition to CrossRef, there are some other registrars.  One I 
know about is DateCite.  And as Keven mentions, the EZID service is a 
pretty slick front-end that allows you to register and maintain DateCite 
DOIs.  While DataCite was set up for assigning DOIs to data sets,  as 
far as I know nothing in any policies (of DOI foundation, DataCite, or 
EZID) prevents you from using DateCite DOIs in general or EZID-managed 
DataCite DOIs in particular for any kind of information resource you 
want, including scholarly articles, or whatever.

EZID may still be free at the moment in it's testing phase, but 
eventually, I am told by EZID, that there WILL be a cost charged.  
However, I think the cost model, tools provided, and obligatory 
requirements (none) of EZID/DataCite compared to CrossRef may be more 
amenable/feasible for a small project.

However, using EZID/DataCite you won't get the CrossRef metadata lookup 
that some library-sector applications (like SFX) use.  DataCite is, I 
hear, planning on adding their own metadata lookup service. But the 
library applications will still only be using the CrossRef one unless 
they are updated, and the DataCite one may use an entirely different 
data schema/vocabulary than CrossRef -- this metadata lookup thing is 
not something actually standardized for DOI in general, in terms of 
either API or response schema. Or discovering a metadata lookup service 
to use for a given DOI. (I tend to think DOI probably ought to work on 
some standardization and auto-discovery here, personally. ).



On 4/13/2011 11:57 AM, Kevin S. Clarke wrote:
> On Wed, Apr 13, 2011 at 10:56 AM, Rick Johnson<[log in to unmask]>  wrote:
>
>>   We have a professor here who would like to create DOI's for some digital objects related to bioinformatics/bioscience with doi.org.   Has anyone had experience with the process of registering DOI's and what is involved in the process of maintaining/updating DOI information if necessary?
> Hi,
>
> I work on the Dryad data repository [1] which registers DOIs for data
> packages (from the biosciences even).  We register our DOIs through
> DataCite [2] and CDL's EZID service [3].  It's built into our workflow
> so that we mint a DOI on submission and then register it with DataCite
> (via EZID) after curation and acceptance.  CDL's EZID service provides
> us with a web service through which we can programmatically register
> our DOIs (it allows minting, too, but we do this internally).
>
> This same interface can be used update/maintain DOI information (what
> the DOI resolves to and the related DataCite metadata set).  In
> addition to the Web service interface, EZID also offers a plain Web
> interface as well that a person can use to register/update/maintain
> the minted DOIs.  DOIs for data packages registered through DataCite
> are resolvable via dx.doi.org (though we've found there is a slight
> delay).  I don't know the details about the fee for using EZID (or
> doi.org for that matter) -- basically, I can answer more questions
> about the technical end, but the administrative end is out of my range
> of experience.
>
> But, my first thought is: "Are the digital objects the professor wants
> a DOI for associated with a publication?"  If so, Dryad might be a
> good place for him/her to deposit the data (fwiw, we take other
> artifacts related to the raw data as a complete "data package" -- so,
> for instance, R code used to manipulate the data).  Depositing the
> data into Dryad would give him/her a DOI that can be used to reference
> the data in future publications.  It also generates a larger pool of
> bioscience data, rather than a lot of smaller pools (which have to be
> searched across).
>
> The caveats are that Dryad only takes data associated with a
> publication and that we're a repository for the biosciences (but that
> doesn't sound like a problem in this case).  I guess the other would
> be anything deposited into Dryad is released using a Creative Commons
> Zero waiver (I don't know if that would be a problem for this
> particular user or not, but it shouldn't be -- yay, Open Data).
>
> Hope that helps,
> Kevin
>
>
> [1] http://datadryad.org/
> [2] http://datacite.org/
> [3] http://n2t.net/ezid
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager