You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
disabling the ORCID confirmation. If someone configure the ORCID API in runtime.properties, and enter the ORCID ID in the profile of a scholar, there is a message Pending confirmation. Can we configure who might approve and whether approve is needed at all.
Describe the solution you'd like
To act just as communication with Scopus
Additional context
Email communication between Arif and @gneissone
Thank you, Benjamin,
I am new to this software. How can we load ORCID triples as admin?
I have the API and I configure the API in runtime.properties. and as the editor, I am able to put the ORCID ID in the profile of the scholar. Now, After I enter the ORCID ID, it is showing the Pending Confirmation. So, my question is who will approve this confirmation? IS there, anyway we can remove this setup for ORCID confirmation?
On Monday, September 26, 2022 at 8:25:09 PM UTC+5:30 benjamin wrote:
Hello Arif,
Unfortunately I don’t think there’s an easy way to allow manual editing through the UI for ORCIDs built into VIVO. There are two options I can think of:
Create a local ‘ORCID’ property. Just create a new data property in your local ontology. You can copy the template logic used for DOIs if you want to link out to ORCID.
It would be nice if the built in ORCID integration was bypassed if ORCID credentials aren’t added to runtime.properties. Perhaps something to look at for the next version.
Is your feature request related to a problem? Please describe.
disabling the ORCID confirmation. If someone configure the ORCID API in runtime.properties, and enter the ORCID ID in the profile of a scholar, there is a message Pending confirmation. Can we configure who might approve and whether approve is needed at all.
Describe the solution you'd like
To act just as communication with Scopus
Additional context
Email communication between Arif and @gneissone
Thank you, Benjamin,
I am new to this software. How can we load ORCID triples as admin?
I have the API and I configure the API in runtime.properties. and as the editor, I am able to put the ORCID ID in the profile of the scholar. Now, After I enter the ORCID ID, it is showing the Pending Confirmation. So, my question is who will approve this confirmation? IS there, anyway we can remove this setup for ORCID confirmation?
On Monday, September 26, 2022 at 8:25:09 PM UTC+5:30 benjamin wrote:
Hello Arif,
Unfortunately I don’t think there’s an easy way to allow manual editing through the UI for ORCIDs built into VIVO. There are two options I can think of:
https://orcid.org/1234-5678-9012-3456 http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2002/07/owl#Thing .
https://orcid.org/1234-5678-9012-3456 http://vitro.mannlib.cornell.edu/ns/vitro/public#mostSpecificType http://www.w3.org/2002/07/owl#Thing .
http://person-uri/ http://vivoweb.org/ontology/core#orcidId https://orcid.org/1234-5678-9012-3456 .
If the ORCID is ‘confirmed’ you can add this triple as well: https://orcid.org/1234-5678-9012-3456 http://vivoweb.org/ontology/core#confirmedOrcidId http://person-uri/ .
It would be nice if the built in ORCID integration was bypassed if ORCID credentials aren’t added to runtime.properties. Perhaps something to look at for the next version.
Benjamin
Benjamin Gross
API Product Manager, Science Group
Clarivate
clarivate.com
Accelerating innovation
On Sep 26, 2022, at 12:00 AM, Arif wrote:
Dear Team,
How to disable the ORCID confirmation and API, try to act just like Scopus.
Thanks,
Arif
The text was updated successfully, but these errors were encountered: