Good day I'm testing the Orcid support in DSpace 6.3 going by instructions here.
https://wiki.lyrasis.org/display/DSDOC6x/ORCID+Integration I haven't tried to use Authority Control for DSpace before. Another resource I have found useful is a webinar done by Atmire a year ago: https://www.atmire.com/articles/detail/webinar-recording-orcid-for-dspace-repositories I am not sure I understand the functionality of the confidence levels. The initial condition in the database is as follows: select count(*), confidence from metadatavalue where metadata_field_id = 3 group by confidence; count | confidence -------+------------ 19 | 0 206 | 300 40067 | -1 1 | 500 13 | 600 This is more or less expected, with the confidence levels of dc.contributor.author values at -1 or "Unset". If I then select a random record and select an author with and Orcid from a lookup, say McCaslin, Laura, 0000-0002-6705-8755. I can then see that the earlier entry has been deleted and a new one now exists but in an incomplete state: select * from metadatavalue where text_value = 'McCaslin, Laura'; metadata_value_id | metadata_field_id | text_value | text_lang | place | authority | confidence | dspace_object_id -------------------+-------------------+-----------------+-----------+-------+-----------------------------------------------+------------+-------------------------------------- 5703635 | 3 | McCaslin, Laura | en | 0 | will be generated::orcid::0000-0002-6705-8755 | 0 | 4a21c3be-48c2-4255-95e2-20950df6b670 I don't understand why the confidence level is only at 0 which signifiies that "No reasonable confidence value is available". I just selected that value manually using the lookup mechanism. Should it not be 600? (see here for the table of confidence values: https://wiki.lyrasis.org/display/DSPACE/Authority+Control+of+Metadata+Values#AuthorityControlofMetadataValues-Confidence) Instead, unless I'm mistaken, a placeholder value ("will be generated::....") is inserted that seems to get replaced only when ./dspace index-authority is run. From a technical perspective it does not make sense to me as the data for Laura McCaslin has just been retrieved from the Orcid API and unless the index-authority job is run frequently there will only be a useless placeholder value behind it until it is run. After index-authority is run the authority value is replaced with an uuid: select * from metadatavalue where text_value = 'McCaslin, Laura'; metadata_value_id | metadata_field_id | text_value | text_lang | place | authority | confidence | dspace_object_id -------------------+-------------------+-----------------+-----------+-------+--------------------------------------+------------+-------------------------------------- 5703635 | 3 | McCaslin, Laura | en | 0 | 10ad8f3f-3331-4a23-b032-00f1cec31b6a | 0 | 4a21c3be-48c2-4255-95e2-20950df6b670 but the confidence is still unchanged. My main question is, how is a confidence value of 600 or "Accepted" achieved? The 13 values already in my repo with 600 were all manually entered BEFORE authority control was enabled. I don't understand why they have 600. Thanks for your help Hrafn 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. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/PAXPR05MB814203935E5B6FC961CF92BEDD459%40PAXPR05MB8142.eurprd05.prod.outlook.com.
