Skip to main content
Ex Libris Knowledge Center

Alma September 2016 Release Notes

The Alma September release provides numerous new features and enhancements. Some of these enhancements are a result of Idea Exchange initiatives.
PDF.png Download a PDF of the Release Notes - Note that the PDF includes the online help pages that describe the core functionality of the new features.

What's New?

The following sections present the new and changed features in this release of Alma.


  • idea_exchange.png Idea Exchange: The Receiving note field was changed in the PO line Summary tab from a text field to a text area field. The field now enables you to enter multiple lines of text.

Resource Management

Digital Resource Management

In the Alma December release, there will be a change to the publishing platform for the Dublin Core format. The dc:identifier field, automatically added to MARC records when published as Dublin Core (using the General publishing profile), will be expanded to include the institution code in addition to the MMS_ID: <identifier>alma:{INSTITUTION CODE}/bibs/{MMS_ID}</identifier>. This will serve to better align the identifier with its potential use in Alma RESTful APIs, and make the identifier field distinct for every institution. If you have an existing integration that uses the Dublin Core format, and specifically the MMS_ID, ensure that you make the necessary changes in the external system that uses the data. Please contact Ex Libris Support if you are unsure whether this change affects your current integration.


Resource Sharing

Collaborative Networks


Administration and Infrastructure


  • The library code was added to the GET PO Lines API (GET /almaws/v1/acq/po-lines).
  • The conf/jobs API now handles scheduled jobs as well as manual jobs. For detailed information, see and
  • Dublin Core is now an accepted format for BIB APIs.
  • The Resource Sharing Requests API now includes a new field, willing_to_pay
  • The Linked Data API now uses the same type of hyphens that are included in the bibliographic record in the wikidata link ISBN field.
  • XSD fields were changed to use xs:string instead of xs:long when representing ID values.
    The API response that includes mms_id as numeric (xs:long) in the following XSDs:
    • rest_bib.xsd
    • rest_holdings.xsd
    • rest_item.xsd
    • rest_user_resource_sharing_request.xsd
    was changed to text (xs:string).
    This is due to a defect in some clients (mainly JavaScript-based) that causes long numbers to be rounded incorrectly. If you use the above APIs with XML, no change is visible. If you use them with JSON and parse the output using string manipulation such as RegEx, these fields now appear surrounded by apostrophes.

Known Issues

  • When importing an EOD file using the New Order profile, if the location of the item does not have a call number type, the call number type of the institution should be used as the alternative call number type. Currently, however, no alternative call number is used.
  • Related to merging bibliographic records in the MD Editor, if there are no requests, the Merge Records and Combine Inventory pop-up window does not display a count of 0 (zero) requests. The count appears for requests only when it is greater than 0 (zero). The count should also appear as 0 (zero) requests when there are no requests.
  • Regarding the autocomplete/pop-up assistance being provided for several UNIMARC fields in the MD Editor, there is a known issue related to UNIMARC 327 $a and 327 $b. These subfields are based on the same functionality and as a result, the pop-up suggestions in the MD Editor suggests both subfields’ values when entering content in either the 327 $a or the 327 $b.
  • Fixed position fields (control fields) cannot be modified using the extension loader (extension packs) at this time.
  • When creating an OCLC Connexion import profile in a Network Zone member institution with the Use NZ option selected, the Use NZ record option is used upon finding a match. Currently, there is no possibility to select the Merge, Overlay, or Do not import options instead.
  • When a record is deleted in Alma, the headings associated with the record are still available when browsing bibliographic headings.
  • The Total electronic portfolios imported count in the MD import report does not take into account the portfolios imported in the first file that is imported when the import is split into several files.
  • The URL condition that was added as an advanced search option under Electronic Collection when searching for electronic titles is not functioning properly.
  • A user with the Physical Inventory Operator role can edit a holdings record using the View Inventory option in the MD Editor, although the user should not have this capability and cannot perform this action from the List of Holdings.
  • Was this article helpful?