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  February 2016

CODE4LIB February 2016

Subject:

Re: Strategy for assigning DOIs?

From:

"Han, Yan - (yhan)" <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Tue, 9 Feb 2016 19:48:02 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (32 lines)

Hi, Jason,

I strongly suggest to separate your DOI namespace/naming schema to be totally independent of your choice of repository/system. DOI is an infrastructure thing, and the main reason behind of assigning DOI is for persistency and permanency. At some point any repository system will go away and will be replaced by another one. 

Secondly I do not think data is a good namespace. I suggest to have something persistent which can standalone even you do not have DOI prefix of 10.17348. 

Yan





On 2/9/16, 11:56 AM, "Code for Libraries on behalf of Jason Best" <[log in to unmask] on behalf of [log in to unmask]> wrote:

>We recently started assigning DOIs to articles published in one of our journals using Open Journal System which generates the DOI and metadata within a namespace dedicated to that journal. We don’t yet have an institutional repository, but are moving in that direction and I hope we have one in a couple of years. But in the meantime, how could we go about issuing DOIs for items that aren’t related to the journal, but that we’d hope to eventually have handled by our IR? For example, we have a handful of datasets for which we’d like to issue DOIs so I planned on created a “data” namespace then just adding a serial number for each dataset (e.g. 10.17348/data.000001 ) which would resolve to a page (with metadata and download links) in our Drupal CMS until we get an IR. Will such an approach allow us to eventually use an IR to 1) become the repository for the items with DOIs previously issued in the “data” namespace and 2) continue issuing DOIs for new items within!
>  the “data” namespace? I know the answer is going to depend on the IR platform we use, so I’m asking this in the broad sense to get your input about your experiences. 
>
>But since DSpace is one of the likely candidates for our IR, I’ll use it as a more concrete example. From my limited understanding (just reading the documentation), items deposited in a DSpace instance will all share the same DOI namespace. The namespace and an internal identifier are then concatenated with the DOI prefix to create the DOI. If we’ve already issued a DOI outside of DSpace, would we have any control over the identifier that was assigned to a newly-deposited item allowing us to control the DOI that is generated?
>
>Any thoughts or suggestions?
>
>Thanks,
>Jason
>
>Jason Best
>Biodiversity Informatician
>Botanical Research Institute of Texas
>1700 University Drive
>Fort Worth, Texas 76107
>
>817-332-4441 ext. 230
>http://www.brit.org

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

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