Skip to main content
  • Subscribe by RSS
  • ExLibris Dev

    Summon: Support for RDA Guidelines in MARC21

    • Product: Summon

    What is the current level of support for RDA data in the Summon service?

    We expect to make incremental changes as we incorporate Resource Description and Access (RDA) data into the Summon service, and of course we welcome feedback from our clients as you make the shift to RDA.
    For the time being, we have determined the following:
    • In general, as appropriate, we are mapping new MARC fields to Summon fields as requested by clients.
    • Going forward, we have changed our default field mappings as outlined below. We will also change mappings for all current clients; we hope these changes will be complete in early April 2013. If your library does not use the RDA guidelines or any of the newly added MARC fields, the changes will be in place but they will not affect your Summon instance. However, by making these changes now, we will ensure that -- if RDA records are added to your catalog at some future time -- the new RDA fields will be used appropriately in Summon. You only need to contact us if you will have the following fields in your records but you prefer not to incorporate our default mapping changes. In that case, please contact us with the Support Portal option:
      • For Publication data, we will add field 264 with second indicators to try to map only Publisher information to this field (not Manufacturer, Distributor, etc.). We believe that ignoring the first indicator will usually map the first Publisher, which is sufficient for most records.
        • Publication Place: 260$a, 264--1$a
        • Publisher: 260$b, 264--1$b
          Summon will use the first value found with this order of priority.
        • Publication Date: 260$c, 264--1$c, 264--4$c
          Summon will use the first value found with this order of priority.
  • We will also add 380$a, Form of Work, to the mapping for Genre.
  • Because Summon currently maps each record to only one content type, the new 3xx fields will not figure in our default content type mappings, which will continue to use mostly Leader and control-field values. However, we will certainly use the new 3xx fields for custom mappings if appropriate.
  • Product management is currently investigating how best to use new relationship data from 1xx/7xx$e, but we have not established a timeline for changes.

    • Date Created: 9-Feb-2014
    • Last Edited Date: 20-Feb-2014
    • Old Article Number: 8858
    // feedback widged