To fully support ORCID functionality we need lots of metadata about the ORCID - namely put codes and provenance information.
For this to work out of the box with ORCID plugins, and to avoid adding too many new fields to the creator/editor/etc. fields, we need a new datastructure that mirrors the creator fields, and allows put codes/provenance information to be stored on a per-creator basis.
This field would not appear in the workflow and all values will be derived automatically. It needs to reflect any changes made to the creators field (which can be keyed off the ORCID field!)
To fully support ORCID functionality we need lots of metadata about the ORCID - namely put codes and provenance information.
For this to work out of the box with ORCID plugins, and to avoid adding too many new fields to the creator/editor/etc. fields, we need a new datastructure that mirrors the creator fields, and allows put codes/provenance information to be stored on a per-creator basis.
This field would not appear in the workflow and all values will be derived automatically. It needs to reflect any changes made to the creators field (which can be keyed off the ORCID field!)