Thank you darry for your reply and clarifications. What about having multiple variants/formats of the same author (dc.contributor.author) names but all linked to the same authority key. Example can be seen below. Even though this author is the same one, this shows as if they are different authors, but when you click on any of them, it shows 3 (total = 1+2) records as it is filtered by the authority key which is shared between both author formats. Can you please clarify why and how the authority key is generated to be shared for two different formats. Is there any technique by the system to automatically aggregate different authors' name formats into the same authority key? [image: image.png]
On Thu, Oct 12, 2023 at 7:48 PM [email protected] < [email protected]> wrote: > My understanding is that each field under authority control is considered > unique and distinct from the others, and will therefore be given different > authority control IDs. As far as I know (and I think this holds for DSpace > 7.6 as well as 6.x) there is no way to share the authority control data > across multiple fields. > > And to make matters worse, authority control comes with a "confidence" > value. If the confidence values also differ, then the author may be listed > again. Our ETD system deposits directly into DSpace, some people don't > bother with the Lookup feature in DSpace 6.x, some do. The end result is a > mess of authority control records, with differing confidence values, in > multiple metadata fields, all for the same person. We've seen the same > author name repeated in our author browse 5 or 6 times. > > - Darryl > > > > On Thursday, October 12, 2023 at 6:05:48 AM UTC-6 Nada Aboueata wrote: > >> Dear, >> >> >> >> We are implementing DSpace version 6.3 and enabling ORCID for two >> metadata fields (dc.contributor.author, dc.contributor.advisor). >> >> >> >> However, when we try to add the same author with the same ORCID ID under >> two *different* metadata fields (as main author and advisor), we have >> noticed that the system is assigning two different authority keys to each >> metadata field even though both are linked to the same ORCID id . The only >> difference is the metadata field that holds this data. As a result, once >> we browse authors, it shows two author records as both assigned to two >> different authority keys. >> >> >> >> In our configuration, we have configured two authority indexes per >> metadata, one for author and other for advisor as shown below. >> >> >> >> authority.author.indexer.field.1=dc.contributor.author >> >> authority.author.indexer.field.2=dc.contributor.alternativeAuthor >> >> authority.author.indexer.field.3=dc.contributor.advisor >> >> >> >> Could you please advise if it’s possible to assign the same authority >> keys for the same authors regardless where it’s stored in which metadata. >> >> >> > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > --- > You received this message because you are subscribed to a topic in the > Google Groups "DSpace Technical Support" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/dspace-tech/qGtYUgjQ1_E/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/388910d0-206a-49b2-aba5-c364cf070d67n%40googlegroups.com > <https://groups.google.com/d/msgid/dspace-tech/388910d0-206a-49b2-aba5-c364cf070d67n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CAPzkmC7BCvaO2Jw9dt4Q0nm23roxeo%2BiX61oaPO4iq%3Ds5cKYDg%40mail.gmail.com.
