Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    Configuring Cataloging

    Translatable
    To configure the metadata environment, you must have one the following roles:
    This section is about configuring the metadata environment. The profiles configured in the Active Profiles section of the Metadata Configuration List page define the cataloging environment you use when working in the MD Editor. The bibliographic profiles available for you to configure on the Metadata Configuration List page is determined by the Active Registry/Registries set for your institution by Ex Libris. The following Active Registries can be configured for Alma:
    • MARC 21
    • UNIMARC
    • KORMARC
    • CNMARC
    • Dublin Core
    This section describes configuring the following characteristics of the MD Editor:
    • Which metadata fields and subfields appear in the metadata editor and if they are repeatable
    • If the subfields use a controlled vocabulary
    • Normalization processes
    • Validation processes
    You configure the metadata fields from the options provided on the Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Metadata Configuration).
    Metadata Configuration List Page
    See Working with Authority Records for additional information related to global and local authority records in Alma.

    Viewing a List of Metadata Profiles

    The Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Metadata Configuration) displays a list of metadata profiles that are defined for the institution, a link to each profile, and the following information (when available) for each profile:
    • Vocabulary
    • Family
    • Type
    • Usage
    • Updated on (date)
    Metadata Configuration List Page

    Viewing Metadata Profile Details

    The Profile Details page provides the following tabs for viewing (and customizing) fields, normalization processes, and validation processes:
    • Fields
    • Normalization Processes
    • Validation Processes
    • Validation Exception Profile List
    To view the details of a metadata profile:
    1. On the Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Metadata Configuration), click the name of the profile you want to view.
      The Profile Details page appears.
      MARC 21 Bibliographic Profile Details Page
    2. Select Actions > View for the profile details you want to view. The Field Details page appears.
      Field Details Page
    3. Click Back to return to the Profile Details page.

    Editing Profile Details

    You can modify the details of a metadata profile using the options provided in the following tabs on the Profile Details page:
    Profile Details Page
    In addition, you can modify the metadata profile using extension packs. Refer to Editing MARC-Based Profiles with Extension Packs for more information.

    Editing Fields

    From the Fields tab on the Profile Details page for a specific metadata configuration profile, you can edit (Actions > Customize) the fields of a metadata profile as described in the To edit fields: procedure below.
    The fields that are available to edit are determined by profile link/type (bibliographic, holdings, authority, or Qualified Dublin Core) that you select on the Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Metadata Configuration).
    A field's subfield that is used for authority suggestions (F3) cannot be customized. The Assign Controlled Vocabulary option is not provided for editing that subfield (see the illustration below). See the Linking an Authority Record to a Bibliographic Record section for more information.
    Assign Controlled Vocabulary Option Unavailable
    To edit fields:
    This procedure describes the procedure for editing bibliographic fields. The procedure is similar for holdings, authority, and Qualified Dublin Core.
    1. On the Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Metadata Configuration), click the name of the profile you want to edit. The Profile Details page appears.
      Profile Details Page
    2. Locate the field you want to edit using the Filter drop-down list or the Find search option to locate a specific Field or Description.
    3. Select Actions > Customize for the field you want to edit. The Field Details page appears.
      Field Details Page
    4. Edit the following field options (which may vary) to match your requirements:
      • Mandatory – Yes or No.
      • Repeatable – Yes or No.
      • Description – Details for your reference.
      • Help URL – A URL that can be used for help.
        The help information that this URL points to appears on the Info tab in the MD Editor.
        MD Editor Info Tab Related to the Help URL Option
      • Subfields – Click the plus sign to expand this section. For each subfield, you can select from the drop-down list (Yes/No) to identify that the subfield is mandatory or repeatable.
      • Click Assign Controlled Vocabulary for the subfield to which you want to assign a specific controlled vocabulary. The Profile Details page with the Create New CV Value section appears.
        Subfields Section Expanded
        Assign Controlled Vocabulary
      • Select a controlled vocabulary (CV) from the Choose Controlled Vocabulary drop-down list. The options in this list are configured in the Configuring Controlled Vocabulary Registry. The details of the controlled vocabulary that you select appear. Click Assign to save this selection.
      • For your convenience, you may use the Create New CV Value section to add controlled vocabulary terms. The terms that you add here only apply to the field that you are editing. If you want to use these terms with another/different field, use the Controlled Vocabulary Registry (see Configuring Controlled Vocabulary Registry) to create a CV that may be used for more than one field.
        To add a new controlled vocabulary value in the Create New CV Value section, enter a code and description and click Add. When you are finished adding terms, click Assign.
      • First Indicator – In the First Indicator section on the Field Details page, make any required changes.
      • Second Indicator – In the First Indicator section on the Field Details page, make any required changes.
    5. Click Save. The field changes are saved in the metadata profile.
    6. Click Deploy.

    Restoring Profile Field Details

    You can restore the profile details to the default values.
    To restore the default profile field details:
    1. On the Metadata Configuration List page, click the link in the Profile column for the profile that contains the field you want to restore. The Profile Details page opens on the Fields tab.
      Profile Details Page
    2. Select Actions > Restore for the profile details that you want to restore. The profile change that was locally customized is restored to the field’s default value.
    3. Click Deploy.

    Controlling the Display and Access of Global Authorities in the MD Editor

    The capability described in this section is specific to institutions that have had their authority usage policy configured by Ex Libris for local authorities.
    Support is provided for controlling which global authorities can be viewed and/or accessed in the MD Editor. This support is managed through your Resource Management metadata configuration options on the Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu > Cataloging section > Metadata Configuration) where you can tailor the display of authority record options for your work in the MD Editor. When your system is configured for working with local authority records, the Authority Vocabularies section of the Metadata Configuration List page provides the following additional columns:
    • Managed Locally
      The Managed Locally column allows you to identify which authority vocabularies you want to display in the MD Editor. In order to do this, you may activate or deactivate the check marks in this column for both local authority vocabulary rows and Community Zone authority vocabulary rows.
    • Managed in Community
      The Managed in Community column identifies the vocabularies that are maintained in the Community Zone. This column is for informational purposes only. There is no option to activate/deactivate the check marks in this column.
    Metadata Configuration List Page
    For institutions that want to limit the number of options in the MD Editor that appear to only those authority vocabulary options that are commonly used versus all that might be available, the Managed Locally column allows you to do that.
    In addition to the MD Editor, the selections that you make in the Managed Locally column also determine which authority vocabularies appear in the import profile. Specifically, these selections affect the following areas:
    • Templates and Records tabs in the MD Editor
    • File > New record options in the MD Editor
    • Vocabulary code parameter's drop-down list of options on the Import Profile Details page
    To change the global and local authority vocabularies that appear in the MD Editor:
    1. Open the Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu > Cataloging section > Metadata Configuration). The Metadata Configuration List page appears.
      Metadata Configuration List Page
      With the Managed Locally column configured as shown above, the File > New options list in the MD Editor displays the following authority vocabulary options:
      Authority Vocabulary Options in the MD Editor
    2. Select the check marks in the Managed Locally column to identify the vocabularies that you want to appear in the MD Editor (and the Import profile).
      See the figures below that illustrate removing the RVK authority vocabulary selection.
      RVK Selection Removed
      RVK Option Removed

    Editing MARC-Based Profiles with Extension Packs

    Extension packs for the metadata profiles enable you to adapt MARC-based bibliographic, holdings, and authority profiles with additional fields, subfields, and indicator values, repeating/nonrepeating and mandatory/nonmandatory specifications and URLs for online help for regional needs. This includes the MARC 21, UNIMARC, and CNMARC profiles (but not Dublin Core). With these MARC profile extension packs, you can load and use regional adaptations to the MARC standard.
    See Extension Pack .xsd for the extension pack schema and the Extension Pack .xml File Example for additional information and an example .xml file.
    Fixed position fields (control fields) cannot be modified using extension packs.
    To add an extension pack:
    1. Create a .xml extension file (see Extension Pack .xml File Example for more information).
    2. Click the link for the profile you want to extend on the Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Metadata Configuration).
      For this example, the MARC21 Bibliographic link is used. The Profile Details page appears with the Add Extensions and Remove Extensions buttons.
      Profile Details Page with Add/Remove Extensions Buttons
    3. Click Add Extensions. The Add Extensions File page appears.
      Add Extensions File Page
    4. Browse for/insert the .xml extension file that you previously created/saved and click Add Extensions. When processing is complete, the system displays a confirmation message.
      Successfully Loaded Confirmation Message
      If during processing the system encounters more than one occurrence of the same value, the first occurrence is applied and the other redundant occurrences are ignored.
    5. Review/confirm your changes. For the rows (fields) that you have modified, the Actions menu provides View, Edit, and Restore options.
      New Actions for Modified Rows
      For the rows that have not been modified, the Actions menu continues to display the View and Customize options (provided with the original metadata profile settings).
    6. Click Deploy.
    To remove all extended values and restore the original metadata profile:
    1. Click the link for the profile from which you want to remove the extension on the Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Metadata Configuration).
      For this example, the MARC21 Bibliographic link is used. The Profile Details page appears with the Add Extensions and Remove Extensions buttons.
      Profile Details Page with Add/Remove Extensions Buttons
    2. Click Remove Extensions and click Confirm in the confirmation dialog box. When processing is complete, the system displays a confirmation message.
      Successfully Removed Message
    3. Click Deploy.

    Extension Pack .xsd

    See the .xsd file below that identifies the fields, subfields, indicators, and the values or characteristics that can be specified in the extension pack .xml file.
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="qualified" targetNamespace="http://com/exlibris/repository/mdprofile/xmlbeans"
    xmlns="http://com/exlibris/repository/mdprofile/xmlbeans">

    <!-- marc_profile element definition -->
    <xs:element name="marc_profile">
    <xs:complexType>
    <xs:sequence>
    <xs:element ref="leader_configuration" minOccurs="1"
    maxOccurs="1" />
    <xs:element ref="control_fields_list" minOccurs="1"
    maxOccurs="1" />
    <xs:element ref="data_fields_list" minOccurs="1"
    maxOccurs="1" />
    </xs:sequence>
    </xs:complexType>
    </xs:element>

    <!-- XSD element definition -->
    <!-- leader element definition -->
    <xs:element name="leader_configuration">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="positions_list" minOccurs="1"
    maxOccurs="1" type="positionsListType" />
    </xs:sequence>
    </xs:complexType>
    </xs:element>

    <!-- control_fields_list element definition -->
    <xs:element name="control_fields_list">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="control_field_configuration" minOccurs="0"
    maxOccurs="unbounded">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="description" minOccurs="1"
    maxOccurs="1" type="xs:string" />
    <xs:element name="help_url" minOccurs="0"
    maxOccurs="1" type="xs:string" />
    <xs:element name="materials_type_list" minOccurs="1"
    maxOccurs="1" type="materialstypeListType" />
    </xs:sequence>
    <xs:attribute name="tag" type="tagType" use="required" />
    <xs:attribute name="repeatable" type="xs:boolean"
    use="required" />
    <xs:attribute name="mandatory" type="xs:boolean" use="optional" />
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>

    <!-- data_fields_list element definition -->
    <xs:element name="data_fields_list">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="data_field_configuration" minOccurs="0"
    maxOccurs="unbounded">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="description" minOccurs="1"
    maxOccurs="1" type="xs:string" />
    <xs:element name="help_url" minOccurs="0"
    maxOccurs="1" type="xs:string" />
    <xs:element name="first_indicator_configuration" type="indicatorType"
    minOccurs="0" maxOccurs="1" />
    <xs:element name="second_indicator_configuration"
    type="indicatorType" minOccurs="0" maxOccurs="1" />
    <xs:element name="sub_fields_list" minOccurs="0"
    maxOccurs="1" type="subfieldType">
    <xs:key name="sub_field_configuration-unique">
    <xs:selector xpath="sub_field_configuration" />
    <xs:field xpath="@code" />
    </xs:key>
    </xs:element>
    </xs:sequence>
    <xs:attribute name="tag" type="tagType" use="required" />
    <xs:attribute name="repeatable" type="xs:boolean"
    use="required" />
    <xs:attribute name="mandatory" type="xs:boolean" use="optional" />
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>

    <!-- XSD complex type definition -->
    <xs:complexType name="positionsListType">
    <xs:sequence>
    <xs:element name="position_configuration" type="positionType"
    minOccurs="0" maxOccurs="unbounded" />
    </xs:sequence>
    </xs:complexType>

    <xs:complexType name="positionType">
    <xs:sequence>
    <xs:element name="description" minOccurs="1" maxOccurs="1"
    type="xs:string" />
    <xs:element name="values" minOccurs="1" maxOccurs="1"
    type="valuesType" />
    </xs:sequence>
    <xs:attribute name="start" type="customIntegerType" use="required" />
    <xs:attribute name="end" type="customIntegerType" use="required" />
    </xs:complexType>

    <xs:complexType name="valuesType">
    <xs:sequence>
    <xs:element name="value" minOccurs="0" maxOccurs="unbounded">
    <xs:complexType>
    <xs:simpleContent>
    <xs:extension base="xs:string">
    <xs:attribute name="code" type="codeType" use="required" />
    </xs:extension>
    </xs:simpleContent>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>

    <xs:complexType name="subfieldValuesType">
    <xs:sequence>
    <xs:element name="value" minOccurs="0" maxOccurs="unbounded">
    <xs:complexType>
    <xs:simpleContent>
    <xs:extension base="xs:string">
    <xs:attribute name="code" type="codeType" use="required" />
    </xs:extension>
    </xs:simpleContent>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    <xs:attribute name="codeTable" type="xs:string" />
    </xs:complexType>

    <xs:complexType name="indicatorType">
    <xs:sequence>
    <xs:element name="description" minOccurs="1" maxOccurs="1"
    type="xs:string" />
    <xs:element name="values" minOccurs="1" maxOccurs="1"
    type="valuesType" />
    </xs:sequence>
    <xs:attribute name="mandatory" type="xs:boolean" use="optional" />
    </xs:complexType>

    <xs:complexType name="subfieldType">
    <xs:sequence>
    <xs:element name="sub_field_configuration" minOccurs="0"
    maxOccurs="unbounded">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="description" minOccurs="1" maxOccurs="1"
    type="xs:string" />
    <xs:element name="values" minOccurs="0" maxOccurs="1"
    type="subfieldValuesType" />
    <xs:element name="materials_type_list" minOccurs="0"
    maxOccurs="1" type="materialstypeListType" />
    </xs:sequence>
    <xs:attribute name="code" type="subfieldCodeType" use="required" />
    <xs:attribute name="repeatable" type="xs:boolean" use="required" />
    <xs:attribute name="mandatory" type="xs:boolean" use="optional" />
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>

    <xs:complexType name="materialstypeListType">
    <xs:sequence>
    <xs:element name="material_type_configuration" minOccurs="0"
    maxOccurs="unbounded" type="materialtypeType">
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    <xs:complexType name="materialtypeType">
    <xs:sequence>
    <xs:element name="positions_list" minOccurs="1" maxOccurs="1"
    type="positionsListType" />
    </xs:sequence>
    <xs:attribute name="name" type="xs:string" use="required" />
    </xs:complexType>

    <!-- XSD simple type definition -->
    <xs:simpleType name="tagType">
    <xs:restriction base="xs:string">
    <xs:pattern value="[0-9]{3}" />
    </xs:restriction>
    </xs:simpleType>
    <xs:simpleType name="customIntegerType">
    <xs:restriction base="xs:string">
    <xs:pattern value="[0-9]+" />
    </xs:restriction>
    </xs:simpleType>

    <xs:simpleType name="codeType">
    <xs:restriction base="xs:string">
    <xs:pattern value="[a-z#0-9|]+" />
    </xs:restriction>
    </xs:simpleType>
    <xs:simpleType name="subfieldCodeType">
    <xs:restriction base="xs:string">
    <xs:pattern value="[a-z0-9]{1}" />
    </xs:restriction>
    </xs:simpleType>
    </xs:schema>

    Extension Pack .xml File Example

    See the .xml file below for an example of an extension pack file that can be applied to a metadata profile.
    Manually, not using extension packs, you can modify existing field information (Actions > Customize from the Fields tab on the Profile Details page) as shown in the illustration below.
    Field Details Page
    Field Details Page Expanded
    With the extension pack .xml file, you can add extra values (fields, subfields, and indicators) that are not part of the formal standard and update existing values (that are defined as part of the standard or that have been defined as part of a previous Add Extensions load) consistent with the schema identified in the .xsd above (in Extension Pack .xsd).
    The extension pack enables you to create multiple unique extensions to the metadata profile so that extensions do not need to be included in a single file. You can load more than one extension pack .xml file. Each additional file that you load with the Add Extensions capability will only customize the fields specified in the additional file. If a field was previously customized by an extension pack .xml file and it is defined/customized in a subsequent extension pack .xml file that is added to the metadata profile, that field’s customization is overridden to reflect the most recent .xml file added.
    For cases in which institutions may want to share a common regional extension pack .xml file, the Ex Libris Developer Network provides the facility for sharing these files.
    <?xml version="1.0" encoding="UTF-8"?>
    <marc_profile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation="marc21_profile_configuration.xsd">
    <control_fields_list>
    <control_field_configuration mandatory="true" repeatable="false"
    tag="003">
    <description>PERSISTENT RECORD IDENTIFIER</description>
    <materials_type_list />
    </control_field_configuration>
    </control_fields_list>
    <data_fields_list>
    <data_field_configuration repeatable="true" mandatory="false" tag="020" xmlns="http://com/exlibris/repository/mdprofile/xmlbeans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <sub_fields_list>
    <sub_field_configuration code="9" mandatory="false" repeatable="true">
    <description>Former ISBN
    </description>
    </sub_field_configuration>
    </sub_fields_list>
    </data_field_configuration>
    <data_field_configuration repeatable="true" mandatory="false" tag="024" xmlns="http://com/exlibris/repository/mdprofile/xmlbeans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <sub_fields_list>
    <sub_field_configuration code="9" mandatory="false" repeatable="true">
    <description>Former ISSN
    </description>
    </sub_field_configuration>
    </sub_fields_list>
    </data_field_configuration>
    <data_field_configuration repeatable="false" mandatory="false" tag="689" xmlns="http://com/exlibris/repository/mdprofile/xmlbeans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <description>SUBJECT HEADING CHAIN</description>
    <help_url>http://www.google.com</help_url>
    <first_indicator_configuration>
    <description>Type of subject heading chain</description>
    <values>
    <value code="0">Simple chain</value>
    <value code="1">Complex chain</value>
    </values>
    </first_indicator_configuration>
    <second_indicator_configuration>
    <description>Undefined</description>
    <values>
    <value code="#">Undefined</value>
    </values>
    </second_indicator_configuration>
    <sub_fields_list>
    <sub_field_configuration code="a" mandatory="true" repeatable="false">
    <description>Heading chain first element
    </description>
    </sub_field_configuration>
    <sub_field_configuration code="b" mandatory="false" repeatable="true">
    <description>Heading chain second element</description>
    </sub_field_configuration>
    <sub_field_configuration code="c" mandatory="true" repeatable="true">
    <description>Type of chain</description>
    <values>
    <value code="0">GND chain</value>
    <value code="1">DNB chain</value>
    </values>
    </sub_field_configuration>
    </sub_fields_list>
    </data_field_configuration>
    </data_fields_list>
    </marc_profile>

    Working with Normalization Processes

    Normalization processes are used to correct or update metadata records such as sorting a record’s fields, removing empty fields, or stripping out fields containing order information. Normalization processes can also be created to handle CJK transliterations in the MD Editor. After creating a normalization process, the process can be applied while cataloging in the MD Editor or by running a job that uses this process.
    Records added using an automated process, such as using an API or through a patron purchase request, are first normalized by the Default template, before being processed by any relevant normalization processes. See Working with Templates.
    You can perform the following actions in the Normalization Processes tab on the Profile Details page (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Metadata Configuration and click one of the profile links such as MARC21 Bibliographic):
    • Create a customized normalization process – Click Add Process to create a normalization process.
      Create Process with Add Process Button
      The Process Details wizard steps you through the options.
      Shared (or Private) normalization rules defined and saved in the MD Editor from the Rules tab (refer to Working with Normalization Rules) using MARC Drool Normalization syntax are selectable options when you create a process that uses the MarcDroolNormalization process from the Process List Pool section. See the following figures for an illustration of this relationship.
      Normalization Rules Created with the MD Editor
      Normalization Rules Created in the MD Editor are Selectable in Process Details
      See the To add a process: procedure below for step-by-step details regarding how to create a process.
      After a new process is saved, it becomes available to run as a job.
      Normalization jobs have type MARC 21 Bib normalization. See Running Manual Jobs on Defined Sets for more information.
    • Edit a normalization process – Select Actions > Edit. The settings for an existing normalization process appear on the following tabs:
      • General Information
      • Task List
      • Task Parameters
      Tabs Containing the Settings of Existing Processes
    • Copy a normalization process – Select Actions > Copy.
    • Disable a normalization process – If the normalization process is not currently required but may be required in the future, you can disable it by clicking the process’ yellow check mark. The check mark turns gray to indicate that the rule is disabled. (To re-enable it, click the gray check mark.)
      Profile Details Page, Normalization Processes Tab
    • Delete a normalization process – Select Actions > Delete.
    To add a process:
    1. In the Normalization Processes tab on the Profile Details page (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Metadata Configuration; click Profile Link), click Add Process. The first page of the wizard appears.
      Process Details Page
      Optionally, you can also create processes by selecting on the Process List page (Resource Management > Resource Configuration > Configuration Menu > General > Processes).
      If you want to create a copy of an existing process, select Actions > Copy. Once you have copied the process, you can edit it as needed.
    2. In the General Information section:
      • Enter the name and description for the process. These values will be visible to users on the Process List page.
      • In the Status field, select whether the process is available (Active) or not. A process that is inactive can be stored and edited in the system without being run. It can be made active at any time.
    3. Click Next. The next page of the wizard appears.
    4. In the Process List Pool area, select one or more processes/tasks.
      Select Processes from the List Pool
      This page (and also the Task List tab when editing saved processes) contains a predefined pool of tasks that you can include in your process (or task chain). You cannot define additional tasks and most of these tasks have fixed parameters. The MARC Drool Normalization task allows you to select the MARC Drools Normalization rules that you created in the MD Editor (refer to Working with Normalization Rules).
      The table below describes the processes in the Process List Pool section. Depending on the metadata configuration that you are editing, the processes available in the Process List Pool section vary.
      Process List Pool Options
      Process Name Description
      852 field normalization Runs a task that takes the control number from the bibliographic record and places it in the correct subfield in the holdings record.
      Add Hanja to Hangul Transliterations Converts content such as a title from Hanja to Hangul by configuring source and target fields as shown below. For more information, see Working with CJK Transliterations in Cataloging. This transliteration process can be used for MARC21 Bibliographic and MARC21 Authority configurations plus any variety of MARC configurations such as KORMARC, UNIMARC, CNMARC, and so forth.
      Add Hanja to Hangul CK Transliterations Converts content such as a title from Hanja to Hangul CK by configuring source and target fields as shown below. For more information, see Working with CJK Transliterations in Cataloging. This transliteration process can be used for MARC21 Bibliographic and MARC21 Authority configurations plus any variety of MARC configurations such as KORMARC, UNIMARC, CNMARC, and so forth.
      Add Hanja to Hangul MOE Transliterations Converts content such as a title from Hanja to Hangul MOE by configuring source and target fields as shown below. For more information, see Working with CJK Transliterations in Cataloging. This transliteration process can be used for MARC21 Bibliographic and MARC21 Authority configurations plus any variety of MARC configurations such as KORMARC, UNIMARC, CNMARC, and so forth.
      Add Hanja to Pinyin Transliterations Converts content such as a title from Hanja to Pinyin by configuring source and target fields as shown below. For more information, see Working with CJK Transliterations in Cataloging. This transliteration process can be used for MARC21 Bibliographic and MARC21 Authority configurations plus any variety of MARC configurations such as KORMARC, UNIMARC, CNMARC, and so forth.
      Add Hanzi to Pinyin Transliterations
      Converts Chinese content to Pinyin.
      The configuration for this process requires that you specify the source and target fields/subfields as shown in the Hanzi to Pinyin illustration below.
      When the normalization is processed, the first and second indicators in the target field are the same as the indicators in the source field. The transliterated words are placed in the target field/subfield and only the words that have more than one transliteration are placed in the angle brackets < > in the target field/subfield. The cataloger can then choose the right one and delete the others.
      If content exists in the target subfield, the normalization process will overwrite it.
      Subfield deletion is not handled as part of this normalization process. To delete subfields, select a normalization process dedicated to that task.
      For more information, see Working with CJK Transliterations in Cataloging. This transliteration process can be used for MARC21 Bibliographic and CNMARC profiles.
      Add Kana to Hangul Transliterations Converts content such as a title from Kana to Hangul by configuring source and target fields as shown below. For more information, see Working with CJK Transliterations in Cataloging. This transliteration process can be used for MARC21 Bibliographic and MARC21 Authority configurations plus any variety of MARC configurations such as KORMARC, UNIMARC, CNMARC, and so forth.
      Add Kana to Romanized Kana Transliterations Converts content such as a title from Kana to Romanized Kana by configuring source and target fields as shown below. For more information, see Working with CJK Transliterations in Cataloging. This transliteration process can be used for MARC21 Bibliographic and MARC21 Authority configurations plus any variety of MARC configurations such as KORMARC, UNIMARC, CNMARC, and so forth.
      AuthorityGenerateControlNumberSequence
      Runs a task that generates a control number sequence for an authority record.
      BibGenerateControlNumberSequence Runs a task that generates a control number sequence for a bibliographic record.
      CnmarcBibAdd005Task The 005 field is added only when saving in the MD Editor.
      CnmarcBibClearEmptyFieldsTask This process runs a task that deletes the bibliographic fields that are empty.
      CnmarcBibReSequenceTask
      This process runs a task that re-sequences the bibliographic fields according to their proper order—for example, 001, 100, 200, and so forth.
      Fields between 500 and 899 are not sorted (or sorted only by hundreds).
      CnmarcBibTag100OpenDateTask If the 100 field exists, the current date is placed at the beginning of 100 $a in positions 00-07 using the YYYYMMDD format.
      CnmarcBibTag100Task Alma automatically inserts or corrects the dates in the 09-12 and 13-16 positions of the CNMARC 100 field according to the date entered in the CNMARC 210 $d (and 210 $h when it contains four consecutive digits). Additionally, the dates of 210 $d are standardized. For dates like 198? or 19?, for example, Alma replaces the question marks and spaces with "-" (hyphens).
      Create210BasedOn010
      This normalization process task adds the MARC 210 $a to the record and places the Chinese publisher in the 210 based on the ISBN in the MARC 010 $a and a table managed within Alma. After you create and save a normalization process with this task selected, you can use the Edit > Enhance the Record option in the MD Editor to update records that you are cataloging.
      Enhance the Record with Create 210 $a Based on 010 $a Normalization Process Task
      210 $a Created
      See Enhance the Record in the MD Editor - Edit Menu table on the Navigating the MD Editor page for more information.
      DcBibClearEmptyFieldsTask Runs a task that deletes the Dublin Core fields that are empty.
      DcBibResequenceTask Runs a task that resequences the Dublin Core fields according to their proper order.
      Identifying Brief Level Runs a task that calculates the brief level of a record.
      Generate Chinese Author Call Number
      Runs a task that generates a Chinese author call number that is stored in the 905 field when, for example, Edit > Enhance the Record is selected while editing a record in the MD Editor.
      This process is under construction. Author number generation routines are beginning to be added. More will be available in a future release of Alma.
      When you select this process from the Process List Pool, click Add to Selection, and click Next, the Generate Chinese Author Number section of the configuration appears in order for you to select an author number generation routine.
      Generate Chinese Author Number Section
      MARC Normalization Rules Runs the normalization rules that are selected as parameters in the Task Parameters tab.
      MARC21 Expand Holding By 863/4/5 Task Runs a task that adds an 863/864/865 summary statement holdings field.
      MARC21 Expand Holding By 866/7/8 Task Runs a task that adds a description to the 866/867/868 textual holdings fields.
      Marc21AuthClearEmptyFieldsTask Runs a task that deletes the authority fields that are empty.
      Marc21AuthResequenceTask Runs a task that resequences the authority record fields according to their proper order.
      Marc21BibClearEmptyFieldsTask Runs a task that deletes the bibliographic fields that are empty.
      Marc21BibResequenceTask
      Runs a task that re-sequences the bibliographic fields according to their proper order—for example, 001, 100, 200, and so forth.
      Fields between 500 and 899 are not sorted (or sorted only by hundreds). The 689 field (relevant for German markets only) is sorted by its indicators.
      Marc21createControlNumber Runs a task that creates a new control number from the bibliographic records’ 001 and 003 fields and places it in the 035 field.
      Marc21HoldingClearEmptyFieldsTask Runs a task that deletes the holdings fields that are empty.
      Marc21HoldingResequenceTask Runs a task that resequences the holdings fields according to their proper order.
      MarcDroolNormalization
      Runs the normalization rules that are selected as parameters in the Marc Drool Normalization section (see below) when creating a process or on the Task Parameters tab when editing a process. For more information regarding creating normalization rules see Working with Normalization Rules.
      MmsTagSuppressed Runs a task that suppresses/unsuppresses the bibliographic records from discovery according to the selected value (True/False) in the Task Parameters tab.
      MmsTagSyncExternal Runs a task that sets the synchronization policy for the bibliographic records with the external catalog according to the selected value in the Task Parameters tab.
      MmsTagSyncNationalCatalog Runs a task that sets the synchronization policy for the bibliographic records with the national catalog according to the selected value in the Task Parameters tab.
      UnimarcBibAdd005Task The 005 field is added only when saving in the MD Editor.
      UnimarcBibClearEmptyFieldsTask This process runs a task that deletes the bibliographic fields that are empty.
      UnimarcBibReSequenceTask
      This process runs a task that re-sequences the bibliographic fields according to their proper order—for example, 001, 100, 200, and so forth.
      Fields between 500 and 899 are not sorted (or sorted only by hundreds).
      UnimarcBibTag100OpenDateTask If the 100 field exists, the current date is placed at the beginning of 100 $a in positions 00-07 using the YYYYMMDD format.
      UnimarcBibTag100Task Alma automatically inserts or corrects the dates in the 09-12 and 13-16 positions of the UNIMARC 100 field according to the date entered in the UNIMARC 210 $d (and 210 $h when it contains four consecutive digits). Additionally, the dates of 210 $d are standardized. For dates like 198? or 19?, for example, Alma replaces the question marks and spaces with "-" (hyphens).
      Update originating system information Use this option to set up the Originating System Version used for version prevention when importing records with Upon match Overlay or Merge options and Consider Originating System or Ignore Originating System options selected. Records stored in the system prior to the September 2015 release, do not have the Originating System Version information. Alma provides the ability to set up this information using a process automation job with Update originating system information selected from the Process List Pool. For records imported after the September 2015 release, the Originating System and Originating System Version are added automatically.
      As you process these existing records from prior to the September 2015 release, be aware that the normalization task will not modify any records linked to the Community Zone.
      See the procedure To configure normalization for managing the Originating System and Originating System Version information: for steps regarding how to set up a process using Update originating system information.
    5. Click Add to Selection.
    6. Use the up and down arrows to arrange the order in which the tasks are to be performed.
      Added to the Processes Selected Section
    7. Click Next. The next page of the wizard appears.
      Task Parameters Tab for Normalization Process
      Depending on the processes that you selected on page 2 of the wizard, you may see none or all of the selections that you see above. For example, when you have selected CJK transliteration tasks from the Process List Pool, you may be prompted to complete source field and target field information or source field/subfield and target field/subfield information. See the examples below.
      Enter Source and Target Fields for Transliteration
      Hanzi to Pinyin Transliteration Process Source Field/Subfield and Target Field/Subfield Configuration
    8. Click Next. The next page of the wizard appears.
    9. For Marc Drool Normalization, select a normalization rule from the drop-down menu. For more information regarding working with and creating normalization rules, see Working with Normalization Rules.
      Only normalization rules that are created as shared rules in the MD Editor are displayed in the drop-down list to be selected.
    10. For the Suppressed from Discovery parameter, select True for records to be suppressed from publishing to Primo, False to allow records to be published to Primo.
    11. For the Synchronize with External Catalog parameter, select one of the following:
      • Publish bibliographic records: marks bibliographic records to be included in exports to OCLC
      • Publish holdings only: marks holdings records to be included in exports to OCLC
      • Don’t publish: marks records to be excluded from exports to OCLC
    12. Click Save. The process is added to the profile in the Alma system and is available to be run as a job (see Running Manual Jobs on Defined Sets).
    To configure normalization for managing the Originating System and Originating System Version information:
    1. On the Process List page (Resource Management > Resource Configuration > Configuration Menu > General > Processes), click Add Process.
    2. Select the following options for the parameters identified below and click Next:
      • Business Entity – Bibliographic title
      • Type – Marc 21 Bib normalization (or the UNIMARC or the KORMARC option depending on your environment)
    3. Complete the General Information section and click Next.
      Process Details Page General Information Section
    4. Select Update originating system information and click Add to Selection.
      Select Update Originating System Information, Add to Selection
    5. Click Next.
    6. Select any of the following check boxes:
      When you select a check box, you must also specify its associated parameter (if any).
      Process Details with Update Originating System Information Task
      Select Originating System and/or Originating System Version
      • Update Originating System – The originating system that you want identified in the imported record’s metadata.
        Originating System Metadata in Search Results
      • Update Originating System Version – The date that you want stored in the record’s metadata. This date is used when you select the prevent overlay/merge options in your import profile for processing record matches (see Creating/Editing an Import Profile: Match Profile). The format of this date parameter is MM/DD/YYYY. The format of the Originating System Version is YYYYMMDDhhmmss.f (where hhmmss.f is hours, minutes, seconds, and a fraction of a second and the 24-hour clock is used). When normalization occurs with this parameter specified, Alma enters YYYYMMDD000000.0. Zeroes are entered for the hhmmss.f portion of the Originating System Version.
        When using metadata import, Alma pulls the date and time (that is formatted as YYYYMMDDhhmmss.f) from the 005 control field of the imported record for the Originating System Version field. See the figure below for an example of the 005 control field and the date/time format.
        005 Control Field
        The normalization process updates the Originating System Version field according to the date entered or selected from the calendar in the Originating System Version parameter above.
        When you run a Marc 21 Bib normalization job that uses a normalization process with a date selected for the Originating System Version parameter, the date that you specify is applied to all the records in the set that you select for the job.
      • Update Existing Originating System Version Values – Whether the originating system version you selected (above) overwrites any existing version. If not selected, the existing version remains as it is.
    7. Click Save. To run the process that you just created to update the Originating System Version information on a set of records, follow the steps on the Running Manual Jobs on Defined Sets page. When you run the job, filter the list of jobs by selecting the Marc 21 Bib normalization type, to more quickly locate the process job you created.
      Normalization Job that You Created
      Optionally, you can modify/override the Originating System and/or Originating System Version parameters when you run the job.
      Override the Originating System/Originating System Version Parameters
      After the job has completed, locate the updated record(s) and confirm that the Originating System/Originating System Version information has been modified to match your settings.
      Check Originating System/Originating System Version Metadata

    Editing Validation Routines

    These are the out-of-the-box validation routines:
    • MARC21 Bib match validation – defines the way in which validation is handled when a bibliographic record match is performed during the import process or in the MD Editor
    • MARC21 Bib validation on save – defines the way in which validation is handled when importing MARC records using an import profile, copy cataloging via an external resource (such as WorldCat or LoC), and saving a bibliographic record in the MD Editor.
    You can edit these routines, but you cannot create new validation routines.
    If the routine is not currently required but may be required in the future, you can disable it by clicking the yellow check mark to the left of the routine. The check mark becomes gray to indicate that the routine is disabled. (To re-enable a routine, click the gray check mark.)
    To edit a validation routine:
    1. In the Profile Details page’s Validation Processes tab (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Metadata Configuration > [profile name]) > Validation), select Edit for the routine that you want to edit.
      Validation Processes Tab
      The Process Details page opens to the General Information tab.
      Process Details Page, General Information Tab
    2. Edit the validation details as required, selecting the tabs to access the information you want to modify.
      Task List Tab for a Validation Routine
    3. Click Save. The validation routine is saved in the Alma system.

    Working with Validation Exception Profiles

    The Validation Exception Profile List tab (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Metadata Configuration > [profile name]) > Validation Exception Profile List) displays the validation exception profiles that are used to determine the severity of the validation issues that are identified using the validation profiles (see Editing Validation Routines).
    There are two out-of-the-box validation exception profiles:
    • MARC XML Bib Import
    • MARC XML Bib Metadata Editing on Save
    The MARC XML Bib Metadata Editing on Save exception profile is used when copy cataloging via an external resource (such as WorldCat or LoC) and when saving a bibliographic record in the MD Editor. When defining an import profile, you define the validation exception profile to be used during the import. It is recommended that you select the MARC XML Bib Import exception profile to handle invalid data as it is being imported.
    Unlike validation profiles, you can define additional exception (severity) profiles. You can also edit the existing profiles or delete them (Actions > Delete).
    For information on configuring an error message to be displayed when adding 9XX fields to Network Zone records, see Preventing the Addition of Local Fields to Network Zone Records.
    To add a severity validation profile:
    1. On the Profile Details page (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Metadata Configuration > [profile name]), click the Validation Exception Profile List tab.
      If you want to create a copy of an existing Validation Exception Profile List, select Actions > Copy. Once you have copied the Validation Exception Profile List, you can modify it as needed.
      Add Severity Validation Profile Area
    2. In the Add Severity Validation Profile area, do the following:
      • Enter a name (required) and description for the severity validation profile you want to add.
      • In the Default Severity field, select the type of severity, an error or a warning.
    3. Click Add Severity Validation Profile. The profile is added to the list of Validation Exception Profiles.
    To edit a severity validation profile:
    1. On the Profile Details Page, in the Validation Exception Profile List tab, select Actions > Edit for the validation exception that you want to update.
      Validation Severity Profile Exceptions Page Edit
    2. In the General Information area, make changes to name, description, or default severity as required. The default severity determines whether violations of the field-level parameters defined in the Fields tab (for example, mandatory, non-repeatable) are treated as warnings (which can be overridden) or as errors (which must be resolved).
    3. In the Message area, select a message to be deleted, as required, and click Delete.
    4. The Add Validation Severity Exception area allows configuration of new validation exceptions. In the Message drop-down list, select a validation exception message. The syntax of the message is not configurable.
    5. Click Save. The validation exception profile is saved in the Alma system.

    Working with UNIMARC Fields, Normalization, and Validation

    Similar to the support Alma provides for MARC 21, Alma provides support for UNIMARC validation and normalization. Alma uses the settings in the validation and normalization profiles when importing records and when working with records in the MD Editor.
    For UNIMARC, additional validation function has been implemented for fixed fields (1XX) that have a subfield.
    Default normalization processes have been created for UNIMARC bibliographic record normalization. See the Process List Pool Options table for more information.
    The UNIMARC metadata profile includes the standard UNIMARC local fields. Specifically, the 9XX local fields are available in the UNIMARC profile. This includes subfields a through z and 0 through 9, plus blank and 0 through 9 values for the first and second indicators.
    To work with the UNIMARC normalization tasks:
    1. Click the UNIMARC Bibliographic link in the Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Metadata Configuration). The Profile Details page appears.
    2. Select the Normalization Processes tab. The following default normalization processes appear on the Normalization Processes tab:
      • Unimarc Bib Initial Normalization
      • Unimarc Bib normalize on save
      • Unimarc Bib Re-sequence
      • Unimarc Bib Re-sequence And Clear empty fields
    3. Select Actions > Edit for one of the normalization processes and select the Task List tab to view the UNIMARC tasks provided (in the Process List Pool section of the tab).
    4. When you are finished, click Save.
    To view an example of the 9XX UNIMARC fields available in the Metadata Configuration profile using the 950 field as an example:
    1. Click the UNIMARC Bibliographic link in the Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Metadata Configuration). The Profile Details page opens on the Fields tab.
    2. Locate the 950 field using Find.
      Find a Field on the Fields Tab
      950 Field Appears on the Profile Details Page
    3. Select Actions > Customize to view the subfields and indicators available for customizing.
      950 Field Details
    4. Expand the Subfields, First Indicator, and Second Indicator sections to view the customizable options.
    To view the UNIMARC validation field changes:
    1. Click the UNIMARC Bibliographic link in the Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Metadata Configuration). The Profile Details page opens on the Fields tab.
    2. Filter the Fields tab by selecting the 1XX: Coded Information Block option.
      Fields Tab Filter
    3. For field 100, select Actions > View. The Field Details page appears.
    4. Expand the Positions section to view the positions being validated.
      Field 100 Positions Section Expanded
      The following position validations have been added for UNIMARC:
      • Date entered on file
      • Type of Publication Date
      • Publication Date 1
      • Publication Date 2
    5. When you are finished, click Back until you return to the Metadata Configuration List page.

    Managing UNIMARC Local Authority Records

    As a multi-format library solution, Alma supports the use of UNIMARC authority records for the purpose of authority control. Alma provides the capability for managing UNIMARC local authority records (and associating them to bibliographic records using the F3 functionality in the MD Editor). From the Metadata Configuration List page, you can create your own UNIMARC authority profile for managing local authorities. In addition, you can create authority record import profiles designed to import UNIMARC records.
    For more information about managing UNIMARC local authority records, see the Managing UNIMARC Local Authority Records video (2:56 mins).
    To create a UNIMARC local authority profile:
    1. On the Metadata Configuration List page (Resource Management > Resource Management > Configuration Menu > Cataloging > Metadata Configuration) click Add Local Authority. The Add Local Authority pop-up window appears.
      Add_Local_Authority_Metadata_Configuration_Profile_Pop-Up_Window_02_TC.png
      Add Local Authority Metadata Configuration Profile Pop-Up Window
    2. Complete the parameters required for the UNIMARC local authority profile.
      • Name – Enter the vocabulary name that you want to display on the Local Authority Registry page for the profile.
      • Code – Enter the vocabulary code name that you want to display when configuring your import profile, for example.
        Vocabulary Code Displayed in the Import Profile Options
      • Family – Select UNIMARC from the drop-down list.
      • Type – Select one of the following types from the drop-down list:
        • Subject
        • Name
        • Names and Subjects
        • Classification
      • Direct ID prefix – Enter the ID prefix if one is used.
      • Multilingual – Select Yes or No from the drop-down list.
    3. Click Add and Close. The local authority registry that you created appears in the list on the Local Authority Registry page.
    4. Click Save. Your local authority profile appears in the list on the Metadata Configuration List page.
    5. Click the UNIMARC Authority link to open the Profile Details page and configure fields, normalization, and validation similar to MARC 21.
      Authority Profile Details
    6. When you have completed making changes to the profile details, click Deploy.
    To create a UNIMARC authority import profile:

    Working with KORMARC Fields, Normalization, and Validation

    Similar to the support Alma provides for MARC 21, Alma provides support for KORMARC validation and normalization. Alma uses the settings in the validation and normalization profiles when importing records and when working with records in the MD Editor.
    Default normalization processes have been created for KORMARC bibliographic record normalization.
    To work with the KORMARC normalization tasks:
    1. Open the Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu).
    2. Click the KORMARC Bibliographic link. The Profile Details page appears.
    3. Select the Normalization Processes tab. The following default normalization processes appear on the Normalization Processes tab:
      • Kormarc Bib normalize on save
      • Kormarc Bib Re-sequence
      • Kormarc Bib Re-sequence And Clear empty fields
    4. Select Actions > Edit for one of the normalization processes and select the Task List tab to view the KORMARC tasks provided (in the Process List Pool section of the tab).
    5. When you are finished, click Save.

    Working with CNMARC Fields, Normalization, and Validation

    Similar to the support Alma provides for MARC 21, Alma provides configuration options for CNMARC fields, normalization and validation for bibliographic and authority records. See Editing Profile Details and Working with Authority Records for more information.
    Alma uses the settings in the validation and normalization profiles when importing records and when working with records in the MD Editor.
    Default normalization processes have been created for CNMARC bibliographic record normalization.
    To work with the CNMARC normalization tasks:
    1. Open the Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu).
    2. Click the CNMARC Bibliographic link. The Profile Details page appears.
    3. Select the Normalization Processes tab. The following default normalization processes appear on the Normalization Processes tab:
      • Cnmarc Bib normalize on save
      • Cnmarc Bib Re-sequence
      • Cnmarc Bib Re-sequence And Clear empty fields
    4. Select Actions > Edit for one of the normalization processes and select the Task List tab to view the CNMARC tasks provided (in the Process List Pool section of the tab). See the Process List Pool Options table for an explanation of normalization tasks.
      Optionally, click Add Process from the Normalization Processes tab if you need to create a new normalization process.
    5. When you are finished, click Save.

    Working with the GND Authority Profile

    A GND profile is available that enables Alma to better integrate with the GND authority records. This feature includes:
    The GND Authority profile is of particular interest to institutions cataloging and contributing records to the GND. While cataloging GND authority records in the Alma MD Editor, the GND Authority profile assists with your GND contributions by having:
    • All the GND fields defined, including mandatory definitions
    • GND controlled vocabularies in place
    • Specific normalization rules
    For institutions that have MARC21 Bibliographic configured as the Active Registry, both the MARC21 Authority and the GND Authority profile options will be available on the Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu > Cataloging section > Metadata Configuration).
    The configurable fields on the Fields tab and normalization and validation processes will be specific to the GND standard. For example, the 079 field is unique to the GND Authority profile configuration.
    For information regarding GND indexes, see Configuring Search Indexes.

    Working with MARC 21 Holdings Profiles

    Working with MARC 21 holdings profiles is similar to working with the bibliographic and authority profiles. They all manage configuration options on the following tabs:
    • Fields
    • Normalization Processes
    • Validation Processes
    • Validation Exception Profile List
    The differences between them have to do with the fields that are being managed (normalized and validated). Due to the similarities, reference the viewing, editing and configuring sections above for detailed steps in navigating the Metadata Configuration profiles when you work with the MARC21 Holding link to profile configurations.
    MARC21 Holding Link
    See the table below for MARC21 Holding profile process options.
    Process Name Description
    Normalization Processes:
    Marc21 Holding normalize from BIB This process is used to normalize MARC21 holdings from bibliographic records. It provides the following process options in the Process List Pool section on the Task List tab when you edit this process:
    • 852 field normalization
    • MarcDroolNormalization
    • marc21HoldingClearEmptyFieldsTask
    • marc21HoldingResequenceTask
    • MARC21 Expand Holding By 866/7/8 Task
    • MARC21 Expand Holdings By 863/4/5 Task
    Marc21Holding normalize on save This process is used to normalize MARC 21 holdings record when the holdings record is saved in the MD Editor. It provides the following process options in the Process List Pool section on the Task List tab when you edit this process:
    • 852 field normalization?
    • MarcDroolNormalization
    • marc21HoldingClearEmptyFieldsTask
    • marc21HoldingResequenceTask
    • MARC21 Expand Holding By 866/7/8 Task
    • MARC21 Expand Holdings By 863/4/5 Task
    Marc21 Holding Re-sequence And Clear empty fields This process is used when resequencing and clearing empty fields. It provides the following process options in the Process List Pool section on the Task List tab when you edit this process:
    • 852 field normalization
    • MarcDroolNormalization
    • marc21HoldingClearEmptyFieldsTask
    • marc21HoldingResequenceTask
    • MARC21 Expand Holding By 866/7/8 Task
    • MARC21 Expand Holdings By 863/4/5 Task
    Validation Processes:
    Marc21 Holding validation on save
    This process is used to validate holdings record contents when the holdings record is saved in the MD Editor. Click Edit to configure the validation processes.
    General Information Tab
    From the General Information tab, the status for the Marc21 Holding validation on save validation process can be set to Active or Inactive.
    Task List Tab
    The following process options are provided on the Task List tab in the Process List Pool section:
    • Validation Recognized Fields MARC21
    • Validation Mandatory MARC21
    • Validation Repeatable MARC21
    • Validation Fixed Fields Positions MARC21 Holding
    • Validation Variable Fields MARC21
    • Validation Recognized Sub-Fields MARC21
    • Validation Mandatory Sub-Fields MARC21
    • Validation Repeatable Sub-Fields MARC21
    • Validation Library and Location MARC21 Holding
    • Duplicate Validation MARC21 Holding
    • Call Number and Accession Number Validation
    • Duplicate Validation MARC21 Holding Other Title
    Select processes from the Process List Pool (click Add to Selection) and prioritize the processes in the Processes Selected section that you want performed to validate holdings records when they are saved in the MD Editor.
    Task Parameters Tab
    When you select the Duplicate Validation MARC21 Holding Other Title process on the Task List tab, the Check different locations for duplicate call numbers check box appears on the Task Parameters tab. Select this check box to have the validation check performed on holdings records in different locations. If this check box is not selected, the validation check is performed only on the holdings records in the current location.

    Configuring Controlled Vocabulary Registry

    To configure the Controlled Vocabulary Registry, you must have one of the following roles:
    • Catalog Administrator
    • General System Administrator
    Alma supports validation of subfield values based on a controlled vocabulary (a list of acceptable values for that subfield). Alma supplies several controlled vocabularies out-of-the-box (OTB), and you can implement additional ones.
    To implement a controlled vocabulary (CV):
    1. Create a controlled vocabulary.
    2. Assign the controlled vocabulary to a specific MARC 21 subfield.
    See the procedure in Editing Fields and the steps that describe editing field options.
    You configure controlled vocabularies (CVs) from the Metadata Configuration List page (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Controlled Vocabulary Registry).
    Controlled Vocabulary Registry Page
    You can perform the following actions on this page:
    • View a controlled vocabulary details (Actions > View)
    • Add a controlled vocabulary (see Adding/Editing a Controlled Vocabulary)
    • Add or delete controlled vocabulary code values (see Adding/Editing a Controlled Vocabulary)
    • Restore a modified out-of-the-box controlled vocabulary (Actions > Restore)
    • Delete a controlled vocabulary that you added (Actions > Delete)

    Adding/Editing a Controlled Vocabulary

    You can add or edit a controlled vocabulary.
    To add a controlled vocabulary:
    1. On the Controlled Vocabulary Registry page (Resource Configuration > Configuration Menu > Cataloging > Controlled Vocabulary Registry), click Add CV. The Controlled Vocabulary Details page opens.
      Controlled Vocabulary Details Page
    2. Enter a name and description.
      This name and description then appear on the Controlled Vocabulary Registry page and in the drop-down list of options for Choose Controlled Vocabulary when you assign a controlled vocabulary to a MARC21 subfield in the metadata configuration profile. See Step 4 in the Editing Fields above. Note that only after you assign a controlled vocabulary to a MARC21 subfield can this vocabulary be used in the MD Editor as shown in Step 4 below.
    3. After you have added at least one controlled vocabulary name, click Save to save any further changes to the description.
    4. In the Add new value area, enter a code and a description. Note that the code can contain spaces or special characters.
      The code that you enter is the term that is validated or provided as an option when entering a record in the MD Editor.
      245 $h CV Example
      In the 245 $h example above, the codes that you enter appear first in each row, and the description appears to the right of each code in parentheses.
      The description for the code that you enter in the CV registry can provide additional information regarding the term that you entered.
    5. Click Add. The code value is added to the list of controlled vocabulary registries.
    6. Repeat steps 3 and 4 to add any additional code values (terms).
    7. Click Delete beside any code value to delete it. A warning appears if you try to delete a code value that was originally included in an out-of-the-box vocabulary.
    8. Click Cancel to return to the Controlled Vocabulary Registry page.
    To edit a controlled vocabulary:
    1. On the Controlled Vocabulary Registry page (Resource Configuration > Configuration Menu > Cataloging > Controlled Vocabulary Registry), select Actions > Configure or Actions > Edit. The Controlled Vocabulary Details page opens.
    2. Continue with the steps described in the above procedure, starting from step 3.

    Configuring Author Number Lists

    To configure Author Number Lists, you must have one of the following roles:
    • Catalog Administrator
    • General System Administrator
    The standardized list of author numbers is incorporated into Alma's logic for automatically generating author numbers when the appropriate file in the mapping table is enabled.
    To configure the Author Number Lists mapping table:
    1. On the Author Number Lists mapping table page (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Author Number Lists), click Customize in the row that contains the author number mapping table that you want to use.
      Author Number Lists Mapping Table Page
      The cutter_three_figure_cn.txt option contains the Chinese author information, and the cutter_three_figure_kor.txt option contains the Korean author information.
      Only one author list may be enabled in the Author Number Lists mapping table.
    2. Confirm that the Target Tag and Target Subfield options are customized to match your requirements. Make changes if necessary.
    3. Click the check mark (in the same row) in the Enabled column to activate that mapping table.
      Author Number Lists Mapping Table Page with Options Customized and Enabled
    4. Click Save.
    With the Author Number Lists mapping table configured, you can automatically generate the author number for the local call number field in the MD Editor (using Edit > Generate Author Number). See Automatically Generating the Chinese Author Call Number for the 905 Local Call Number Field in a MARC 21 Bibliographic Record on the Working with Bibliographic Records page and Automatically Generating the Author Number for the 090 Local Call Number Field in a KORMARC Bibliographic Record for additional details.

    Configuring Cataloging Levels for Contribution to Externally Managed Authorities

    Each external system stores the cataloging level of a record in a predefined field. To align Alma's cataloger permission levels (see Cataloging Privileges) with the external system's cataloging levels, use the Cataloging Level Mapping for External Authority configuration mapping table (Resource Management > Resource Configuration > Configuration Menu > Cataloging > Cataloging Level Mapping for External Authority). The Cataloging Level Mapping for External Authority configuration that you create identifies how the mapping between Alma cataloging permission levels and the external cataloging levels will be validated in the MD Editor when you are creating and editing externally managed authority records for contribution.
    The following is an example for GND:
    079_$c_GND_Authority_Record_02.png
    079 $c GND Authority Record
    The Cataloging Level Mapping for External Authority configuration option is available only in the Network Zone (not the member institutions) and standalone institutions that are not part of a collaborative network.
    To configure cataloging levels for contributions, your institution must be configured by Ex Libris Support to allow authority contributions to the Community Zone from external systems. In addition, your institution must be configured to work with cataloging levels in Alma (also dependent on Ex Libris Support configuration - see Cataloging Privileges).
    To configure Cataloging Level Mapping for External Authority contributions:
    1. On the Cataloger Level to Vocabulary Code mapping table (Resource Management > Resource Configuration > Configuration Menu), in the Create a New Mapping Row section, use the Quick Add options to map an Alma cataloging level to an external system cataloging level.
      Cataloger_Level_to_Vocabulary_Code_Mapping_Table_06.png
      Cataloger Level to Vocabulary Code Mapping Table
      1. Select one of the Alma cataloging levels from the drop-down list. The cataloging levels that appear in the drop-down list are determined by the Cataloger Permission Level configuration. See Cataloging Privileges for more information.
      2. Enter one of the external system's cataloging levels to map to the Alma cataloging level that you selected.
      3. Select True or False from the Default Value drop-down list to indicate whether the mapping that you're creating for the level is the default mapping.
        Since the mapping table allows you to specify many-to-many relationships, as shown in the figure above where 40 maps to 4, 5, and 6 and 4 maps to 30 and 40, you need to indicate which one is the default mapping.
      4. Select the relevant vocabulary.
        Current options are GND and BARE.
      5. Click Add Row.
      If you need to change a mapping, use the Delete action for the mapping you want to change and create a new mapping.
    2. When you are finished making your configuration changes, click Save or Save and Distribute. See Centralized Management of Configuration Tables for more information, including an explanation of Stop Network Management.
    With the Cataloging Level Mapping for External Authority configuration set, the MD Editor can determine whether the cataloger has the necessary Alma cataloging level for a given authority record being edited. If Alma detects that the cataloger may have insufficient permissions to successfully contribute the authority record, it prompts the cataloger with the following message:
    Insufficient_Permissions_Detected_02.png
    Insufficient Permissions Detected
    Since the external system controls which contributed records are accepted or rejected, Alma leaves that determination to the external system and does not block the user from editing the authority record even when it detects that the cataloger may have insufficient permissions. As a result, the ability to edit an authority record in Alma does not guarantee that it will be accepted when contributed.

    Configuring Multiple Access Points for CNMARC 6XX Fields

    New for May!
    Use the CNMARC 6XX Category configuration option for identifying the CNMARC 6XX fields that should have multiple access points. See Using Multiple Access Points for CNMARC 6XX Fields for more information.
    To configure CNMARC 6XX headings control fields:
    1. Click CNMARC 6XX Category in the Cataloging section of the Resource Management configuration (Resource Management > Resource Configuration > Configuration Menu). The CNMARC 6XX Category mapping table appears.
      CNMARC 6XX Category Mapping Table
    2. In the Add Row section, enter the 6XX field, its description, and click Add Row for the 6XX field that you want to have segmented.
      CNMARC 6XX Field Added
    3. Repeat step 2 for all the 6XX fields that you want to add to the CNMARC 6XX Category mapping table.
    4. When you have finished adding 6XX fields, click Customize.
    .