looking into using the ORCID functionality

[Jose Blanco]

I want to make sure I understand what the ORCID function in 6.3 provides.  So I have a few questions.

(1)  When you run

[dspace]/bin/dspace index-authority

this goes out to: https://pub.orcid.org/v2.1 (defined in dspace.cfg:orcid.api.url )

 

And creates records of them in the authority index.  

Correct?

(2) After the solr authority index is created, depositors of items will be given a "Lookup" button for dc metadata configed, out of the box this is contributor.author.  The user can then click on this button and search for the author and select it. I'm a bit confused about the difference between the case when the selection presents the same author twice ( once italicized, and one not ).  What's the difference in selecting one from the other?

(3)  Do you ever see the ORCIDs for the authors in any of the Dspace pages? Say during the deposit, I select Smith, John with x ORCID, does this show up in the short display?  I would think it would be valuable to see the ORCids?

(4)  I have a spreadsheet of authors and ORCIDs.  Is there a way to get it in the authority index, or is the only way for the authority index to be populated via https://pub.orcid.org/v2.1 when you run "[dspace]/bin/dspace index-authority"?

(5) Do any cron jobs have to be run to maintain the authority index?  Should 

[dspace]/bin/dspace index-authority

be run periodically?  I think it takes a long time for this to run, so it may not be practical?

(6) I think one thing I'm really confused about is why the ORCId is never displayed.

(7) In the table metadatavalue, I think authority is a key to the authority solr index for that record, but what is the confidence field? 

(8)  Is there any information about the orcid in any of the tables of the database?

Thank you!

-Jose

[Sean Kalynuk]

Hi Jose,

 

I’ve encountered a number of issues using the ORCID functionality in DSpace 6.3, and I’m still working through them, but here’s some info based on my experience so far (numbered according to your questions):

 

1. index-authority will keep the Solr authority index up-to-date with respect to metadata in the database that is authority controlled. In regards to ORCID and dc.contributor.author, it does not use the ORCID API to find authors. (Important – See Issue: https://jira.lyrasis.org/browse/DS-3999) More details in the manual than I can include here (https://wiki.lyrasis.org/display/DSDOC6x/ORCID+Integration#ORCIDIntegration-Importingexistingauthors&keepingtheindexuptodate). Keep in mind that the first run will take a long time. In our environment I think I was only getting <2000 records created per hour. In addition to index-authority, in order to keep the ORCID information in the Solr authority index up-to-date, you’re supposed to run “dsrun org.dspace.authority.UpdateAuthorities” but there’s another issue as well - https://jira.lyrasis.org/browse/DS-3302. I don’t have an official patch for it yet, but the problem is that the default Solr query only checks 10 records. I only corrected this in our source code for now, and haven’t really had the time to test it fully.
2. Italicized authors in the lookup are the ones found using the ORCID API, whereas the non-italicized authors come from your Solr authority index. If you don’t apply the fix for DS-3999 you may see duplicates.
3. The ORCID iD is only displayed in the lookup dialog. However, if you apply the Expanded ORCID patch (https://atmire.github.io/expanded-ORCID-support/#/) a clickable icon is displayed next to authors’ names that have their ORCID iD assigned in DSpace. There are other features as well. (See issue https://github.com/atmire/expanded-ORCID-support/issues/3 with regards to the DS-3999 fix).
4. ORCID iDs can be populated manually via the lookup dialog (either via the admin-level metadata edit, or with a normal submission when adding authors), and also imported via the metadata import tool. Using the metadata import tool to do it (https://wiki.lyrasis.org/display/DSDOC7x/ORCID+Integration#ORCIDIntegration-EditingexistingitemsusingBatchCSVEditing) has its own quirks. Too many to go into here unfortunately, so I’d suggest doing a lot of testing before trying it in production.
5. The recommendation is to run index-authority once a day during off-hours. (The first run of index-authority takes a long time, but subsequent runs don’t take nearly as long. Some recent tests I did took about 1 hour to check and update about 30,000 records.) When you run UpdateAuthorities is dependent on your needs.
6. I was also surprised that the default DSpace 6.3 ORCID functionality did not include a proper item display of the ORCID iD along with the author name (or even a clickable link to the ORCID record). Sure, you can click the ORCID iD link in the lookup dialog, but that doesn’t apply for normal browsing. Other people obviously had the same reaction, hence the Expanded ORCID Support patch. Surprisingly, there is an icon displayed for the confidence level in the detailed metadata view (see more on the confidence in the next answer)
7. You’re correct that the authority key is the identifier that links the metadata record to a record in the Solr authority index. The confidence value is supposed to reflect different levels of confidence on the metadata value based on where the information was obtained, or who entered it. Again, lots of quirks on this one. Check out the source code to see an explanation of different values https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace-api/src/main/java/org/dspace/content/authority/Choices.java. There’s also this issue: https://jira.lyrasis.org/browse/DS-3994
8. All ORCID information is kept in the Solr authority index. Again, really important to get the fix for DS-3999 since if you don’t have it you can lose ORCID information.

 

--

Sean

--
All messages to this mailing list should adhere to the DuraSpace 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/CAK%3DKc-uZDi0W7Qw88VMUM%3Dd2CSyS4zRXV5XW4KuqFjm-pd-cAA%40mail.gmail.com.

[Jose Blanco]

Sean, This is really helpful.  It really sounds like it's not that reliable, with all the issues, but I need to read your response more carefully.

Thank you!!!!

-Jose

[Sean Kalynuk]

You’re welcome. I hope I didn’t scare you. 😊 We do have the bare minimum ORCID support in production (with some of the known patches/fixes applied), but I still need to do a lot more testing before we can really commit to it.

 

BTW, there’s some better info on the Authority Control here:

 

https://wiki.lyrasis.org/display/DSPACE/Authority+Control+of+Metadata+Values

 

Also some better info on the confidence value than I originally provided:

 

https://wiki.lyrasis.org/display/DSPACE/Authority+Control+of+Metadata+Values#AuthorityControlofMetadataValues-Confidence

 

--

Sean

 

From: Jose Blanco <bla...@umich.edu>
Date: Tuesday, February 23, 2021 at 5:13 PM
To: Sean Kalynuk <Sean.K...@umanitoba.ca>
Cc: DSpace Technical Support <dspac...@googlegroups.com>
Subject: Re: [dspace-tech] looking into using the ORCID functionality

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

[Никола Шћепанчевић]

I have a problem, we have a dspace repository, and when I want to add some data from orcid via MyDSpace->start new submission->search for identifier ->ORCID, I am getting only results which are referenced in Scopus, the same issue I'm having with doi. only doi referenced in Scopus are available for submission.