Hello, Our institute relied quite heavily on DSpace's ORCID integration and, as such, we have a few thousand records with associated ORCID identifiers. Unfortunately this integration did not store the identifiers in a regular metadata field in the database and the only place they live is in the "authority" Solr core. We made the decision to create a controlled vocabulary so that our editors add ORCID identifiers to items during item submission.
I want to share a Python script[0] that I wrote to extract the ORCID identifiers from Solr and query the public ORCID API for the names associated with those identifiers. The script has a few other things that might be useful to people here, for example reading a list of ORCID identifiers from a text file, extracting identifiers from Solr and simply saving them without resolving their names, etc. I'm still trying to figure out how to link ORCID identifiers with items somehow, as there is no strong link between the metadata and the authority Solr core—perhaps looking at each item's dc.contributor.author and checking each listed authority to see if it has an ORCID identifier, then inserting a new metadata field with the ORCID identifier for that item. Anyways, I digress! This script is tested on macOS, Linux, and Windows with DSpace 5.x. I've added quite a few sanity checks and verbose debug messages, but nevertheless your mileage may vary! Please try it and share any comments or suggestions. [0] https://gist.github.com/alanorth/57a88379126d844563c1410bd7b8d12b Thanks, and I hope that someone finds this useful. On Wed, Feb 7, 2018 at 12:51 PM Alan Orth <[email protected]> wrote: > Just an FYI that ORCID.org has finally deprecated the v1 API that DSpace > was using to look up authors. Technically their mailing list > announcement[0] says that as of February 1, 2018 the default API version > for calls to pub.orcid.org will become v2, and that v1 will move to a new > URL until March 1, 2018, but this appears to be broken currently: > > $ curl -i http://pub.orcid.org > HTTP/1.1 302 Found > Server: nginx/1.4.6 (Ubuntu) > Date: Wed, 07 Feb 2018 10:45:39 GMT > Location: https://pub.orcid.org/v2.0/ > Connection: keep-alive > Set-Cookie: X-Mapping-fjhppofk=BB32ADE26669E4E542AAA075A6CC205A; path=/ > Content-Length: 0 > > $ curl -i http://pub.orcid.org/v1.2 > HTTP/1.1 302 Found > Server: nginx/1.4.6 (Ubuntu) > Date: Wed, 07 Feb 2018 10:45:49 GMT > Location: https://pub.orcid.org/v2.0/v1.2 > Connection: keep-alive > Set-Cookie: X-Mapping-fjhppofk=BB32ADE26669E4E542AAA075A6CC205A; path=/ > Content-Length: 0 > > In any case, DSpace 4.x, 5.x, and 6.x are hard coded to use the old API > path at http://pub.orcid.org (on HTTP, no less!) and can now no longer > look up authors and ORCID iDs from ORCID.org. > > [0] https://groups.google.com/forum/#!topic/orcid-api-users/qfg-HwAB1bk > > Regards, > > On Mon, Nov 13, 2017 at 5:01 PM Alan Orth <[email protected]> wrote: > >> Hi, >> >> The ORCID v1 API that DSpace 5 and 6 use to look up author names during >> item submission is set to be decommissioned in "late 2017"[0]. This was >> briefly discussed in the June, 2017 DSpace Community Advisory Team (DCAT) >> meeting[1], and there is an open issue[2] on Jira tracking work to move to >> the new ORCID API in DSpace 6.3. Does anyone know how this will affect >> DSpace? For example, will the author lookup only return authors that are >> already in the local database, or will it break the lookup function >> entirely in some weird way? I suppose it could be tested by blocking access >> to the API endpoint or something... >> >> Anyways, I'm partially just thinking out loud and partially trying to >> start a discussion. Thank you, >> >> [0] https://members.orcid.org/api >> [1] https://wiki.duraspace.org/display/cmtygp/DCAT+Meeting+June+2017 >> [2] https://jira.duraspace.org/browse/DS-3447 >> -- >> >> Alan Orth >> [email protected] >> https://picturingjordan.com >> https://englishbulgaria.net >> https://mjanja.ch >> > -- > > Alan Orth > [email protected] > https://picturingjordan.com > https://englishbulgaria.net > https://mjanja.ch > -- Alan Orth [email protected] https://picturingjordan.com https://englishbulgaria.net https://mjanja.ch -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
