Hi Kev, Although I haven’t changed our default from “ambiguous”, you could set it to “unset” which is the lowest value at -1. That should get everything. After the first run of “dspace index-authority” all confidence values will be “unset”. As you update metadata from the user interface, you might see “novalue” or “accepted”. I have yet to see any other confidence value other than when I tried setting them via the “Import Metadata” feature or directly in the database with a SQL update. And, as usual, you need to make sure “dspace index-discovery” is run afterwards.
>From the code, the possible keywords (and internal integer values) are: accepted (600) This authority value has been confirmed as accurate by an interactive user or authoritative policy uncertain (500) Authority value is singular and valid but has not been seen and accepted by a human, so its provenance is uncertain ambiguous (400) There are multiple matching authority values of equal validity notfound (300) There are no matching answers from the authority failed (200) The authority encountered an internal failure in trying to match the value rejected (100) The authority recommends this submission be rejected novalue (0) No reasonable confidence value is available unset (-1) No confidence value has been set -- Sean From: [email protected] <[email protected]> On Behalf Of Kev Evans Sent: March 13, 2019 10:07 AM To: DSpace Technical Support <[email protected]> Subject: [dspace-tech] Re: Problems with Author LookUp functionality Dspace 6.3 Hi Sean, Many thanks. This makes sense with the issues I am seeing. One question. I want to retrieve as many items as possible. I currently have both authority.minconfidence and authority.minconfidence.dc.contributor.author parameters set to 'accepted' Is this too strict? Cheers Kev On Tuesday, 12 March 2019 22:18:37 UTC, Kev Evans wrote: Hi I am having some issues with the Author Lookup functionality on Dspace 6.3. resulting in multiple ID's for the same author and inconsistent search results from the view items link. Mostly resulting in no results. I have turned off the ORCID integration to identify the issue. In fact I commented out most of the author lookup config to see what difference it would make. It doesn't behave as expected as in the instructions. Can I have some help please? The site is due to go live on Monday. Some indication of where I am going wrong or if this is a bug of some kind will be much appreciated. Kev -- 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 [email protected]<mailto:[email protected]>. To post to this group, send email to [email protected]<mailto:[email protected]>. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout. -- 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 [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.
