RE: [dspace-tech] Re: Problems with Orcid in dspace 6.3

Technical Support Subject: Re: [dspace-tech] Re: Problems with Orcid in dspace 6.3 Great. I've left a comment in DS-3999 stating that it appears to correct the issue. - Darryl On Thursday, September 20, 2018 at 3:26:06 PM UTC-6, Tim Donohue wrote: Hi Darryl, We welcome *either* code reviewe

[dspace-tech] Re: Problems with Orcid in dspace 6.3

Thanks Darryl, This makes sense now. In my testing the same authority key is generated for dc.contributor.editor and it's different from the key generated for dc.contrinbutor.author so i believe it's by design. I hope there's a good reason for that because it's essentially the same person, and

[dspace-tech] Re: Problems with Orcid in dspace 6.3

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 fi

[dspace-tech] Re: Problems with Orcid in dspace 6.3

Hi, The fix in DS-3999 worked for me when using the Author field (dc.contrinbutor.author) but when using the editor field (dc.contributor.editor) a new id is generated, am i missing something? Thanks, Mike On Sunday, September 16, 2018 at 5:37:20 AM

Re: [dspace-tech] Re: Problems with Orcid in dspace 6.3

t;>> authors added from ORCID, so, when there are duplicate author entries, you >>>> cannot differentiate authority_type=”orcid_id” from >>>> authority_type=”person” >>>> for the same person >>>> >>>> · UpdateAuthorities has mul

Re: [dspace-tech] Re: Problems with Orcid in dspace 6.3

kup for >>> authors added from ORCID, so, when there are duplicate author entries, you >>> cannot differentiate authority_type=”orcid_id” from authority_type=”person” >>> for the same person >>> >>> · UpdateAuthorities has multiple issues (-i opti

Re: [dspace-tech] Re: Problems with Orcid in dspace 6.3

s://jira.duraspace.org/browse/DS-3302) >> >> >> >> -- >> >> Sean >> >> >> >> *From:* dspac...@googlegroups.com < >> dspac...@googlegroups.com > *On Behalf Of *Darryl Friesen >> *Sent:* September 20, 2018 11:18 AM >

Re: [dspace-tech] Re: Problems with Orcid in dspace 6.3

records) (see > https://jira.duraspace.org/browse/DS-3302) > > > > -- > > Sean > > > > *From:* dspace-tech@googlegroups.com *On > Behalf Of *Darryl Friesen > *Sent:* September 20, 2018 11:18 AM > *To:* DSpace Technical Support > *Subject:* [dspace-tech] Re

RE: [dspace-tech] Re: Problems with Orcid in dspace 6.3

https://jira.duraspace.org/browse/DS-3302) -- Sean From: dspace-tech@googlegroups.com On Behalf Of Darryl Friesen Sent: September 20, 2018 11:18 AM To: DSpace Technical Support Subject: [dspace-tech] Re: Problems with Orcid in dspace 6.3 While I haven't experimented with what happens

[dspace-tech] Re: Problems with Orcid in dspace 6.3

While I haven't experimented with what happens when adding additional authors, I've noticed that the "orcid_id" field also seems to get removed by the "index-authority" job that runs as part of cron. Perhaps there's a common task that is executed during both processes that is messing up the So