Overview

This procedure captures the steps used to automatically generate database categories in Alma records for use in the Primo Database Search categories based on LCSH subject terms present in the Alma bibliographic records.

For setting up database categories in Primo via Alma records see the existing documentation:

https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/030Highlights/018Primo_November_2018_Highlights#Browse_Databases_by_Category

Rational for automating this process

The existing infrastructure for database categories requires that the desired subject categories be entered into the databases bibliographic record in Alma. This can be a time consuming and tedious process. In addition, the maintenance of an internal list of subject categories can be easily neglected.

To avoid both the manual addition of subjects, and the need to maintain an internal subject categories list we chose to automatically assign categories based on existing LCSH subjects within the records. Some more points about this decision making can be found at the end of this document.

Benefits of this process

• Automatic generation of database categories (a real time saver)
• Database categories generated are based on valid subject terminology
• Ability to edit and update subject choices with ease in the future

Step 1: Generate database categories field based on LCSH subjects

Using Alma Normalization rules copy the LCSH subject into the desired database category field (for example 699).

Tip: LCSH subjects can be identified by the MARC field 650 Ind 1=blank, Ind 2=0

Example Alma Normalization rule 1

when

(TRUE)

then

copyField "650.a" to "699.a" if (exists "650.{ ,0}")

end

Note: Copying all LCSH subjects can result in a very long list of subjects

We chose to focus on the Top 30 occuring LSCH subjects. The identification of these subjects was a quick process done using the MARCEdit tool.

To only generate the database categories subjects for select LCSH subjects nominate the desired LCSH subjects in the normalization rule.

Example Alma Normalization rule 2

rule "Copy 650 Social science to 699 Field"
priority 31
when
(not exists "699.a.Social sciences") AND ((exists "650.{ ,0}.a.Social sciences.") OR (exists "650.{ ,0}.a.Social sciences\\\\."))
then
addField "699.a.Social sciences"
end

rule "Copy 650 Science to 699 Field"
priority 30
when
(not exists "699.a.Science") AND ((exists "650.{ ,0}.a.Science") OR (exists "650.{ ,0}.a.Science\\\\."))
then
addField "699.a.Science"
end

Example Alma Normalization rule 2 acts as a white list nominating which subjects you wish to use. At any point in the future this list can be edited by editing the normalization rule.

Note: In your Normalization rule it is important to capture the LCSH with end punctution and without.

Note: The Normalization rule looks to confirm the 699 of the subject doesn't already exist. This is to ensure duplicate 699s are not created.

Note: For information about Alma Normalization rules generally go to: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/040Metadata_Management/070Working_with_Normalization_Rules

Step 2: Create set of database records

Create a set of bibliographic records that includes the desired electronic collections. You will use this set in Steps 3 and 4.

We use a special field to identify our database records, this field is used in generating our logical set of database records.

Step 3: Create Process

For information of how to add normalization rules to processes see the documentation:

https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/080Configuring_Resource_Management/070Configuring_Processes

Step 4: Run Process

Rational for deciding to use LCSH subjects

1. Impractical to maintain an internal database categories list
2. All database bibliographic records already contain LCSH fields
3. The decision to copy only 650 $a and not to capture other subfields, valid LCSH geographic fields, and valid LCSH events fields was made to keep the categories list concise and broadly applicable.

Should you wish to copy subfields into the database categories you can do this by copying them into the subfield b or c of your database category field (for example 699 $b and $c).

4. The decision of which LCSH subjects to use was based on analysis of LCSH subjects present on database records. The top 30 most used subjects were chosen.