Page Comparison

Library and Uploader is modified to support uploading and processing of marc files with .mrc extensions. In order to translate a marc record into a format this is recognized by the LUNA Library, mappings must be properly specified in the collection's schema for each of the fields that will hold data from the fields in the Marc record. Certain limitations are imposed on the structure of the cataloging template to facilitate transition of data from MARC Format, which will be discussed below.

Brief MARC format summary:

1. Control Fields-Control numbers and other kinds of control and coded information that are used in the processing of machine-readable bibliographic records. These fields have no subfield codes. These fields do not repeat.

...

2. Data Fields-are further divided into into subfields using a single letter or number designation (e.g $a). Subfields are where data values are located. Data Fields and SubFields are repeatable. To find out if a certain field is repeatable, check:

http://www.loc.gov/marc/bibliographic/

How to specify a mapping:

To specify a mapping for a field, add a <marc_mapping> element directly under the <field> element for the targeted field, specify a value for the marc mapping, either a 3-digit number for Marc control fields (e.g. 005), or a 3-digit number followed by the subfield code for Subfields (e.g. 949$a)

      <entity eType="Dependent" name="title" order="2">
        <display_name>Title</display_name>
        <field fType="String" name="title" order="1">
          <marc_mapping>245$a</marc_mapping>
          <display>true</display>
          <display_name>Title</display_name>
          <is_required>false</is_required>
          <searchable>true</searchable>
          <sortable>true</sortable>
          <text_box_type>Single</text_box_type>
          <validation>
            <is_required>false</is_required>
            <max_length/>
            <min_length/>
            <regexp/>
          </validation>
        </field>
      </entity>

Limitations on cataloging template structure:

1. Since many Data fields are repeatable, it is required that fields that are mapped to them be placed inside of a field group. Furthermore, field groups should contain fields that are mapped to Marc subfields of the SAME Marc Data field. For example, a field group named 'Description' contains fields 'Extent' and 'Dimensions', if 'Extent' is mapping to '300$a', then 'Dimensions' must be mapped (if there's a mapping at all) to a subfield in the 300 data field, such as '300$c'.

...