Hi,
We faced the same problem one year ago and it's a known bug caused from the
library Xalan 2.7.1 As there is no updates on that library, the only
solution I found is to use an older one (Xalan 2.7.0) instead of the
"problematic" 2.7.1 if you need to use OAI with that encoding. You have to
You’re welcome. I hope I didn’t scare you. We do have the bare minimum ORCID
support in production (with some of the known patches/fixes applied), but I
still need to do a lot more testing before we can really commit to it.
BTW, there’s some better info on the Authority Control here:
Sean, This is really helpful. It really sounds like it's not that
reliable, with all the issues, but I need to read your response
more carefully.
Thank you
-Jose
On Tue, Feb 23, 2021 at 5:26 PM Sean Kalynuk
wrote:
> Hi Jose,
>
>
>
> I’ve encountered a number of issues using the ORCID
Hi Jose,
I’ve encountered a number of issues using the ORCID functionality in DSpace
6.3, and I’m still working through them, but here’s some info based on my
experience so far (numbered according to your questions):
1. index-authority will keep the Solr authority index up-to-date with
I want to make sure I understand what the ORCID function in 6.3 provides.
So I have a few questions.
(1) When you run
[dspace]/bin/dspace index-authority
this goes out to: https://pub.orcid.org/v2.1 (defined in
dspace.cfg:orcid.api.url )
And creates records of them in the authority index.
