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

    General

    General

    What controlled mechanisms options does Alma offer for for monitoring cataloging standards?

    There are various methods of using controlled mechanisms for monitoring cataloging standards. 
    These methods will depend on the library workflow as well as the method of cataloging. The methods are not mutually exclusive (both can be used simultaneously)
    1. One option is to use the “brief record” methodology. In this mechanism records are assigned varying levels based on either the values in fields (such as LDR position 17) or the presence of fields (such as 020 or 022). There are two groups of predefined sets of rules provided in the default Alma environment. They may be used “as is” or customized by each institution. In this way each record is assigned a level and based on that level it can be either retrieved for manual update or put into a set for global update. For more information see:
      https://knowledge.exlibrisgroup.com/@api/deki/files/43376/Resource_Management_-_Brief_record_levels_functionality_in_Alma.pptx
    2. Another option is to make a group of normalization rules which can be activated when the record is saved in the Metadata Editor or imported via an import profile.Alma includes a wide variety of default normalization rules which may be applied. They can also be customized, and shared by each institution. For more information see:
      https://knowledge.exlibrisgroup.com/@api/deki/files/42089/Rules_-_Normalization_rules_and_processes.pptx
      https://knowledge.exlibrisgroup.com/@api/deki/files/42165/Rules_-_Normalization_rule_examples.docx
       
    3. A third method is to retrieve records using indication rules and in this manner find records which do not conform to MARC cataloging standards and fix them with normalization rules.  For example there are rules which can fix and populate the 008 position 7-10 from the 260 or 264 subfield c.  Another rule can make LDR pos. 18 be "i" if 040 subfield e is RDA.  Here is an example:
       

      rule "If 040 e is RDA then make LDR pos 18 be i"

          when

             ((exists "040.e.rda") OR (exists "040.e.RDA"))

          then

              replaceControlContents "LDR.{18,1}" with "i"

      end

     

     

    What options does Alma support for resource management?

    Alma offers great flexibility in the ways institutions and consortia manage their cataloging, by providing the ability to manage local holdings and collections as well as shared resources (e.g., resources from the consortia or from the broader Alma community).
    Alma’s centralized metadata management environment (Metadata Management Service, or MMS) supports both traditional and new methods for cataloging, which allows libraries to move into a shared metadata environment in a way that best meets local needs and policies. This includes support for local catalogs and local fields in shared records in the Network Zone.
    The Metadata Management System includes three primary areas: the Institution Zone, the Network Zone, and the Community Zone. This hybrid model allows institutions to manage their unique local collections while supporting a shared consortial catalog, as well as a global Community Catalog.
    The Institution Zone represents the single library, and it is the basic level of data and workflow management in Alma. An institution [library] can link its inventory records to the metadata records in the Community Zone or the Network Zone, either of which eliminates the need to download these records to the local catalog. In addition, a library can copy catalog (or download) records from shared catalogs (Community or Network) into the local Institution Zone catalog. The Community Zone also contains authority catalogs that are synchronized against the relevant authorizing agency, ensuring individual institutions have access to the benefits of authority control without having to invest their local resources in synchronizing the authority files themselves.
    Furthermore, Alma is designed using an open data philosophy with records in the Community Catalog fully open to, owned by and stewarded by the Alma community. Ex Libris claims no rights of ownership nor restricts the use or reuse of these records.
    Record import and publication is considered a core function, and may be set up and run as a frequent process in Alma without intervention from Ex Libris. Libraries will set up one or more import and publication profiles, which can then be used to automatically import and export records from different sources on an ongoing basis. These processes may also be run on demand by the library.
    Alma supports the ability to import records in bulk on demand or according to a schedule. It will preserve unique fields and lowered encoding levels, though each condition may be logged when the incoming records are validated. The rules by which it imports records are set up in “import profiles.” Each site may set up many import profiles—for records from different sources, containing different data types, etc.
    Alma supports the ability to load records in one of the supported metadata schemas (presently MARC 21 for bibliographic, holdings, and authority records, as well as Dublin Core). Data that does not align with a supported schema must be mapped into a valid form before being imported.
    When importing any record, Alma goes through specific steps according to the rule of the appropriate import profile. It validates each record for encoding and content. It checks for matching records that already exist in the catalog, then can be set up to either merge, overlay, ignore (importing anyway), or flag matched records for review.
    Finally, it runs additional services. The additional services work according to the rule framework. For example, an additional service might be to extract inventory information and create holdings and item records.
    Another service is to flag brief records. These are identified by checking for the presence of a combination of fields, including call number, title, publication statement, subject, etc. If the default rules do not suit a site’s needs, libraries may design additional validations and services and bind them to import profiles.

    How does Alma manage inventory control of library holdings?

    Alma inventory provides the institution with the capability to manage the following types of resources:
    Alma’s inventory menu interface, designed for non-catalogers, enables staff to enter library information for:
    The figure below illustrates the inventory component as it relates to the overall Alma architecture.
    Alma’s inventory is comprised of the intellectual entity (IE), a middle level, and an item.
    Intellectual Entity (IE)
    The IE is the resource that is managed. The IE provides a pointer to the metadata (MMS) record at the inventory level. Within Alma, the IE is mostly transparent and is not discoverable on its own, but allows Alma to point to a combination of community and institutional records from the local inventory.
    Middle Level
    The middle level as a grouping level for the different resource types:
    • For physical resources, the middle level contains the holdings information such as the Main library or Law library holdings.
    • For electronic resources, the middle level contains the electronic service information such as full text or selected full text.
    • For digital resources, the middle level contains the representation information such as master copy or derivative copy.
    Item
    The item is the inventory level for fulfillment and usage. This level inventory contains information about the physical item, the electronic portfolio, or the digital file.
    Electronic Collection
    For electronic resources, the electronic collection is the top level of the electronic hierarchy (electronic collection > electronic service > electronic portfolio) that is discoverable in Alma. In Alma, the electronic collection is the inventory unit that is purchased, activated, and maintained.
    Physical
    The following example illustrates a book with three copies with holdings in the main stacks and off-site storage.
    The following example illustrates an ongoing serial with three issues with holdings in Periodicals.
    At the item level, book copies are handled differently from serial issues. Each issue of a serial contains different content and is not generally interchangeable for fulfillment purposes. Book copies can be interchangeable for fulfillment purposes.
    Electronic
    The following example illustrates a single title that is offered by two vendors.
    When bibliographic data is sufficient in the Community Zone, the institution can have the resource and title list linked from the Community Zone on activation of your electronic collection. Activation can include a complete vendor bundle or specific titles for a selective service.
    Linking through the Community Zone allows the institution’s local inventory to benefit from any changes to global access or descriptive information.
    Digital
    The following digital example illustrates a thesis with a master and a derivative representation.

    Can Alma help with identification and flagging of potential duplicates of content?

    Alma provides the capability to perform overlap analysis for electronic resources. This function enables you to compare the content of electronic collections in order to determine where there may be a subscription overlap.
    Alma also supports a Duplicate Title Analysis tool. You can run a job to create a report that identifies duplicate bibliographic records. Duplicates are determined by looking for a match on parameters such as:

    Is there a unique ID number for each bibliographic, holding and item record?

    Alma automatically generates a unique ID for every bibliographic, holding and item record. This is a 15 string number, (the last three digits being the institution ID). An example of the unique ID for a bibliographic record:
    For holding records:

    Does Alma support the concept of brief bibliographic record levels?

    Alma supports multiple brief record levels. Varying levels of brief records can be defined using normalization rules.
    An example of defining a brief level is shown in the following screen capture:
    Ten levels of brief records can be defined from 01 through 10, where 01 represents the most brief record and 10 represents the most full brief record.
    Parameters in import profiles allow for defining the handling of records with a brief level.

    Local Fields

    Can library defined fields be used for local data?

    As part of Alma’s standard support of the MARC21 standard, all local fields (e.g. 9xx, x9x, etc.) can be used by the library. These fields can be renamed and used for local data purposes. In addition, Alma supports the option of loading Extension Packs. Extension packs for a metadata profile 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.

    Format Support, Standards

    What metadata schemas are supported in Alma?

    Alma’s infrastructure includes robust, cross-schema metadata support, allowing libraries to manage records stored in the different standards available today, as well as providing an environment for new schemas as they are created and adopted by the community. This also provides the ability to crosswalk data between supported schemas, as well as when importing and exporting records.
    Alma supports MARC 21 (with RDA extensions) bibliographic, holdings, and authority formats, as well as Dublin Core (including all terms in the dcterms namespace). We are presently evaluating the best approach to handling collection-level description of EAD files. The infrastructure supports the ability to extend to add additional vocabularies in the future. Supported metadata schemas may be searched, edited through the metadata editor, imported and exported. Records may be cross-walked from one format to another either on import or export. For example, a MARC21 bibliographic record may be cross-walked to Dublin Core when publishing to an OAI-PMH repository.
    This approach to multi-schema support aligns to the principles of Dublin Core application profiles. Alma maintains a metadata registry that tracks valid fields/terms, along with administrative information about each field (such as the controlled vocabulary to validate against). Our implementation allows schemas to be edited and managed with no loss of granularity—they are not being cross-walked to an internal schema, and therefore losing the advantages of native multi-schema support. Alma supports the ability to load records in one of the supported metadata schemas (presently MARC 21 for bibliographic, holdings, and authority records, as well as Dublin Core). Data that does not align with a supported schema must be mapped into a valid form before being imported.
    EAD is supported for exporting collections in EAD format.
    Alma supports the following crosswalks out of the box:

    What cataloging formats are supported in Alma?

    Edit section
    Alma’s infrastructure includes robust, cross-schema metadata support, allowing libraries to manage records stored in the different standards available today, as well as providing an environment for new schemas as they are created and adopted by the community. This also provides the ability to crosswalk data between supported schemas, as well as when importing and exporting records.
    Alma supports MARC 21 (with RDA extensions) UNIMARC and KORMARCbibliographic, holdings, and authority formats, as well as Dublin Core (including all terms in the dcterms namespace).
    We are presently evaluating the best approach to handling collection-level description of EAD files. The infrastructure supports the ability to extend to add additional vocabularies in the future. Supported metadata schemas may be searched, edited through the metadata editor, imported and exported. Records may be cross-walked from one format to another either on import or export. For example, a MARC21 bibliographic record may be cross-walked to Dublin Core when publishing to an OAI-PMH repository.

    Is Alma updated Alma with changes to the standards e.g. MARC21?

    The metadata profiles in Alma are updated with standard changes twice a year.

    How does Alma deal with a variety of formats (electronic, digital, print)?

    Alma can manage Physical, Electronic and Digital resources (P,E and D). A physical book, a digital copy of it and an electronic version of that book can be linked to the same bibliographic record which is managed in Alma’s main metadata catalogue (MMS). The highest level of any entity managed by Alma is called the ‘Intellectual Entity’. This entity can have three types of child: Physical (Holding), Electronic (Service) and Digital (Representation). The following diagram illustrates Alma’s object’s data model:
    All three types of material are managed in the same repository.
    Objects that share the same descriptive information are linked. The following is a screenshot taken from Alma which represents a record which has two versions: one physical and one digital, the green text ‘Availability’ points to the two available versions:
    The Digital resources are based on the same principle and the data model looks as follows:
    Where the metadata description will link to an Intellectual Entity (IE) that represents a coherent set of content. Representation are set of file/s grouped in an IE by a common usage (e.g. archival tiffs versus derivative copy jpg) and the file can be any supported digital object such as JPG/MP3/pdf etc.

    Does Alma support MARC 21 holdings records?

    Alma supports MARC21 holdings. The holding record provides the link between the bibliographic record and the physical inventory (items), as can be seen in the following diagram:

    What is the data model for e-resources?

    For electronic resources, the data model looks like this:
    For electronic resources, the holding-level record corresponds to the collection of aggregated electronic resources offered by the vendor. It contains information about the available services (e.g., full text, abstract, etc.). The item-level record corresponds to the Portfolio - the specific coverage, service(s), and links information relevant for a specific title in the collection.

    Does Alma support RDA and AACR2?

    Alma supports RDA and ACCR2. The MARC 21 schema in Alma supports the updated fields for bibliographic and authority records that support the RDA descriptive standard. These fields are fully editable and searchable, and may take advantage of the assisted text entry for a controlled vocabulary.
    Alma supports RDA and ACCR2. The MARC 21 schema in Alma supports the updated fields for bibliographic and authority records that support the RDA descriptive standard. These fields are fully editable and searchable, and may take advantage of the assisted text entry for a controlled vocabulary.

    Does Alma support Linked Data?

    See also Linked Data in Repository Search, Indexing
    Linked Data is a major development initiative for Ex Libris.  Linked data elements are now available while using the Alma MD Editor and in repository search results for titles (All titles, Physical titles, Electronic titles and Digital titles) in the Institution Zone.
    While working with bibliographic records in the MD Editor, the record's link data element information is available in the lower pane of the editor.

     

    The Linked Data List page displays the following information:
    This is pulled according to context. The default context is https://open-na.hosted.exlibrisgroup.com/alma/contexts/bib.
    If there is an active Linked Data integration profile with a path to a context, this context is used.
    A Linked Data integration profile does not need to be created in order to access linked data from the Alma Repository Search results. However, one is required to expose linked data in the JSON-LD format.
    For ISBN, ISSN, and OCLC, the field content is displayed. For creator and subject, the value of the heading is displayed.  Click the URI link of interest to access the linked data.

    What is Alma's approach to BIBFRAME?

    Refer to the response under General - Standards

    Integration with external applications

    Can Alma integrate with OCLC Connexion?

    Alma’s Integration Profile framework may be utilized for integrating with cataloging clients such as the OCLC Connexion client. Setting up the Integration Profile with the requested normalization, validation and merge routines will enable direct upload of externally cataloged records into Alma’s repository:
    Staff can define the relevant parameters in the Connexion client (for example) that will link and automatically download records from OCLC Connexion to Alma:
    After choosing the Export option in Connexion, the following will display:

    Total views:

    3
    • Electronic
    • Digital
    • Physical
    • Holdings
    • Items
    • Activated electronic resources
    • Digital objects
    • System Control Number (035 field) with or without a prefix such as (oclc)
    • ISBN
    • ISSN
    • Other Standard Identifier (024 field)
    • MARC21 to UNIMARC and vice versa
    • MARC21 to KORMARC and vice versa
    • Dublin Core to MARC21 and vice versa
    • Vocabulary field
    • Linked data URI
    • Label

    Total views:

    3
    • Was this article helpful?
    //doorbell.io feedback widged