Editing ORCID (section)

==Field Recommendations==
As at 2016-10-18 these are the recommended field names and types as discussed at the Jisc ORCID hack day in London - Alan Stiles, John Salter, Adam Vials Moore, Peter West, Andrew Beeken

===New MetaField Type===
* Type 'Orcid' is a subtype of 'id', provides validation and render methods  
N.B. Store the 16 digit, hyphen separated value, without the authority (host) details e.g. 'nnnn-nnnn-nnnn-nnnn'  (as per the value returned by the ORCID API)

===User Object===
*new field named 'orcid', type 'Orcid' to store the value of the ORCID id for that user

====Suggested fields====
*'orcid_auth_code', type text - to hold the long authorisation token returned by the ORCID API at the end of a successful OAuth2 process
*'orcid_granted_permissions', type text - to hold the permissions granted via the ORCID API during the authorisation process
*'orcid_token_expires', type time - to hold the expiry timestamp for the authorisation code above (time now plus expires duration returned by the ORCID API)
*'orcid_last_update_timestamp', type text - to hold the timestamp of the last time the user's ORCID record was processed, to enable quicker reprocessing in the future.
*'orcid_webhook_ref', type text - to hold the value provided when configuring the webhook notification to validate new notifications have come from ORCID

Also potential fields for requested permissions .e.g. boolean flags or text to capture auth codes if individual permissions captured separately? (e.g. Peter West work)

===Eprints Contributors (e.g. creators, editors)===
*new sub-field of contributor_orcid  (e.g. creator_orcid, editor_orcid) type 'Orcid' to store the value of the ORCID id for that contributor