All, For anyone affected by the index-authority bug described in https://jira.duraspace.org/browse/DS-3999, we could use more testers for the proposed fix at: https://github.com/DSpace/DSpace/pull/2195 . The quicker bug fixes get tested or reviewed, the quicker we are able to move them along into the actual codebase. While we do have some volunteers that help us with testing/reviewing, finding additional community users can always speed up the process.
- Tim On Thu, Sep 20, 2018 at 1:12 PM Sean Kalynuk <[email protected]> wrote: > Hi Darryl, > > > > I’m currently experimenting with DSpace 6.3 and have the same or similar > issues. > > > > · index-authority is removing orcid_id but leaving the > authority_type as “orcid” (see https://jira.duraspace.org/browse/DS-3999) > > · The orcid_id is not displaying in the Author Lookup 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 option results in NPE > and a full update only runs on 10 records) (see > https://jira.duraspace.org/browse/DS-3302) > > > > -- > > Sean > > > > *From:* [email protected] <[email protected]> *On > Behalf Of *Darryl Friesen > *Sent:* September 20, 2018 11:18 AM > *To:* DSpace Technical Support <[email protected]> > *Subject:* [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 > Solr database. > > > > I've also noticed issues with the authority control/ORCID Lookup features > during submission (and when editing). The OCRID seems to be lost there > too, and the authority control will happily create duplicates. I posted > about it a couple weeks ago: > > > > https://groups.google.com/d/msg/dspace-tech/4nJRVyn8Hk8/M0TnMAIBCgAJ > > > > I'm happy the ORCID lookup works again, but there seems to be some issues > with it. > > > > - Darryl > > > > On Sunday, September 16, 2018 at 3:37:20 AM UTC-6, Stefanie Behnke wrote: > > Dear all, > > we use Dspace 6.3, XMLUI Interface and ORCID enabled. > > Submitting a new item with 2 authors works. The result in the authority > shows: (example for one author) > > { > > "id": "75e2dd03-7cdf-4e21-9b1d-293f02d3c0cf", > > "field": "dc_contributor_author", > > "value": "Behnke, Stefanie", > > "deleted": false, > > "creation_date": "2018-09-16T09:01:40.474Z", > > "last_modified_date": "2018-09-16T09:01:40.474Z", > > "authority_type": "orcid", > > "first_name": "Stefanie", > > "last_name": "Behnke", > > "orcid_id": "0000-0001-5923-423X" > > }, > > > > Trying to add a third author with ORCID to this item make the “orcid_id” > for the existing authors vanish from the authority: > > { > > "id": "75e2dd03-7cdf-4e21-9b1d-293f02d3c0cf", > > "field": "dc_contributor_author", > > "value": "Behnke, Stefanie", > > "deleted": false, > > "creation_date": "2018-09-16T09:01:40.474Z", > > "last_modified_date": "2018-09-16T09:01:40.474Z", > > "authority_type": "orcid", > > "first_name": "Stefanie", > > "last_name": "Behnke" > > }, > > > > I cannot imagine that this should be the intended behaviour, so I think > this is a bug. > > Any help is much appreciated. > > Best regards > > Stefanie > > -- > 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. > > -- > 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. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- 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.
