Library The LUNALibrary and Uploader is have been modified to support uploading and processing of MARC files with .mrc extensions. In order to translate a MARC record into a format that 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 Formatformat, which will be discussed below.
...
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 MARC mapping, either a 3-digit number for Marc MARC control fields (e.g. 005), or a 3-digit number followed by the subfield code for Subfields (e.g. 949$a)
...
Limitations on cataloging template structure:
1. Since many Data data fields are repeatable, it is required that the fields mapped to them be placed inside of a field group. Furthermore, field groups should contain fields that are mapped to Marc MARC subfields of the SAME Marc 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'.
...
3. Repeated subfields- if a Marc MARC record contains a data field with repeating subfields, the repeating values will be placed into the same Luna LUNA field, separated by a semicolon and followed by a space. For example, 541$a has value "Wood River Journal" and anther $a subfield in the SAME 541 data field has value "Copy costs and use fees apply", the mapped Luna LUNA field will have "Wood River Journal; Copy costs and use fees apply"
4. Use ':' to combine values in subfields- In some occasion, you may want to combine values from multiple subfields of the same Data data field. You may do so by placing more than one subfields into <marc_mapping> using colon as a separator. Data from these subfields will be concatenated and separated by a space. For example <marc_mapping>949$a:949$b:949$c:949$d:949$e</marc_mapping>.
5. Like importing data using csv or xml, at least one field in the primary entity must contain data, and since Marc MARC data fields are always in a field group (see #1 above), at least one field in the primary entity should be mapped to a Marc MARC Control field, and this field must always contain data.
...