Lighton,

We are working on a contribution to DSpace 3.0 that includes functionality
to assign external identifiers such as DOI in DSpace.  This is based on
work at @mire did with NESCent on Dryad,  but also on some funded
contribution work that is also happening this summer with WHOI to improve
the contribution.  Our current situation with DOI integration is that you
will need to be registered with an RA.  For Dryad, that provider was
originally Datacite, but now is EZID. The API used in this situation is
novel and unstandardized, each situation we've encountered required custom
coding in DSpace, thus what is being contributed is specifically designed
to support customizable ID providers on the backend.

You will find that the Handle RA is significantly more cost effective than
any of the existing DOI RA, this is one of the original intents of using
the Handle platform for repositories, where costs are a significant
concern.  What you are getting with those additional DOI costs are
additional services being matketed by those various RA providers, 1.
someone else's guarantee for the resolution records in a centralized
registry rather than their resolution being dependent on internal calls
back to your DSpace server, 2. Metadata/citation registration, linked data
exposure, 3. Automatic indexing of your items into aggregated catologs, and
so on.  Unless you have a really critical need to integrate based on
policies or decisions that were made in your organization, I would wiegh
the overall cost benefits before getting yourselves vested in having to
maintain DOI on your repository items.  Consider that Handles are not only
the more cost effective route, they are supported "out of the box" on your
current DSpace release.

So there are important management questions independent of implementing DOI
that you will need to answer first. We don't necessarily perceive DOI as
being technically any better than Handles or other identifier systems at
this moment, just much more marketed by SaaS providers.  Thus our intent
for future DSpace PID support is that it be extensible and plural in
nature.  I would start with Handles given the low cost of entry, then
consider adding DOI after a longer "needs analysis" on what benefits DOI
will bring to your repository.

Mark



On Sunday, July 15, 2012, Lighton Phiri wrote:

> We are at a stage where we would like to integrate a DSpace instance
> with persistent identifiers and would want to make use of DOIs. I
> would like to find out if there is anyone who has had luck doing this,
> just so we know if going the Handle System route may be the only
> viable option.
>
> I should mention here that other than this relatively old forum post
> [1], I haven't found anything comprehensive on the wiki pages or
> online.
>
> [1] https://sourceforge.net/mailarchive/message.php?msg_id=28698555
>
> Lighton Phiri
> http://lightonphiri.org
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>


-- 
[image: @mire Inc.]
*Mark Diggory *(Schedule a Meeting <https://tungle.me/markdiggory>)
*2888 Loker Avenue East, Suite 305, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee 3001, Belgium*
http://www.atmire.com
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to