Alma integrates the BIBFRAME and BFLC ontologies into its metadata infrastructure to support flexible, standard-based cataloging workflows. This section outlines how Alma leverages these ontologies to enhance record creation, editing, and validation.

Key aspects of Alma's ontology usage include:

• Alma uploads the BIBFRAME and BFLC ontologies into its metadata configuration and application profile. This enables Alma to update the ontology as needed while maintaining backward compatibility for existing records.
• When updates to the ontology are released, the Alma team analyzes them and integrates them into the application profile.
• The Alma LOD editor currently supports the creation of records and templates that are defined from the Key classes of Work and Instance.
• When creating or editing a record, Alma's editor suggests appropriate properties and classes based on the relationships defined in the ontology. For example, when creating a bf:Instance, the editor suggests the property bf:provisionActivity for a section. However, this property is not suggested when creating a bf:Work, as it is not defined as applicable for this class in the ontology.
• Note that some properties in the BIBFRAME ontology are not tightly constrained with "Used with" (domain) and "Expected Value" (range) definitions. As a result, properties like bf:note and bf:agent are broadly applicable and are always suggested by the editor, regardless of the class being edited.
• There are some properties and classes that have moved from the BFLC extension into the BIBFRAME main ontology. Alma stores these duplicated entities as part of the BIBFRAME application profile for backward compatibility. However, when creating a new record or editing an existing record, the BIBFRAME editor does not suggest these duplicated or deprecated properties and classes to the user.