Currently the only option to add bespoke mappings are for item types. There could be any amount of bespoke fields or custom mappings needed depending on how an EPrints repo has been setup and customized. This can be solved by calling out to a config level function which can manipulate the current mapping or write their own from scratch, allowing for better integration.
DOI usage should probably be standard, as this is one of the ways orcid determines duplication.
The changes made in this commit are not breaking.
Currently the only option to add bespoke mappings are for item types. There could be any amount of bespoke fields or custom mappings needed depending on how an EPrints repo has been setup and customized. This can be solved by calling out to a config level function which can manipulate the current mapping or write their own from scratch, allowing for better integration.
DOI usage should probably be standard, as this is one of the ways orcid determines duplication.