--
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 dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/e707e431-047e-4690-b4d3-ae0071292ac8%40googlegroups.com.
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, 2019 at 10:35 AM Gabriel Galson <tuf0...@temple.edu> wrote:
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......and add it to another field through some kind of automated process.Has anyone found a way to do this? The alternative we're looking at is to manually cut and paste from the authority key, but it seems like there should be an easier way.Thanks in advance for any help or insight you can provide!-GG
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 dspac...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/e707e431-047e-4690-b4d3-ae0071292ac8%40googlegroups.com.
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/dfaf8d2a-6d20-42aa-8037-3697a2c7835d%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/dfaf8d2a-6d20-42aa-8037-3697a2c7835d%40googlegroups.com.
Hi Terry, could you point us to a record which has a linked ORCID? Helen
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CAMp2YEzGwRSxxMo%3Dy%2BW0CvVKQg-BL%3DeZ6vZyHd2UL4JKwkcgvQ%40mail.gmail.com.
Not sure if this helps, but in our case we've added multiple orcids for contributors in each records. To do this we created a custom metadata field dc.contributor.orcid, and modified item-view.xsl.
It matches the contributor by his/hers exact name, and creates a link to his/her orcid profile. This allows for multiple orcids in each record, but the negative to this is that you have to add orcids in each record.
You can see an example at https://gnosis.library.ucy.ac.cy/handle/7/45168
Evelthon
--
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 dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/0782e5e1-6d2f-469f-877a-ebc3e90674a4%40googlegroups.com.