Devorah May Working Copy
RN Order:
RN Order:
| 1. FUL - Fulfillment and Resource Sharing | 6. COL - Collaborative Networks (Consortia) |
| 2. MDM - Metadata & Linked Open Data | 7. ADM - User Experience, Accessibility & Infrastructure |
| 3. AI - Artificial Intelligence | 8. ANA - Analytics and Insights |
| 4. RM - Resource Management | 9. API - APIs |
| 5. ACQ - Acquisitions |
This is the order of the categories, as they are to appear.
RN Story Tags
(URM-XXXXXX) TBD
Text LOD.
(URM-XXXXXX) TBD
Text.
(URM-XXXXXX) TBD
Text.
(URM-XXXXXX) TBD
Text.
(URM-XXXXXX) TBD
Text.
Main Features
Erez
(URM-319471, URM-318578) Storage Location ID Can Now Be Managed as a Closed List
A new option is now available to manage the Storage Location ID field as a controlled list on the physical item. Enabling this feature also provides a configuration screen for maintaining the vocabulary entries. This enhancement is particularly beneficial for libraries that work with remote storage facilities and maintain a large number of Storage Location ID entries on their physical items in Alma.
- Contact Support to enable this feature.
- This capability is available for up to 100,000 storage IDs.
- The <More...> indicator is for informational purposes only and will be updated in a later release when the Item page moves to the NG layout.
For more information, see Storage Location ID.
(URM-319073/URM-319489) Update MARC21 Bibliographic Resource Types
Idea Exchange URM-319073 URM-319489This update enhances the Alma MARC21-Based Resource Type classification to improve the accuracy, coverage, and usability of bibliographic resources. Alma determines the resource type automatically based on metadata fields, enabling more precise filtering and reporting. The enhancement introduces additional resource types that were previously unavailable, enriching the classification system.
Impact: Users will benefit from more granular and accurate resource type categorization in Alma, improving search facets, analytics reporting, and overall system functionality.
For the filter to apply to existing types, the data must be re-indexed. The next re-indexing is scheduled for the end of June 2026.
(URM-319488) Enhanced Sorting by Full Publication Date
Sorting was previously limited to the publication year. With this update, when metadata is available, the system now sorts by the full date, Year, Month, and Day. This ensures consistency with existing indexing and sorting logic. Users managing daily publications will benefit from precise chronological sorting by full publication date, improving discoverability and providing a consistent experience.
For more information, see Sorting Search Results.(URM-238773) Expose Linked Headings in Simple Record View
Idea Exchange URM-238773
Adina
(URM-239313) Relations for BIBFRAME from the LOD Editor
Alma LOD Editor supports BIBFRAME relations that contain the following structure
(URM-236917) HEADING
Alma now supports easy navigation between different record views for each user to find the view that is most suited for them.
Also we are introducing a new condensed display for BIBFRAME records into a table view, supporting the option to view as much metadata as possible within a section and using the familiar display known to catalogers from MARC formats.
(URM-306215) BIBFRAME and BFLC Ontology Update
Alma has updated the metadata standard of BIBFRAME and the BFLC extension to support the latest version 3.0, thus keeping up with the standard to support valid BIBFRAME creation within Alma.
Additionally, a Restore action is now available on the Linked Data Active Profile views to restore the out-of-the-box default value for any changes applied to an ontology.
For more information, see Customizing Field Labels and Descriptions.
(URM-324422) New View Options for BIBFRAME Work Record
To enhance interoperability of BIBFRAME, the BIBFRAME work record now includes the Turtle (.ttl) view mode option.
(URM-322918) Enhancements to the Linked Open Data Editor Form and Templates
When editing a BIBFRAME record, section-level and field-level actions for adding, duplicating, and deleting sections are now available.
When hovering over the Add Section/Field or Duplicate Section/Field icons, a horizontal line appears, indicating where the section/field will be added.
It is still possible to scroll to the end of the sections and use the Add Section/Add Field buttons to the end of the sections.
Additionally, BIBFRAME records and template sections can now be reordered using the Reorder button. The new order is then applied to newly created records and templates.
Lili
(URM-322839) Improved Language Support in AI Metadata Assistant, Using Optical Character Recognition
The AI Metadata Assistant enables catalogers to easily extract metadata from images and files to streamline the cataloging process. The text is extracted from images by the AI LLM model used in the assistant, as part of the metadata generation process. However, for some languages, scripts, and resource types, lower LLM optical character recognition accuracy may result in lower metadata quality. It is now possible to apply a dedicated OCR tool to improve results for those resources — the LLM then generates metadata based on the text extracted by the OCR tool, rather than directly from the image, leading to improved support for more languages and resource types. Catalogers can select their preferred text extraction method for the specific resource being cataloged:
- AI Metadata Assistant — text processed by the LLM as part of the metadata generation (as today).
- Azure Document Intelligence — an advanced, AI-based OCR service with extensive language support.
- Tesseract — a seasoned, robust OCR tool for extracting text from images and files.
This is especially beneficial for libraries cataloging resources in languages and scripts with lower LLM OCR capabilities (e.g., non-Latin scripts).
(URM-325022) Enrich Bibliographic Records in Bulk Using a Streamlined Copy — Cataloging Process and AI Title Matching
A new job, Enrich Bibliographic Records, enables the library to enrich a set of up to 1000 records, streamlining the search for matching records in its existing search profiles and copy-cataloging partners, filtering and assessing the results, and providing copy-cataloging recommendations to the cataloger.
As a first step, the Enrich Bibliographic Records job supports searching in Alma copy-cataloging partners to avoid overwhelming external resources with a large volume of search queries they’re not prepared to handle. Support for external copy-cataloging partners will be added in the future, based on the community's needs and subject to their ability and agreement to handle a large volume of search queries.
This is especially useful for libraries enriching their bibliographic records from copy-cataloging partners, making the process easy, fast, and efficient.
For more information, see LINK.
Tamar
(URM-322777) HEADING
Until now, the assistant has provided the transaction ID and the invoice line ID/POL ID. Now, the assistant provides the POL number and invoice number as displayed in Alma UI for transactions:
Additionally, the assistant provides a link to the PO line and invoice.
For more information, LINK.
(URM-322774) HEADING
TEXT
For more information, LINK.
Additional Enhancements
- May 2026 Metadata & Linked Open Data URM-218454
To provide consistent Analytics reporting across MARC21, UNIMARC, and CNMARC, UNIMARC and CNMARC data were added to Analytics to align with the data already available for MARC21.For more information, see Bibliographic Details.
- May 2026 Metadata & Linked Open Data URM-322524
(URM-322524) GND Profile Updates:- One value of the CV list of 043 $c was altered
- New CV lists were added to 100 $l, 110 $l, 111 $l and 130 $l – the lists are identical in these four subfields and are also identical to the CV list in 377 $a, which is already available in Alma
- One code was added to, and the description of one of the already existing codes was altered in the CV list of 377 $a (this updated list is the one added to 100 $l, etc.)
- All existing codes of the CV list of 384 $a were altered ($0 was added), and several new codes were added
- The attribute “repeatable” of 384 $0 was changed from true to false
- New CV lists were added to 400 $l, 410 $l, 411 $l and 430 $l – the lists are identical to the ones mentioned above (100 $l, etc., and 377 $a)
- Codes were added to the already existing CV lists of 400 $9, 410 $9, 411 $9 and 430 $9 and the description of one of the already existing codes was altered
- New CV lists were added to 450 $9 and 451 $9 – the lists are identical to the codes added to 400 $9, etc., except for <value code="v:ISO639: zgh">Tamazight</value>, which was not added to 450 and 451 but to 400, 410, 411 and 430
- One code was added to the CV list of 670 $a (this code is a combination of $a and $u in the same way as is in 384 with regards to $a and $0)
- The CV list of 670 $u was deleted (because the one value that was available there is now included in the newly added code of 670 $a)
- Two existing codes of the CV list of 680 $a were altered because they contained decomposed special characters, which were replaced by the precomposed versions; otherwise the codes remained unchanged
- New CV lists were added to 700 $l, 710 $l, 711 $l and 730 $l – the lists are identical to the ones mentioned above (100 $l, etc., 377 $a, and 400 $l, etc.)
- New CV lists were added to 700 $9, 710 $9, 711 $9, 730 $9 and 751 $9 – the lists are identical to the one mentioned above (450 $9 and 451 $9)
- May 2026 Metadata & Linked Open Data URM-319214
(URM-319214) When using the source of Wikidata for a lookup and searching with a different language than the default of English, the language tag will be saved for the specific field in the record, allowing the update of the record without reverting back to the default. - May 2026 Metadata & Linked Open Data URM-318309
(URM-318309) In the new UX titles and holdings searches, a new display field, Short Title, was added that contains only the title proper (245 $$a). This field is hidden by default, but can be added to the table or record displays by configuring the views. It is especially useful for users who want to minimize the space the title takes in the table view, and can now choose to display a Short Title column instead of the Title column.This new field was also added when exporting all fields from the search results to Excel.
Short Title Column