EPrints Technical Mailing List Archive

Message: #08329

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Plan-S compliance and IDs IDs IDs plugin

Hi all,
One thing that John, Rory and I identified was needed to help EPrint be fully Plan S compliant [1] was to enhance the provision for:
"Use of persistent identifiers (PIDs) for scholarly publications (with versioning, for example, in case of revisions), such as DOI (preferable), URN, or Handle."
At the moment by default EPrints can store only a single ID in the id_number field.  Typically, this is a DOI but it does not have to be an their is no consistency of what type of ID and how the ID is formatted.  Also if there are multiple IDs to store then you could add both these to the id_number field but this will prevent the render_possible_doi from working properly.  Therefore, I have written a new plugin based on the Dates Dates Dates plugin but for IDs, imaginitively named IDs IDs IDs.  This provides a compound multiple field (named ids) to store multiple IDs with their types.  It provides validators and renderers for each type of ID, currently these are: 

DOI
ISBN
PMCID
PubMed ID
ISSN (print)
ISSN (online)
ISSN
If you add the ids field to eprint_render.pl then each ID will be rendered as part of an undordered list (i.e. ul HTML element). There is also a pre-commit hook that will take the values in id_number, issn and isbn and do its best to add it as IDs with the appropriate types to the ids field. This allows for a "epadmin recommit" to initial populate the ids field so the old fields can be disabled in the workflow.  It will also back fill IDs added to the ids fields into these original fields, if these are used elsewhere in EPrints or for exports to third-party applications. It uses a set of ID priorities in the order of IDs shown above to work out the most important ID to backfill into the id_number and/or issn field.
I have added this new plugin to a public GitHub repository [2], so people can submit issues and pull requests if they wish to develop it further.  I have also added an under development version (0.1) of the plugin to the Bazaar [3].  Comments, suggestions and bug reports are welcome, so that I can ensure that the plugin is robust and works for most people's scenarios. 

Regards

David Newman

[1] https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FPlan_S&amp;data=01%7C01%7C%7C7ffd2b02abb84cfab52608d85efc3082%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=BgeJgmewITLo0i7a4t9Rz22LmTyqLiMIuP%2BL0%2FBs2L0%3D&amp;reserved=0
[2] https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feprints%2Fidsidsids&amp;data=01%7C01%7C%7C7ffd2b02abb84cfab52608d85efc3082%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=RKYonWs5Zyb7nwltlDBB11LC0PuTi4qVVdWiSmoLzNU%3D&amp;reserved=0
[3] https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbazaar.eprints.org%2F1149%2F&amp;data=01%7C01%7C%7C7ffd2b02abb84cfab52608d85efc3082%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Yap3hWnz8kVgJDcNsCpk7U%2FwF7myk%2BMIZLuHZSHY9eU%3D&amp;reserved=0

--
This email has been checked for viruses by AVG.
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.avg.com%2F&amp;data=01%7C01%7C%7C7ffd2b02abb84cfab52608d85efc3082%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=MeTyKRzxRrGGkLmMJZiyKlqu8wGUNGLlJAdAwh8biw0%3D&amp;reserved=0