- Catalog Manager
- Catalog Administrator
- Repository Manager
- Physical Inventory Operator
- Purchase Operator
- Purchase Manager
- Editor Full
- Digital Inventory Operator
|Authority Vocabulary||Subject/Name Authority||Update Frequency||Vocabulary Code|
BARE (Norwegian Authority System) – BIBSYS Authority Registry(See Working with Norwegian Authority System (BARE) Records for more information.)
|Subject and Name||Daily||BARE|
|BK Basisklassifikation Classification||Subject and Name||When available|
|BNC - Catàleg d’autoritats de noms i títols de Catalunya (CANTIC)||Subject and Name||When available||CANTIC|
|BNC - Llista d'encapçalaments de matèria en català (Lemac)||Subject||When available||LEMAC|
|BNF – Bibliothèque nationale de France - MARC 21 Version||Subject and Name||Monthly|
|Canadiana Name Authorities in French||Name||Every 2 weeks||LACNAF|
|Cataleg d’autoritats del CCUC||Subject and Name||When available||CCUC|
|CSIC||Subject and Name||Daily||CSICAU|
|EuroVoc – the EU's multilingual thesaurus||Subject||When available||EUROVOC|
|FAST – Faceted Application of Subject Terminology – OCLC||Subject||When available||FAST|
|Finnish Name Authority File||Name||Every 6 hours||FINAF|
|French MeSH UNIMARC Version||Subject||When available||FMESH|
|GND – German National Library||Subject and Name||Daily||GND|
|GSAFD Genre Terms||Subject||When available||GSAFD|
|Haifa Children Library Subjects||Subject||When available||HAIFACH|
|Hong Kong Chinese Authority Name||Subject and Name||Daily||HKCAN|
|IdRef - Version MARC21||Subject and Name||Every 6 hours||IDREF|
|IdRef – Version UNIMARC||Subject and Name||Every 6 hours||RAMEAU|
|LCDGT (Library of Congress Demographic Group Terms)||Subject||When available||LCDGT|
|Library and Archives Canada (LAC) – Canadian Subject Headings||Subject||When available||CSH|
|Library of Congress (LoC) – Genre/Form Terms Thesaurus Records||Subject||Weekly||LCGFT|
|Library of Congress (LoC) – Medium of Performance Thesaurus for Music||Subject||When available||LCMPT|
|Library of Congress Name (LCNAF)||Name||Weekly||LCNAMES|
|Library of Congress Subject (LCSH)||Subject||Weekly||LCSH|
|Maori Subject Headings||Subject||3 times a year||REO|
|National Agricultural Library subject authority file||Subject (English Terms)||Annually||NAL|
|National Library of Israel – Multilingual Thesaurus||Subject and Name||Every 6 hours||NLI|
|National Library of Spain||Subject and Name||When available||EMBNE|
|NLM MeSH – United States National Library of Medicine||Subject||Annually||MESH|
|Nuovo Soggettario||Subject||Twice a year||NSBNCF|
|PUC – Pontificia Universidad Católica de Chile||Subject and Name||When available||CLSAPUC|
|RAMEAU – MARC 21 Version||Subject||Monthly||RAM|
(See Working with the RVK Authority Record Classification for more information.)
|Subject and Name||Twice a year||RVK|
Jobs Related to Authority Records
- Authorities - Link BIB Headings – This job searches all authority (and local authority, if enabled by Ex Libris Support) record fields, including subdivision fields, for complete terms listed in bibliographic records (giving priority to local authorities, if enabled). If exact matches are found, the bibliographic records are linked to the corresponding authority records. If exact matches are not found, a search of all authority records is performed once again but the subdivision fields are disregarded, and the bibliographic records are linked to the matching authority records that are located during the second search. On a subsequent run of the Authorities – Link BIB Headings job, a bibliographic record that was linked to an authority record without subdivision fields may be re-linked to a better matching authority record (with subdivision fields). If a match is found on the main part of the heading, the subdivisions are still retained in the bib record. For MARC 21, partial matching for sub divisions is done on $v $x $y $z in 6XX fields. For UNIMARC and CNMARC, partial matching for sub divisions is done on $$j, x, y, z ,on fields 410, 600, 601, 602, 605, 606, 607, 610, 616, 617, 620, 675, 680, 711, 713, 730, 740, 741, 742.
Over time, you may have local authority records that you’ve created that subsequently become available as Community Zone authority records. When these records are added to the Community Zone, nothing happens to the records attached to your local authority records. The local authority records will still be local without any connection to the Community Zone. A bibliographic record that is already linked to your local authority record will not have its link switched to the Community Zone authority record.However, when the authority records that are the same as your local authority records are added to the Community Zone, you can choose to delete the local authority records. If you choose to delete the local authority records, all the headings will be linked to the Community Zone authority record with the same preferred term (1XX field) by Alma’s nightly linking job.For CJK content, bibliographic records are linked to authority records based on CJK content (not transliterated Latin content).
- Authorities - Preferred Term Correction – This job performs preferred term correction on all bibliographic records that are linked to authority records using the Authorities - Link BIB Headings job. For example, if a bibliographic record contains the non-preferred term “Narcotics, Control of,” and the associated authority record contains the preferred term “Drug control,” the Authorities – Preferred Term Correction job replaces “Narcotics, Control of” with the preferred term “Drug control.” Bibliographic records are also updated with any subsequent updates to authority records. If there were any failed records in the job's run, the job handles them in its next run.
This job is disabled by default. To enable it, set the disable_preferred_term_correction_job parameter (see Configuring Other Settings (Resource Management)) to false. Subsequently, view the Scheduled tab of the Monitor Jobs page (see Viewing Scheduled Jobs) and confirm that the Authorities - Preferred Term Correction job is active.The Authorities - Preferred Term Correction job does not handle preferred term correction on migrated bibliographic records retroactively. Since migrated bibliographic records may be linked to authorities in Alma, any change (to the bibliographic record authorized fields, or to the authority record in the Community Zone to which the bibliographic record is linked) that occurs in Alma after the record is initially migrated, triggers future preferred term corrections on the records after the Authorities - Preferred Term Correction job is enabled.
Alma-Based Authority Management
Alma supports Alma-based authority management. For an institution that manages local authority records and publishes them to the Community Zone, there is the option to have the Alma community contribute to these authority records (like the National Library of Israel (NLI) implementation). If you are an institution that 1) currently manages an authority file locally, 2) publishes it to the Community Zone, and 3) wants to have other authorized members of the Alma community contribute changes to this authority file, contact Ex Libris to analyze the feasibility of your request. If your authority requirements match the criteria for this functionality, Ex Libris will work with you to implement this capability. See Working with NLI Integrated Authority Records for more information.
Adding a Local Authority Definition
- In order to use local authorities in Alma, an Ex Libris representative must enable the local authority functionality for your institution.
Unless you have configured authority priorities for your system (see Resource Management - November 2016 Enhancements for information on this feature), multiple subject authorities can be used by Alma, but only one type of names authority can be used (global or local). For example, if Alma is defined to use LCNAMES, it cannot also use GND names authorities.However, if Alma is defined to use LCNAMES, you can also maintain a local LCNAMES authority and use it. But you cannot use a local authority that is not LCNAMES. In this case, only one type is being used both as a local and a global authority.Given these considerations, you should define only one type of Name or Names and Subjects local vocabulary.For information on the code to be used for the defined names authority, see the Code entry in the Add Local Authority dialog box below.
Note that when you add a local authority configuration, if you want to use the functionality provided by the Language Configuration option, you first need to contact Support to configure that capability for your system.
- On the Metadata Configuration List page (Configuration Menu > Resources > Cataloging > Metadata Configuration), select Add Local Authority. The Add Local Authority dialog box appears.
- Complete the information in the Add Local Authority dialog box (see the table below for more information).
Parameter Description Name Enter a name to identify this local authority. This name appears in the Vocabulary Name column. Code Enter an identifying code for this local authority that appears in the Code column in the Authority Vocabularies section on the Metadata Configuration List page and the Vocabulary code drop-down list on the Import Profile Details page for authority profiles.If the authority indication is in the bibliographic record’s second indicator 7, subfield 2, the code must match what is in this subfield 2. This is relevant for Subject and Names and Subjects types of local authorities.For the Name type of local authority (see the note above, at the beginning of this section), the code must match the authority_names customer parameter value that was entered for your institution by Ex Libris staff. If you are unsure of the defined value for this parameter (the default for which is LCNAMES), contact an Ex Libris representative. Type Select from the following options available in the drop-down list:
No more than one name type of local vocabulary should be created.
- Names and subjects
Direct ID Prefix Enter one or more prefixes in this field to be used for bibliographic to authority record matching and linking when there are multiple $0 entries (or $3 in UNIMARC or CNMARC records). For more information, see Authority Control Based on Multiple Authority Identifiers in a Bibliographic Record and Using Originating System IDs for Linking Bibliographic Records to Authority Records.The prefix must be entered with parentheses surrounding it. If more than one prefix is required, separate them by commas. For example: (CCL1),(CCL2),(CCL3). Notice that there are no spaces separating these entries. The maximum number of characters for this field is 255. The sequence in which you enter the prefixes determines the priority order in which they are evaluated for a match when there are multiple 035 entries in the authority record to match against.For Community Zone managed authority records, the Direct ID Prefix needs to be configured by Ex Libris. For example, the DE-588 Direct Prefix ID used in the GND (German National Library Names and Subjects) records is configured at the Community Zone level.
Select the cataloging standard (such as MARC 21, UNIMARC, or CNMARC) that you plan to use for entering the local authority records with this profile. This name displays in the Family column. Multilingual Select Yes from the drop-down list to indicate that the authority record may contain multiple language entries. See step 4 below for more information.For Community Zone managed authority records, the Multilingual parameter (and its associated components, Language Configuration and Allow multi preferred terms) needs to be configured by Ex Libris at the Community Zone level.See Working with Multilingual Authority Records for more information. Description Use this option to more fully identify the local authority that you are creating.
- Select Add and Close. The local authority configuration that you created appears in the Authority Vocabularies section of the Metadata Configuration List page.
- (Optional) If you selected Yes for the Multilingual option above, select the Edit row action for the local vocabulary that you created in the steps above and complete configuring the local vocabulary using the information provided in the table below.
- This is only available for multilingual authorities.
- If you want to use the functionality provided by the Language Configuration option, you first need to contact Support to configure this capability for your system.
This button appears when you select Yes for the Multilingual parameter.Language Configuration Button
Select the Language Configuration button to open the Language Code mapping table.
This configuration defines all the possible languages that are defined in the authority records. With this mapping table, when no language is specified in $9 of the bibliographic record, the system looks for an authority heading with text that matches exactly to the text in the bibliographic field. The system will look for a match in each language in the order defined in the Order column of the configuration. See the example below.
In this example, if an exact text match is found in Chinese, the link is created between the bibliographic and authority record and $9 with the correct language is added when the preferred-term correction is done. If no Chinese text match is found, the system continues to look for an exact text match using the next language in numeric order as specified in the Order column of the mapping table. If no text match is found and the end of the list is reached, no link is made. Notice, in this example, that an empty Language Code setting in the mapping table is a valid option.
Language Code Mapping Table
Select Add Row and enter Vocabulary Code, Language Name, Language Code, and Order. Note that the language code entries are free-text fields. Add these based on the codes that the authority file uses.
Select Add Row to add these settings to your Language Code mapping table.Add Row Options
In addition to local authority records, this capability is also available for global authority records when Ex Libris configures the Multilingual parameter in the Community Zone.This feature is only relevant for multilingual authorities where the matching is done by text and not by ID.
See Working with Multilingual Authority Records for more information.
Allow multi preferred terms This parameter appears when you select Yes for the Multilingual parameter.
- Use this option to set the record validation in Alma for accepting multilingual authority records with multiple preferred terms when the same language is identified in $9.
Multiple Preferred Terms with the Same $9 (Authority Record)If Allow multi preferred terms is not selected, a warning or block validation occurs for multilingual authority records with multiple preferred terms and the same language is identified in $9.See Subfield 9 with the Same Language Code for more information.
- Use this option to set the record validation in Alma for accepting multilingual authority records with multiple preferred terms when there is no $9 specified. With Allow multi preferred terms selected, the MARC 21 Auth validation on save process will allow records without $9 specified. See Working with Validation Exception Profiles for more information.
MARC 21 Auth validation on save ProcessSee No Subfield 9 Specified for more information.
See Working with Multilingual Authority Records for more information.
- Select Save.
Creating Local Authority Records
- Using the MD Editor (see Creating Local Authority Records Using the MD Editor)
- Using an import profile (see Managing Import Profiles)
- To use local authorities in Alma, Ex Libris Support/your Ex Libris Professional Services representative must enable local authority functionality for your institution.
- To create a local authority record (either via the MD Editor or via an import profile) for authority vocabulary that exists in the Community Zone, you must first create this local authority (vocabulary) in your institution (if it does not already exist). For example, if the Community Zone has a defined authority (vocabulary) for REO, but is missing a specific authority record that you want to create locally, ensure that the local authority (vocabulary) for REO exists in your institution before you create the authority record locally. For information on creating local authorities (vocabulary), see Adding a Local Authority Definition to the Local Authority Registry.
- You can delete local authorities using the Delete Local Authority Records job – see Delete Local Authority Records.
- Unless you have configured authority priorities for your system (see Resource Management - November 2016 Enhancements for information on this feature), multiple subject authorities can be used by Alma, but only one type of names authority can be used. For example, if Alma is defined to use LCNAMES, it cannot also use GND names authorities. For more information, see Adding a Local Authority Definition to the Local Authority Registry.
Creating Local Authority Records Using the MD Editor
- Open the MD Editor.
- Select File > New and select from the list of local vocabularies that have been created/implemented for your system (see Adding a Local Authority Definition to the Local Authority Registry, or if the local authority vocabulary is an extension of a global one, it appears here automatically as an option with no predefinition required), such as:
Create New Local Authority Records (Select Vocabulary)For members in a Network configured for creating local authority records, the File > New menu options display with both the Institution and Network icons to distinguish where the record you are creating will be stored (at the Institution level or the Network level).MD Editor File > New Menu Options for a Member in the Network
- (local) Library of Congress Subject Headings
- (local) Library of Congress name authority records
- (local) U.S. National Library of Medicine, Medical Subject Headings 2013
- (local) German National Library of Names and Subject Headings
- Choose a template (see Working with Record Templates) and enter the authority record data/terms.
Select File > Save and Release Record.If the system identifies another record in the Alma repository with duplicate headings content, it presents a confirmation pop-up message. You need to select Yes or No to indicate how to handle the duplicate. If you select Yes, the duplicate information is presented for you to view and/or edit.Duplicating Handling ConfirmationAfter the record is saved, you can view the record you entered using an Authorities search. You can create a bibliographic record that uses the local authority record/terms that you created/saved. Preferred terms are marked with a star. (Note that if you select a non-preferred term, the MD Editor automatically populates the bibliographic record with the preferred term.)
Viewing Authority Records
Exporting Local Authority Records
Changing the Placement of an Authority Record
- Open the MD Editor (Resource Management > Cataloging > Open Metadata Editor).
- Select File > New and select the vocabulary name.
For this example, a Network vocabulary has been selected.Creating a Network Authority Record
- Enter the authority record details.
- Select Tools > MARC 21 Authorities.
Change Authority Placement
- Select Change Authority Placement.
The New Authority Record Placement dialog box appears. One or more of the following options are provided:
New Authority Record Placement Dialog BoxThe options that are provided vary depending on the vocabulary that you selected for your draft authority record (Local or Network) and how your Metadata configuration is set for locally managed or community managed authority records (see Controlling the Display and Access of Global Authorities in the MD Editor).
- Community Zone
- Network (Zone)
- Local (Institution Zone)
- Select the placement location and select OK.
You may select Tools > MARC 21 Authorities > Change Authority Placement and change the placement location, again. However, once you have saved the record, you can no longer change the placement. The Change Authority Placement option appears as disabled after the record has been saved.
Performing Global Changes on Locally Managed Authority Records
- Open the Metadata List Configuration page (Configuration Menu > Cataloging section > Metadata Configuration).
- Select the MARC 21 Authority link, for example, for the local authority Metadata Configuration for which you want to create a Drool-based normalization rule. The Fields tab of the Profile Details page opens.
- Select the Normalization Processes tab.
Normalization Processes Tab
- Select Add Process. The Process Details wizard step 1 page opens.
- Enter the Name, Description, and Status.
- Select Next. Wizard step 2 of the Process Details page opens.
- Select Add Tasks, select the MARC Normalization Rules process, and select Add and Close.
- Select Next. Wizard step 3 of the Process Details page opens.
- From the drop-down list, select the Drools File Key that you created for this process job (refer to Working with Normalization Rules for additional information).
- Select Save. The new normalization rule displays in the Normalization tab of the Profile Details page and can be edited, copied, or deleted using the Actions options.
- Run the normalization job you created above. For more information, see Running Manual Jobs on Defined Sets.
Managing Authority Records in the MD Editor
Linking an Authority Record to a Bibliographic Record
- 130 – Main Entry – Uniform Title
- 630 – Subject Added Entry – Uniform Title
- 730 – Added Entry – Uniform Title
- 830 – Series Added Entry – Uniform Title
Viewing and Linking to an Authority Record
- Open a new or existing bibliographic record in the MD Editor.
- In an authority-controlled field (100, 110, 111, 130, 440, 490, 600, 610-611, 620, 630, 648, 650, 651, 654, 655, 700, 710, 730, 748, 751, 754, 800, 810-819, and 830), press F3 OR type at least three characters of the author’s name or subject heading for a new bibliographic record and then press F3 to display a list of suggestions.
Suggested Terms ListLocal authorities are indicated by (Local) to the right of the title. A star to the left of the title indicates the preferred term. With any selection, the preferred term immediately replaces the non-preferred term.If you do not see the name or subject heading you are looking for in the list, you may need to type additional characters in the field to narrow the results.
- Select one of the following buttons:
- Select – Links the selected authority name or subject heading to your bibliographic record.
- View – Opens a read-only version of the full authority record on the right side of the split screen in the Authority tab.
- Add record to editing list – If the authority record that appears when you select View is local, not locked by another user, and not already included in the authority draft list, you can add it to your authority draft list by using this option. Select Add record to editing list to add the local authority record to your working records list as shown in the example below. After the record has been added to your working records list, you can edit this local authority record in the MD Editor.
Edit – If the authority record that appears when you select View is local and not locked by another user, you can select Edit to modify the local authority record. Note that this capability is also available from Browse Bibliographic Headings (Resources > Cataloging > Browse Bibliographic Headings).View / Edit Local Authority RecordBrowse Bibliographic Headings Local Authority Editing
Viewing Bibliographic Records Linked or Available for a Suggested Authority Record
When you use F3, bibliographic headings may be presented in addition to the authority headings. Note that the list of authority headings and Headings from bibliographic records that appear with using F3 originate from the Network Zone or the Institution Zone based on the scope of the record that you are editing. Use the procedure below to view the available bibliographic records.
- Open a new or existing bibliographic record in the MD Editor.
- In an authority-controlled field (100, 110, 111, 130, 440, 490, 600, 610-611, 620, 630, 648, 650, 651, 654, 655, 700, 710, 730, 748, 751, 754, 800, 810-819, and 830), type at least three characters of the author’s name or subject heading for a new bibliographic record and then press F3 to display a list of suggestions or press F3 in the authority-controlled field.
- Select the View button for one of the rows that appears in the authority records list. The right pane opens with the Authority and Bibliographic Records tabs.
- Select the Bibliographic Records tab (in the right pane of the MD Editor).
Use the Include filter to select one of the following options:
View Linked or Available Bibliographic Records
- Matching Headings – Select this option to view all the possible available bibliographic headings that match the record that you selected to view in the left pane.
- Linked Records – Select this option to view only the linked bibliographic headings for the record that you selected to view in the left pane.
Note that in a Network Zone, when you use F3 (or the binoculars, linking icon) from a Network Zone record, the bibliographic headings that appear on the Bibliographic Records tab are Network Zone records. When you use F3 from a local record, the bibliographic headings that appear on the Bibliographic Records tab are local records.
- Select the View link from the Bibliographic Records tab for the bibliographic record that you want to see that is linked or available for the selected authority record. When you select the View link for a result, Alma displays a full, read-only bibliographic record.
Deriving an Authority Record from a Bibliographic Record
- Open a new or existing bibliographic record in the MD Editor.
In an authority-controlled field (100, 110, 111, 130, 600, 610-619, 620, 630, 700 710 730, 800, 810-819, 830, 440, 490, 648, 650,651, 654, 655, 748, 751, 754), enter headings information that you know does not exist in an authority record and press F3. The field appears in the normal manner with the addition of the Create Authority Record option.Create Authority Record Option
Select Create Authority Record. The new authority record is created and displays in the MD Editor in the side-by-side, split screen format.Quick Authority Record Created
The list of authority records in the MD Editor also shows the new authority record that you created.List of Authority Records in the MD EditorWhen you create authority records using Create Authority Record and the focus field when you press F3 is a non-preferred field such as the 600 field, the content is placed in the preferred field 100 in the new authority record that is created.
- Complete processing the bibliographic record as you normally would.
Viewing Linked Names/Subject Headings from a Bibliographic Record
Open a bibliographic record in the MD Editor.If an authority-controlled field is linked to a name/subject heading, an icon appears next to the field: the icon appears for full linking, and New for November! appears for partial linking.
Select the icon to display the linked name/subject heading in split-screen mode.
View Name/Subject Heading in Split-Screen Mode
Editing Bibliographic Records with F3
Headings from Bibliographic Records Tab
|$9 in the Record Being Edited||$9 in the Bibliographic Headings Record||Resulting $9 in the Record Being Edited|
When you use F3 in the 751 field, names headings and subject headings are presented in the authority headings results. With this implementation of F3 for the 751 field, subject headings results are presented in addition to names headings results, when a second indicator is cataloged in the bibliographic record. If no second indicator is specified, only names headings results appear in the F3 results.
The 751 field can also be linked to names headings and subject headings depending on how you have cataloged the record.
This implementation of F3 does not affect the options presented in Browse Bibliographic Headings (Resources > Cataloging > Browse Bibliographic Headings). The Geographic Name source code option only appears when the Subjects heading type is selected and presents all 651 and 751 geographic names. See Subjects for more information.
3XX Bibliographic Record Control Fields
|Bibliographic Tag||Authority Headings Tag|
- F3 linking in the MD Editor
- Linking when saving or loading records
- Linking via the linking job
Editing Authority Records with F3
5XX Authority Record Control Fields
- MARC 21 – Subfield 0
- UNIMARC – Subfield 3
3XX Authority Record Control Fields
|Authority Tag||Authority Headings Tag|
|372||150, 155, 450, 455|
Copying Community Zone Authority Records to Your Local Authority Database
Working with GND Records in the MD Editor
GND Bibliographic Control Fields Used with F3
|Bibliographic Field||Authority Heading Type||
Entity Type of the GND Authority Record Identified in the 075 $b
|100||Personal Name||n or p|
|110||Corporate Name||g or b|
|110||Geographic Name||g or b|
|600||Personal Name||p or u|
|611||Meeting Name||f or u|
|689||Any||All except n|
|700||Personal Name||n or p or u|
|710||Corporate Name||b or u|
|711||Meeting Name||f or u|
GND Special Sorting Routine Used for Browsing Headings with F3
- The text from the name and subject headings is used to build the string for sorting the headings browse list.
- Each subfield is treated as a separate sorting block.
- Under certain conditions, the 548 $a and the 550 $a are added to the string built for sorting the headings browse list.
- When building the filing value for GND records with the 548 and 550 fields, the 548 field is appended with a single space as a delimiter; and the 550 field is appended with three spaces as a delimiter.
- When there are repeatable occurrences of the 548 and 550 fields, the filing text concatenates all entries into a single component.
German Language Sorting Used with F3
Implemented Punctuation Rules for Updated Bibliographic Records
|(1) Tag & Indicators||(2 Subfield to Which Punctuation Is Added||(3) Subfield Following the Subfield in Column (2)||(4) Punctuation to Be Added||(5) If Punctuation Exists/Does Not Exist Condition|
|800##||t||v||_; (space before semicolon)||;|
- If any of the punctuation specified in this column exists, the punctuation specified in column (4) is not added.
- If there is no punctuation specified in this column (the cell is blank), the punctuation in column (4) is added if all other conditions are met.
Handling Deleted Authorities During Metadata Imports
Working with the Norwegian Authority System (BARE) Records
Contributing BARE Records
- Open the MD Editor (Resources > Cataloging > Open Metadata Editor).
Select File > New > BARE to create a new record.Bare Contribution Option
- Enter the authority record details.
Select the Save icon.Alma submits the record to BARE for approval. If there is an error, Alma displays an error message in a dialog box and asks if you want to reload the record from scratch or continue editing. Select Yes to reload the record and discard your changes or select No to return to the MD Editor and continue editing. If the contributed record is approved, it is stored in the Community Zone and the master BARE database.
Working with the Regensburger Verbundklassifikation (RVK) Authority Record Classification
- Open the MD Editor (Resources > Cataloging > Open Metadata Editor).
Select the Templates tab. The list of template folders appear. The default RVK template provided by Alma is located in the German Classification Method folder.German Classification Method Folder with the RVK Template
- Open the German Classification Method Folder to work with the default RVK template provided. See Working with Record Templates for instructions.
- Open the MD Editor (Resources > Cataloging > Open Metadata Editor).
Select File > New > German Classification Method.German Classification Method for New RVK Local Authority RecordAlma loads the RVK form in which you can enter the RVK local authority record.RVK Local Authority Record
- Enter the data for your authority record.
Select File > Save and Release Record.Using the repository search, you should be able to locate the RVK authority record with an Authorities search.RVK Authority Record
- Use a search to locate the bibliographic record with which you want to work, and select Edit to open the record in the MD Editor.
- Select Edit > Add Field to add the 084 field.
- Enter $2 with rvk.
When you enter $a, press F3 to check for preferred terms. The system finds authority records based on the classification number (153 $a) or classification caption (153 $j). See Classification Search Indexes for more information.Entering the Bibliographic 084 Field084 $a Preferred Term Check Using F3
Using Originating System IDs for Linking Bibliographic Records to Authority Records
|Type||Authority-Controlled Data Fields|
The originating system is determined by the authority_names setting that Ex Libris defines in your Customer Parameters mapping. For example, if authority_names is set to LCNAMES, the originating system is the Library of Congress.
|100, 110, 111, 130, 700, 710, 711, 730, 800, 810, 811, 830|
The originating system is determined by the field’s second indicator as identified in the following list:
|600, 610, 611, 630, 648, 650, 651, 654, 655|
- Open the bibliographic record to which you want to add $0 in the MD Editor.
Make the authority-controlled data field to which you want to add the $0 the active row and press F3. The headings from authority records are displayed.F3 Authority Suggestions List
Select View for the authority record you prefer. The MD Editor displays the details of the authority record in Split Editor mode.Authority Record Details in Split Editor Mode
Review the authority record details, confirm that this is the authority record to which you want to link the bibliographic record, and select Select from the list of suggestions.Select Select for the Preferred Authority$0 Created
Save your bibliographic record. Now that this authority-controlled data field contains $0, pressing F3 displays only the authority record with the originating ID that is stored in $0.Only the Authority Record with the Originating ID stored in $0 is Displayed
Authority Control Based on Multiple Authority Identifiers in a Bibliographic Record
Navigating from the Authority Record to the Linked Bibliographic Record
- Authority vocabulary and the linked originating system ID
- Direct IDs
Working with Multilingual Authority Records
Processing Preferred-Term Correction for Multilingual Records
The Multilingual parameter needs to be set to Yes for multilingual authority records. For local authority records, you need to specify this parameter in the Metadata Configuration. For Community Zone managed authority records, this setting needs to be configured by Ex Libris at the Community Zone level. For more information, see Multilingual in the table in the Adding a Local Authority Definition section.
For MARC 21 records, the language code (such as lat, heb, ara, and so forth) for all preferred, non-preferred, and related terms is entered in $9.Subfield 9 lat Record EntrySubfield 9 lat Headings Display
For UNIMARC records, the language code for all preferred, non-preferred, and related terms is entered in $7. Specifically, the system uses positions 5 and 6 of $7.Positions 5 and 6 in $7
In a multilingual authority record, the preferred term is duplicated for each language. Non-preferred terms are entered as necessary for each language.Multiple $9 Entries with Duplicated Terms for Each Language
When a non-preferred term is used in a bibliographic record, Alma updates the bibliographic record using the preferred term of the same language.
When F3 is used (from the appropriate bibliographic fields) in the MD Editor to display a list of headings, the headings list is displayed as follows:
If there is a language code (specified in the MARC 21 $9 or the UNIMARC $7) in the bibliographic record, only the headings that match the language appear.
If there is no language code specified in the bibliographic record, all of the matching headings in all languages are displayed. The language code in the authority/bibliographic headings records is ignored.
Validation of records is handled in the following manner:
For authority records, Alma checks for the Multilingual setting. If the Multilingual setting is No, only one preferred field is allowed in the MARC 21 1XX or the UNIMARC 2XX. If the Multilingual setting is Yes and there is more than one preferred term, Alma checks for a language indication in the MARC 21 $9 or the UNIMARC $7, positions 5 and 6.
For bibliographic records, validation of $9 has been enhanced to include $9 in the fields specified in the table below.
MARC 21 Bibliographic Fields KORMARC Bibliographic Fields 084 084 382 100-199 440 382 490 440 648 490 650-651 600 654-655 610-619 748 630 751 648 810-819 650-651 830 654-655 700 710-719 730 748 751 800 810-819 830
- Publishing to Primo enriches the bibliographic records with the preferred, non-preferred, and related terms of all languages.
Handling of Multiple Preferred Terms with the Same Language
When you are doing preferred-term correction from the MD Editor using F3 in an authority controlled field of a bibliographic record and you select a non-preferred term, the system checks for a preferred term to link to; and if it finds multiple preferred terms with the same language, the system prompts you to select which preferred term to use. See the example below.
After selecting the preferred term, the system updates the bibliographic record in the MD Editor with the preferred term that you selected and identifies it with the binoculars icon indicating that the field is showing the preferred term for that authority controlled field.
Subfield 9 with the Same Language Code
With the appropriate configuration, Alma enables saving a multilingual authority that has multiple preferred terms with the same language code in subfield 9 without a validation warning or block. See Allow multi preferred terms for more information.
When the Authorities – Preferred Term Correction job is run and it finds multiple preferred terms with the same language code in subfield 9, the bibliographic record is not corrected and the following message is reported in the Authority Control Task List:
Preferred Term Correction – Multiple preferred terms with the same language found
For these records, use the Authority Control Task List (see Using the Authority Control Task List) and make the changes manually. Use the Preferred Term Correction – Multiple preferred terms with the same language found Action option in the Authority Control Task List to locate these tasks.
No Subfield 9 Specified
Authority records with no $9 can be processed in Alma. Specific validation and preferred-term correction processes have been implemented to handle these cases. See Validation with No Subfield 9 and Preferred-Term Correction with No Subfield 9 for more information.
Validation with No Subfield 9
With the appropriate configuration, Alma enables saving a multilingual authority that has no $9 without a validation warning or block when using the MARC 21 Auth validation on save process. See Allow multi preferred terms for more information.
Preferred-Term Correction with No Subfield 9
If a field in a bibliograhic record is linked to a non-preferred term that has no subfield 9, the system attempts to identify a preferred term with no subfield 9 and uses that preferred term to correct the bibliographic record. If no such preferred term is found, the bibliographic record is not corrected; and it is reported in the Authority Control Task List (see Using the Authority Control Task List). See the example below in green.
Display of Authority Search Results with Multiple Preferred Terms
When there is more that one preferred term in an authority record, each preferred term appears in the Authorities search results. See below for an example.
Preferred Term Correction for ID Linked Bibliographic Records with No Language Indication
When bibliographic record linking (to authority records) is done by ID, preferred term correction is completed for cases where there is no language indication in the bibliographic record and multiple preferred term options exist due to multilingual differences. As part of the preferred term correction process, the language indication in addition to the preferred term is copied to the bibliographic record. For MARC 21, the language indication is copied to $9; and for UNIMARC, it is copied to $7 positions 0-1.
Updating the Authority Record ID Automatically in Bibliographic Records
Processing Automatic ID Changes
New authority records with authority record ID changes are loaded into the Community Zone. The new authority records that are replacing existing authority records in the Community Zone have the new authority record ID stored in the 035 $a, and the previous authority record ID is stored in the 035 $z.There may be more than one previous record ID and, therefore, multiple 035 $z entries in a single authority record. In the example below, the (DE-588) entries are highlighted because (DE-588) is identified as the Direct ID Prefix in the Metadata Configuration List.New Authority Record ID in the 035 $a
The following scheduled jobs update the bibliographic records:
See the Viewing Scheduled Jobs page for more information.
Synchronize Changes from CZ (and/or Authorities – Handle Local Authority Record Updates for local authority records)The Synchronize Changes from CZ job updates $0 in the bibliographic record and performs relinking to the authority record in the Community Zone.The Authorities – Handle Local Authority Record Updates job updates $0 in the bibliographic record and performs relinking for local authority records.
The Authorities – Preferred Term Correction job updates the bibliographic records with the new preferred terms based on the new authority record for both Community Zone linked records and local authority-linked records (when local authorities have been implemented).
- Changes are identified in the Authority Control Task List. See Reporting in the Authority Control Task List (below) for more information.
Reporting in the Authority Control Task List
- Old authority record ID pulled from the authority record's 035 $z
- New authority record ID pulled from the authority record's 035 $a