Mike, the ORCID Integration page (https://wiki.duraspace.org/display/DSDOC6x/ORCID+Integration#ORCIDIntegration-AddingadditionalfieldsunderORCID) has this comment
*Note*: Each metadata field has a separate set of authority records. > Authority keys are not shared between different metadata fields. E. g. > multiple dc.contributor.author can have the same authority key and point to > the same authority record in the cache. But when an ORCID is chosen for a > dc.contributor.editor field, a separate record is made in the cache. Both > records are updated from the same source and will contain the same > information. The difference is that when performing a look-up of a person > that has been introduced as an authority for an author field but not yet as > an editor, it will show as record that is not yet present in the repository > cache. So I wonder if the new IDs are actually by-design, because they are for a different metadata field. Or is your issue not that dc.contrinbutor.author and dc.contributor.editor each contain different IDs, but that the patch only fixed the issue for dc.contrinbutor.author and dc.contributor.editor still has teh same issue as before (multiple authority control records in the Solr database for the same person, each with a new ID)? - Darryl -- 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.
