Hi Tomasz,

One thing to check - the ORCID field may store the values differently to how you store them (e.g. as 19 characters vs a full URI).

 

I don’t think changing the field type would alter the table in any way, but if you store it as anything other than 0000-1234-1234-123X, I think you'll get validation warnings from:

https://github.com/eprints/orcid_support/blob/master/lib/plugins/EPrints/MetaField/Orcid.pm#L117-L149

 

Cheers,

John

PS there is a minor update (css styling) and a pull-request to render the links over https in the GitHub version that hasn't been included in a Bazaar version yet.

 

 

 

Hi Tomasz,

 

Follow the instructions on this wiki page: https://wiki.eprints.org/w/ORCID_Support

it explains how to deal with existing ORCID fields in creators and users. https://wiki.eprints.org/w/ORCID_Support#Existing_ORCID_Fields

It is as simple as installing the plugin and then updating your creators orcid field to type ‘orcid’ in the eprint_fields.pl file.

 

Good luck!

Monica

 

 

 

We have Import from ORCID plugin installed: http://bazaar.eprints.org/354/

We also have basic ORCID support in our repository based on this information: https://wiki.eprints.org/w/ORCID.

That means we already have an “orcid” subfield for eprints_creators where we have been collecting ORCIDs of authors. 

This field is of type “text”, not “orcid” as the ORCID Support plugin now has it.

 

Now we want to move to the official ORCID Support plugin: http://bazaar.eprints.org/544/

 

What is the best way to install the ORCID Support plugin without breaking things, and without losing the ORCIDs that we have been collecting?

 

Method 1 :

 

1)    Write a script to copy all author ORCID fields into a new field, such as “ORCID-ID”

2)    Remove the old ORCID field from creators in eprints_fields

3)    Run epadmin update

4)    Install the ORCID Support plugin which will install the new ORCID fields

5)    Write a script to copy the old “ORCID-ID” fields into the new fields

 

Method 2 :

 

1)    Try to install the ORCID Support plugin on top of the existing configuration

 

Obviously, Method 2 sounds easier and quicker, as I would rather not have to write these scripts to move metadata values around, but we would probably receive errors during installation of the plugin, since the “ORCID” field already exists in creators. 

Could we then just try to rename the “type” of that field to “orcid” to fix it?

 

Any comments/suggestions would be greatly appreciated.  Thank you!

 

Tomasz

 

 

University of Tasmania Electronic Communications Policy (December, 2014).
This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise.