Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Appendix A: Field Mapping from Primo PNX to Leganto Citations

    Translatable

    Mapping from Primo to Leganto

    For more information about the integration between Leganto and Primo, see the developer's network documentation and Configuring Search Repository.
    You can view and edit the default mapping between Primo PNX fields and Leganto citation fields on the Leganto Primo Mapping mapping table (Configuration Manu > Leganto > Discovery > Primo Mapping). For more information about mapping tables, see Mapping Tables.
    On this table, you can change the source Primo PNX fields for Leganto citation fields and you can add or delete additional, secondary source fields to map to Leganto fields, as follows:
    • You cannot edit the Leganto citation fields. For a list of these fields, see the Field Mapping between Primo PNX and Leganto Citations table, below.
    • Field names are case sensitive.
    • Adding a line on this page is only useful for providing additional sources to map to the Leganto fields already listed on this page (there is no possibility to map to fields not listed on this page or create new Leganto fields). To do this, use <Leganto field code>#<order>. For example, the Leganto field publisher#2 is used for Leganto's Publisher field if there is no value for the Primo field mapped to publisher. If there is also a publisher#3, it will be used for Leganto's Publisher field if there is no value for the Primo fields mapped to publisher and publisher#2.
    • Enter concat in the Operation column to concatenate all values in the Primo field. If concat is not entered in this column and more than one value is found in the Primo field, only the first values is mapped to the Leganto field. If concat_mapping_fields (Configuration Menu > Leganto > Discovery > Primo Settings) is set to true, all values mapped to the same field are concatenated.

    concat.png

    Concat multiple fields
    The following table presents the default mapping between Primo PNX fields and Leganto citation fields. The Search Results column indicates the fields that appear in the list of search results; search results in Leganto including information from Primo (using the Primo API). The Brief Display column indicates the fields that appear for the citation when viewing the reading list for books, articles, or both (note that there are other materials types, see Configuring Citation Material Types). The Full Display column indicates the fields that appear when viewing the citation details. all concatenated fields are outputted.
    Field Mapping between Primo PNX and Leganto Citations
    Primo PNX Section Primo PNX Field Citation Field Code Citation Field Name Search Results Brief Display (Article/Book) Full Display
    addata btitle book_title Book Title Y Book Chapter Y
    display contributor rlterms_additionalPersonName Additional Person Name   Both Both
    rlterms_editor Editor   Book Chapter Y
    display creator creator Author (Editor) Y Both Both
    rlterms_chapter_author Chapter Author Y Book Chapter Y
    addata doi doi DOI     Both
    display edition rlterms_edition Edition Y Book Book
    addata epage end_page End Page Y Both Both
    addata isbn identifier_isbn ISBN Y   Book
    addata issn identifier_issn ISSN Y   Article
    addata issue rlterms_issue Issue Y Article Article
    addata jtitle rlterms_journalTitle Journal Title Y Article Article
    addata lccn lcc_number LCCN Number     Book
    addata notes rlterms_note Note   Both Both
    addata oclcid oclc_number OCLC Number     Book
    addata pages rlterms_pages Pages   Both (if no start/end page) Both
    addata cop rlterms_placeOfPublication Place of Publication   Book Both
    addata date date Publication Date Y Both Both
    addata pub publisher Publisher Y Book Book
    display publisher publisher#2 Publisher (if addata/pub is empty) Y Book Book
    addata spage start_page Start Page Y Both Both
    display title title Title Y Both Both
    rlterms_chapter_title Chapter Title Y Book Chapter Y
    addata volume volume Volume Y Article Article
    search creationdate rlterms_year Year   Book Book
    In addition, search:addsrcrecordid is required for the display of alternate (physical) editions and alternate (electronic) formats of a citation linked to a physical resource. See Configuring the Display of Other Formats and Editions of Citations.
    Changes to this table only apply for newly created citations.

    Mapping from Primo Subfields 

    The mapping table Leganto Primo Mapping allows you to map information from a specific subfield in a PNX field and to utilize regular expressions to match information in the subfield. This may be useful when mapping thumbnail images from Primo citations so that they display in the Leganto Reading Lists.

    To map all or a portion of a specific subfield of a PNX field from Primo to Leganto, specify the following columns: 

    • Subfield – The subfield that contains the data that you want to map from Primo.

    • Regexp – A regular expression that describes the value for which you are matching. If the value does not match this regexp, the value will not be taken. For example, the following regexp matches any value that ends with jpg: .*.jpg

    LGTO_LegantoPrimoMappingMT.png

    Leganto Primo Mapping Page

    For example:

    If the PNX record for the citation contained the following image links, but you want to map the image that is stored in the $$U subfield (not the $$T subfield) to the Thumbnail URL field in Leganto:

    <links>

         <thumbnail>$$Tgoogle_thumb</thumbnail>

         <thumbnail>$$Uhttps://media.boknett.no/objects/53/productimage_1234987.jpg</thumbnail>

    </links>

    Specify the following fields to create a mapping row on the Leganto Primo Mapping page

    • Leganto Field – originalThumbnail

    • Primo Section – links

    • Primo Field – thumbnail

    • Operation – concat

    • Subfield – U

    If you were looking for a specific image format, you could have specified the Regexp field.

    Primo Material Type Mapping

    For Primo customers, you can define the mapping of Primo Material Type to Leganto Material Type. For example, if a DVD item in Primo is added to Leganto, you can define the Leganto type to be dvd, video, or audio visual. The mapping table is Primo Material Type Mapping, in Leganto Configuration Menu > Discovery.

    Mapping Primo Translation Fields

    The value populated in the following citation fields is translated:

    • Creator
    • Additional person name
    • Editor

    Fields are searched for ”$$T<code>”. If the code exists, and the use_local_field_translations (Configuration > Leganto > Discovery > Primo Settings) parameter is set to true, Leganto checks the value in the Local Field Translate (Discovery > Display Configuration > Labels).

    This configuration is only applicable to Primo VE.

    • Was this article helpful?