DSpace 7.6.1 ORCID integration / Synchronization settings ERROR

[Matthias Letsch]

Hello there,

I managed to activate ORCID integration in a test environment with connection to the ORCID sandbox api. (I'm only interested in the Profile and synchronization part, not the ORCID authentication method). Unfortunately, when I try to update ORCID synchronization settings, I get a error message.

So what I did:
1. Enable configurable entities (https://wiki.lyrasis.org/display/DSDOC7x/Configurable+Entities) and Enable Researcher profiles (https://wiki.lyrasis.org/display/DSDOC7x/Researcher+Profiles)

2. Get ORCID sandbox credentials (https://info.orcid.org/documentation/integration-guide/sandbox-testing-server/) and enable ORCID integration by setting properties in local.cfg / modules/orcid.cfg (https://wiki.lyrasis.org/display/DSDOC7x/ORCID+Integration)

3. Log in as test person, claim an existing Person entity as Researcher Profile, connect the profile to sandbox orcid id. <-- Everything worked so far.

The DSpace ORCID page now states the following:
Granted Authorizations: Get your ORCID ID
Missing authorizations: " Great! This box is empty, so you have granted all access rights to use all functions offers by your institution."

The Error
When changing values in ORCID Synchronization settings and clicking on "Update settings", an error message appears "The update of the synchronization settings failed"

The dspace logs tell me the following:

2024-06-13 17:20:41,332 WARN  unknown unknown org.dspace.discovery.SolrServiceImpl @ We have a collection or community admin with ID: 6edd60e9-9457-4ec7-91a0-cbaefec205e2 without any administrable collection or community!

2024-06-13 17:20:41,363 WARN  unknown unknown org.dspace.discovery.SolrServiceImpl @ We have a collection or community admin with ID: 6edd60e9-9457-4ec7-91a0-cbaefec205e2 without any administrable collection or community!

2024-06-13 17:20:41,369 INFO  f70163a4-0bc1-4d1d-a361-1601ecfd846b 98ac4304-eeaf-4c3c-96ba-3d575a332afb org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api/eperson/profiles/6edd60e9-9457-4ec7-91a0-cbaefec205e2] originated from /entities/person/08715eca-330f-4798-91e6-91a476dafce7/orcid

2024-06-13 17:20:41,501 WARN  unknown unknown org.dspace.discovery.SolrServiceImpl @ We have a collection or community admin with ID: 6edd60e9-9457-4ec7-91a0-cbaefec205e2 without any administrable collection or community!

2024-06-13 17:20:41,532 WARN  unknown unknown org.dspace.discovery.SolrServiceImpl @ We have a collection or community admin with ID: 6edd60e9-9457-4ec7-91a0-cbaefec205e2 without any administrable collection or community!

2024-06-13 17:20:41,546 INFO  f70163a4-0bc1-4d1d-a361-1601ecfd846b b945ba4b-b7e8-46e4-8a6f-3d28184cc02a org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [PATCH /server/api/eperson/profiles/6edd60e9-9457-4ec7-91a0-cbaefec205e2] originated from /entities/person/08715eca-330f-4798-91e6-91a476dafce7/orcid

This ID belongs to the user with whom I am testing the Orcid link and want to update the settings. So that reads as follows for me: Users who link their profile to ORCID need certain rights to at least one collection or community for the ORCID synchronization to work. Do I understand that correctly?

As an admin, how do I assign these rights to users? Can I automate this or do I have to manually give each user with an ORCID link rights to a collection? I don't quite understand this yet. Does anyone have any experience with ORCID integration and can help me here?

Many thanks and best regards
Matthias

[Matthias Letsch]

Perhaps for completeness: My user is already in the Submitters Role group for Collection "Publications", to which the corresponding publication entity is assigned.

[Sean Kalynuk]

Hi Matthias,

 

Regarding the error “The update of the synchronization settings failed”, this has been documented as part the following issue:

 

https://github.com/DSpace/DSpace/issues/8925

 

Locally, I applied the source code fix as described in a comment from that issue https://github.com/DSpace/DSpace/issues/8925#issuecomment-1617623431 and it resolved that particular problem for us (at least it did with 7.5).

 

-- 

Sean

 

From: dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf of Matthias Letsch <lets...@gmail.com>
Date: Thursday, June 13, 2024 at 10:32 AM
To: DSpace Technical Support <dspac...@googlegroups.com>
Subject: [dspace-tech] DSpace 7.6.1 ORCID integration / Synchronization settings ERROR

Caution! This message was sent from outside the University of Manitoba.

 

--
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 dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/ddd09eed-5daf-438f-b4e7-657b68d9a173n%40googlegroups.com.

[Matthias Letsch]

Hi Sean,

great! That was it. Thank you!

I also had to change the scope to

orcid.scope = /activities/update

in order to get publications pushed to orcid.

Kind regards,

Matthias