I was happy to see the return of ORCID in 6.3, however I'm experiencing 
some odd behavior which I think may be a bug.

Using the Lookup button, the initial interaction with the OCRID v2 API 
seems to work great

[image: orcid_bug_01.png] <about:invalid#zClosurez>



A match is found, I can see the ORCID and I can add that person as an 
author. An entry is written in the Solr autority database.


[image: orcid_bug_02.png] <about:invalid#zClosurez>

However, if the Lookup button is used again with that same author's name, 
not only is the current entry from authority control returned, but an 
additional hit from OCRID appears (shown in yellow in the image below).  To 
add to the confusion, the current hit from authority control does *not* show 
the ORCID, even though is it recorded in the Solr database.


[image: orcid_bug_03.png] <about:invalid#zClosurez>


This differs from the previous behavior with DSpace and the ORCID v1 API.  
I'm sure matches from the local authority control database *would* display 
the ORCID, and if a hit from the ORCID API matched an existing entry in 
authority control, it would not be displayed in italics as a new author.


If I go ahead and select the new italicized author in the above scenario, 
DSpace will create a duplicate entry in the authority control database.  
The records will have different record IDs, but the data, including the 
ORCID ID, is the same.


[image: orcid_bug_04.png] <about:invalid#zClosurez>



This process can repeat; each time you lookup an author, an additional new 
entry from ORCID will appear as new, and if selected, and additional 
authority control record will be created.

I'm seeing this behavior on my test server (running DSpace 6.4-SNAPSHOT 
checked out of GitHub lat week) but I also see the same behavior on the 
DSpace 6.3 demo site, so I don't believe it's an issue with my 
configuration.

Does this sound like a bug?  Is anyone else using ORCID v2 integration 
experiencing this behavior?

- Darryl


----------------------------------------------------------------------

Darryl Friesen, B.Sc., Programmer/Analyst    darryl.frie...@usask.ca

Library Systems & Information Technology,    http://library.usask.ca/

University of Saskatchewan Library

----------------------------------------------------------------------

"Go not to the Elves for counsel, for they will say both no and yes"

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Reply via email to