Assigning DOIs automatically for a single community

Gail Steinhart

unread,

May 10, 2021, 2:56:41 PM5/10/21

to dspac...@googlegroups.com

Greetings all and with apologies for posting to both lists.

We have a use case where a community would like DOIs assigned to items in all their collections automatically, but we do not want to do that across the entire repository. Does anyone know if this is possible, and better still, is anyone actually doing it? DSpace documentation is written for implementation across the repository (understandable), so I can’t tell whether it’s not possible or whether it simply not documented.

Thanks so much,

Gail

Gail Steinhart

Open Scholarship Services Librarian

Cornell University Library Information Technology

218 Olin Library | 607.255.7251

https://orcid.org/0000-0002-2441-1651 | @gailst

she/her

Sean Kalynuk

unread,

May 10, 2021, 3:10:55 PM5/10/21

to Gail Steinhart, dspac...@googlegroups.com

Hi Gail,

There is a feature request for that functionality in DSpace 7, although it doesn’t look like it has been implemented yet:

https://jira.lyrasis.org/browse/DS-3749

As far as I can tell, DSpace 6 has DOI assignment for the whole repository, or nothing at all.

--

Sean

From: dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf of Gail Steinhart <gs...@cornell.edu>
Date: Monday, May 10, 2021 at 1:56 PM
To: dspac...@googlegroups.com <dspac...@googlegroups.com>
Subject: [dspace-tech] Assigning DOIs automatically for a single community

Caution: This message was sent from outside the University of Manitoba.

--
All messages to this mailing list should adhere to the Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/1FF1987A-783E-4893-91D1-CC1390394370%40cornell.edu.

MALMQUIST Hrafn

unread,

May 17, 2021, 8:37:04 AM5/17/21

to Sean Kalynuk, Gail Steinhart, dspac...@googlegroups.com

Hi Gail and other

Sorry for the late reply.

The implemention for 7.1 is advanced, and I know that a port to 6.x is also very advanced. Kim Shepherd is doing this great work. See https://github.com/DSpace/DSpace/pull/2789

The safe bet would be to wait for this feature to be officially implemented. Although it is very unlikely that it will be included in the upcoming 6.4 which we've been meaning to release for ages now.

Alternatively, you could have a look at our workaround:

https://github.com/UoEMainLibrary/DSpace-6.x/tree/doi_collection

Note that this is a STATIC repo of a version of the 6.3 code. It is not in sync with the live offical dspace-6_x branch.

There are a few commits you would need on that branch, but the bulk of it is in this one:

https://github.com/UoEMainLibrary/DSpace-6.x/commit/70df2327bdff0515527f1178c3c8ee8874fbf599

What this modification does is enable a checkbox in when editing a collection (note, not when creating a new one) which, when checked, logs the uuid of the collection in a new table in the database, doi_collection. When the doi-organiser cronjob is run it will check if the item's owning collection is in that table. This is then an on off switch for DOI minting and mean you can submit an item with DOI minting off, switch it on and submit an item that only gets a DOI.

This might or might not cause a complication when migrating to a future version of DSpace. Let me be clear, you can implement this at your own risk with no guarantees.

Best regards, Hrafn Malmquist

developer in the Digital Library Team, University of Edinburgh

From: dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf of Sean Kalynuk <Sean.K...@umanitoba.ca>
Sent: 10 May 2021 20:10
To: Gail Steinhart <gs...@cornell.edu>; dspac...@googlegroups.com <dspac...@googlegroups.com>
Subject: [dspace-tech] Re: Assigning DOIs automatically for a single community

This email was sent to you by someone outside the University.

You should only click on links or attachments if you are certain that the email is genuine and the content is safe.

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/YTXPR0101MB08482B117FE3D38D08434CBEE8549%40YTXPR0101MB0848.CANPRD01.PROD.OUTLOOK.COM.

The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th’ ann an Oilthigh Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336.

Pascal-Nicolas Becker

unread,

May 17, 2021, 1:37:00 PM5/17/21

to DSpace Technical Support

Hi Gail, hi Hrafn, hi everyone on this list,

Hrafn already provided the correct link to our pull request, thanks for that. Let me add a little bit of background. Kim Shepherd and I are working with The Library Code. The Library Code is a DSpace Service Provider and Certified DSpace Partner. The pull request is based on code that we developed with the support of Technische Informationsbibliothek and Technische Universität Hamburg.

Our code does provide the possibility to restrict the assignment of DOIs based on the owning collection of items. It also offers possibilities to make this decision depending on the existence of certain metadata fields, depending on the value of metadata fields, the existence of file(s) in certain Bundles, or many other questions. It is a complete filter system that allows to combine these rules with boolean logic (AND, OR, NOT). We will give a presentation at Open Repositories 2021 about that.

To make it easy to apply upgrades to DSpace 5 and 6 those versions get bug fixes only and no new features, following the rules of the DSpace community. That is the reason we provided the pull request for DSpace 7 only. We do have code for DSpace 5 and DSpace 6 that is running in production at some of our clients. We do license this code as Open Source and are willing to make it publicly available, but we do need financial support to fund the work that we thing is still missing. We basically need to enhance our documentation and lower the effort needed to embed the code in DSpace installations. If anyone here is interested in getting the code for DSpace 5 and/or 6 and willing to help funding the necessary work, please get in touch with me.