Customizable RIS mapping table for Primo VE
In Primo, customers could customize the RIS export table, to determine what PNX fields should be used for RIS fields. In Primo VE this is not possible:
The mapping of the RIS fields to PNX fields is as follows:
IS addata/issue
TY addata/ristype
N2 addata/abstract
N1 addata/notes
PB addata/publisher
A2 display/contributor
ET addata/edition
KW display/subject
EP addata/epage
DO addata/doi
PY addata/date ; display/creationdate
JA addata/stitle
VL addata/volume
CY addata/cop
AU display/creator
T3 addata/seriestitle
T2 addata/addtitle
T1 display/title
SP Addata/spage
JF Addata/jtitle
ID Alma MMS ID
SN Addata/issn; addata/isbn; addata/eissn; addata/eisbn
As most reference managers will read A2 as Series Editor, it would be helpful if the display/contributor could be conditioned to map to AU instead. This is just one example - and why the mapping should be customizable.
Thank you for this idea . With the April 2022 release Primo VE allows you to customize the default mapping used to export records to RIS format.
-
François Renaville commented
Hi Nili,
Thanks. While checking the option to allow customization of the RIS mapping in Primo VE, I hope Ex Libris will also consider the same for BibTex and conduct your in-depth analysis on records coming from External Data Sources. For example:
- identifiers in RIS or BibTex are local Alma records identifiers (e.g. alma123456789123456), and not DOI, ISBN or ISSN while they exist in the target dc:identifier of the records
- summaries/descriptions are never exported although they exist in the target dc:description.Additionally, journals and book titles where articles (coming from External Data Sources) have been published are not exported in RIS or BibTex nor displayed in MLA, APA or Chicago styles (even if there is a dc:source). When those articles are CDI records, information is displayed. Libraries should also know what is the recommended matching for target DC in Primo VE in order to get the best results as possible for records coming from External Data Sources. Thanks.
-
Lori Stethers commented
Adding my votes. In particular, we want to be able to export to RIS fields that aren't included in the PrimoVE export mapping and map local fields to those. CN (call number) is our highest priority to customize.
-
François Renaville commented
Thanks for the idea! I would like to add that the quality of RIS and BibTex exports for local records coming External Data Sources is terrible. I wish a mapping table could help to improve this...