len
>
>
>
> *From:* dspace-tech@googlegroups.com *On
> Behalf Of *Terry Brady
> *Sent:* Tuesday, May 14, 2019 12:32 PM
> *To:* DSpace Technical Support
> *Subject:* Re: [dspace-tech] ORCID integration- programmatically pulling
> ORCID from authent
Hi Terry, could you point us to a record which has a linked ORCID? Helen
From: dspace-tech@googlegroups.com On Behalf Of
Terry Brady
Sent: Tuesday, May 14, 2019 12:32 PM
To: DSpace Technical Support
Subject: Re: [dspace-tech] ORCID integration- programmatically pulling ORCID
from
That clears it up. Thanks again Terry!
-Gabe
On Tuesday, May 14, 2019 at 2:32:38 PM UTC-4, Terry Brady wrote:
>
> That is an important detail that I did not include. We do not use the
> lookup tool. We key in the ORCID in the "identifier" box or we pull it in
> from ProQuest.
>
> If you
That is an important detail that I did not include. We do not use the
lookup tool. We key in the ORCID in the "identifier" box or we pull it in
from ProQuest.
If you look at one of our ETD collections, you will see that some items
have a linked ORCID.
Terry-
I feel silly asking, but how does this actually work? From what I can see
of DSpace's ORCID integration, the ORCID appears only as a text string
within the authentication key. Assuming an article has only one author,
will the ORCID actually appear in that field? Or is additional
We have placed this field in dc.identifier.orcid and we modified our theme
to display that field as a hyperlink to the ORCID website.
This works reasonably well for items with only one author. Since the
majority of our content with ORCID's are ETD's, this works for us.
Terry
On Tue, May 14,
Group-
We've enabled ORCID integration on our author field and are wondering if
there's a way to programmatically add the ORCID from the authentication key
to another field specifically for this data.
So, we'd like to take the text string highlighted in pink...
[image: Screen Shot
