New module: Islandora DOI Framework

[Mark Jordan]

Hello,

At Simon Fraser University Library we've developed a module that provides the ability to assign Digital Object Identifiers (DOIs) to Islandora objects. It's available at:

https://github.com/mjordan/islandora_doi_framework

This module and its submodules do not replace or compete with the Islandora DOI module bundled with Islandora Scholar. The Scholar DOI module allows you to add objects to a repository based on a list of DOIs, whereas the Islandora DOI Framework module assigns DOIs to existing objects.

Islandora DOI Framework delegates the creation ("minting") and the saving ("persisting") of DOIs to submodules. This separation of concerns means that extending the Framework to suit new use cases is fairly simple. The Framework module includes submodules to mint a DOI using DataCite and persist the DOI to an objects' MODS datastream, and Alex Garnett has developed a persisting submodule that saves the DOI to an object's DDI datastream, illustrating the ability to mix and match minting and persisting modules:

https://github.com/axfelix/islandora_doi_ddi

 

Thanks very much to Alex and to Brandon Weigel for pre-release testing and feedback.

A question for the community: We wrote this module to meet our own use case of assigning DOIs to our objects. At last week's conference, I heard people from other Islandora sites mention in presentations that they want to assign ARKs and PURLs instead of DOIs. I'd like to ask sites who want to assign persistent identifiers to their objects, but plan on assigning some other persistent, globally resolvable identifier like ARKs or PURLs (not DOIs)? I am asking because it would not take a huge amount of work to morph the Islandora DOI Framework into something that supports other types of identifiers as well (Islandora URN Framework? Islandora Global ID Framework?). As far as I can tell, the work involved would entail renaming the module, adding a few mechanisms for overriding the hardcoded use of "DOI" in the module now, and writing additional submodules to do the work of minting the ARKs/PURLs/etc. I am happy to consider doing this now, at the initial release of this module, if I hear from sites that can provide real use cases. Otherwise, it will remain DOI-only at its initial release. Let me hear from you if you're one of those sites. If you have use cases, please describe them in the module's issue queue.

Mark

[Bryan Brown]

That's awesome! We've been looking for something like this. I look forward to testing this out on our IR!

-Bryan

[Mark Jordan]

Thanks Bryan, I'd love to hear your feedback,

Mark

--
For more information about using this group, please read our Listserv Guidelines: http://islandora.ca/content/welcome-islandora-listserv
---
You received this message because you are subscribed to the Google Groups "islandora" group.
To unsubscribe from this group and stop receiving emails from it, send an email to islandora+...@googlegroups.com.
Visit this group at https://groups.google.com/group/islandora.
To view this discussion on the web visit https://groups.google.com/d/msgid/islandora/910a09e8-2c3e-4ca2-990e-645de1a4c85f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[W. P. Wentzell]

Hello Mark,

This is fantastic! Our use case relies on ARKs, as that is what our parent University is using. Having the option to mint ARKs would make this a no-brainer for us. If you do decide to make those additions, please consider our request. Thanks again.

Paul

[Aaron Krebeck]

I'm very excited about using this module for our IR.  We are currently building a system that can automatically generate faculty person entities from their ORCID information.

I'm having trouble making the "DOI" subtab appear under each object's "Manage" tab.  I have cloned the module, enabled the Islandora DOI DataCite, Islandora DOI Framework, and Islandora DOI MODS modules and submodules, granted the proper permissions, and configured my DataCite with our credentials.  But I see no sub tab on my documents, citations, or other content types.

Am I missing something simple (entirely possible)?

On Tuesday, May 23, 2017 at 6:31:19 PM UTC-4, Mark Jordan wrote:

[Mark Jordan]

Aaron, I'm in a call at the moment so can't look into this, but would you mind opening an issue at https://github.com/mjordan/islandora_doi_framework/issues so we can take this off list?

Mark

--
For more information about using this group, please read our Listserv Guidelines: http://islandora.ca/content/welcome-islandora-listserv
---
You received this message because you are subscribed to the Google Groups "islandora" group.
To unsubscribe from this group and stop receiving emails from it, send an email to islandora+...@googlegroups.com.
Visit this group at https://groups.google.com/group/islandora.

To view this discussion on the web visit https://groups.google.com/d/msgid/islandora/dfe5b458-e541-4bd4-8a83-e7b7db57db85%40googlegroups.com.

[Krebeck, Aaron]

I'll be happy to.  Thanks.

A

Aaron Krebeck

Digital Services Librarian

Washington Research Library Consortium

301-390-2040

To unsubscribe from this group and stop receiving emails from it, send an email to islandora+unsubscribe@googlegroups.com.

Visit this group at https://groups.google.com/group/islandora.
To view this discussion on the web visit https://groups.google.com/d/msgid/islandora/dfe5b458-e541-4bd4-8a83-e7b7db57db85%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

For more information about using this group, please read our Listserv Guidelines: http://islandora.ca/content/welcome-islandora-listserv
---

You received this message because you are subscribed to a topic in the Google Groups "islandora" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/islandora/3dvSnZfOUNM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to islandora+unsubscribe@googlegroups.com.

Visit this group at https://groups.google.com/group/islandora.

To view this discussion on the web visit https://groups.google.com/d/msgid/islandora/1871636636.140613211.1512581768745.JavaMail.zimbra%40sfu.ca.

[Aaron Krebeck]

Done.  Thanks a lot.

Aaron

[Mark Jordan]

Speaking of ORCHID, the next thing we'll need to tackle here at SFU is integrating ORCHIDs into our Islandora. Is anyone doing any of that yet? I know that "integrating into Islandora" is vague, but we are still getting our head around what we want to do, so if I were any more specific it would be premature. But, we're prepared to do some development on this.

Mark

----- On Dec 6, 2017, at 8:58 AM, Aaron Krebeck <kre...@wrlc.org> wrote:

[Aaron Krebeck]

Here at Washington Research Library Consortium, we are working on a pilot project to integrate ORCIDs into Islandora and are defining that work as such:

Faculty members would be presented with a form that allows them to connect their ORCID to our Islandora Institutional Repository.  If they don't already have an ORCID, it allows them to create one.  The middleware magic (coded in Python and Javascript by a much more capable colleague) would then retrieve faculty bio information from their ORCID (name, department, ORCID of course, university, areas of study, etc) and use the Islandora REST API to build a somewhat rudimentary person entity.  This same middleware service will also grab listed publications for that ORCID and create citation objects also through the REST API that could then be "attached" to that person entity using existing functionality in Islandora Scholar.  When this is complete, library staff or the faculty themselves could go in and flesh out the person entity or publications more fully with thumbnail and further bio information.

We have tested the various parts successfully but are now trying to pack them up into something more complete that is ready for deployment to our development server.  I'll be happy to give more detailed information when we are a bit further down the path.

[Brandon Weigel]

That sounds like a great tool, Aaron. Please do update us when it's been developed some more; I know a number of sites who would be very interested in deploying something like that.

[Rosie Le Faive]

We have something started [1]. It seems almost trivially simple - implement the "connect or create" button - but turned out to require a lot of attention to details and the human side rather than the technical side. ORCID doesn't just hand out production API keys, you have to demo to them that your implementation meets requirements[2] - for example, you must store the tokens (we use a datastream) and you must style the button with their branding and you must have a page on your IR explaining what ORCID is and why your scholars should get and connect them... it was the hand-holdiest API key application procedure I've ever seen - and probably the integration that we were best prepared for as a result. We haven't done any slurping of ORCID data to populate our MADS profiles or related citations yet, but that's on the horizon if uptake is good. 

[1] https://github.com/roblib/upei_roblib_orcid

[2] https://members.orcid.org/api/workflow/repository