678 results found

1. Release notes should be posted

   Currently when LibOW is updated to a new version, no notice is given, and no list of new features / enhancements is provided. The changes are sometimes significant. For instance, recently a set of new webhook triggers was added. Release notes should be posted somewhere for LibOW users to review.

   12 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   Completed  ·  1 comment  ·  Library Open Workflows  ·  Delete…  ·  Admin →

2. Holdings Display

   Please revert the display back to what it was before August 2025 updates for viewing holdings for a title. Go back to a full screen (not a sliding window). Show POL in holdings again. This helps serials work when needing to move items to a suppressed record to be able to see the POL and the receiving dates displaying easily.

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Acquisitions - General  ·  Delete…  ·  Admin →
   Completed  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

   Starting from November release it is possible to expand the sliding pannel into a full page as well as resize it using the drag&drop option.

   Best,

3. Browse Shelf Listing for call numbers: Improve search for letters with umlauts

   Sorting of the whole call number index is generally correct - scrolling through the list, page after page, we see that the call numbers are sorted correctly. But if we search for a special call number (search field "signature"), we do not always get the right entry when it comes to umlauts.

   The umlauts should sort like that:
   ä = ae
   ö = oe
   ü = ue

   When searching, it looks like this is the sorting:
   ä = a
   ö = o
   ü = u

   Example: The results from Bo to Brym in the order when scrolling through the pages:
   Boci-4
   Boci-5
   Boci-6
   Boci-7
   Boci-8
   Boci-9
   Boci-10
   Boci-11
   Boci-13
   Böhm (5x)
   Böhm-1
   Böhm-2
   Böhm-3
   Böhm-4
   Böhm-5
   Böhm-6
   Böhm-7
   Böhm-8
   Böhm-9
   Böhm-10
   Böhm-27
   Bofi
   Bofi
   Bofi
   Bohl
   Bort
   Bort
   Brat-1
   Brat-5
   Brat-21
   Brat-25
   Brat-30
   Brat-31
   Brea
   Brea-1
   Brea-2
   ...
   Brea-38
   Brym
   Brym-1
   ...

   So, you can see the call number index sorts correct scrolling page after page.

   When searching for Böhm, the call number is sorted it the third place, but the terms before are not the right once - see in the attached screen.

   Sorting of the whole call number index is generally correct - scrolling through the list, page after page, we see that the call numbers are sorted correctly. But if we search for a special call number (search field "signature"), we do not always get the right entry when it comes to umlauts.

   The umlauts should sort like that:
   ä = ae
   ö = oe
   ü = ue

   When searching, it looks like this is the sorting:
   ä = a
   ö = o
   ü = u

   Example: The results from Bo to Brym in the order when scrolling through the pages:… more

   •  

   417 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   4 comments  ·  Resource Management - Physical  ·  Delete…  ·  Admin →
   Completed  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

   Thanks everyone who supported this idea and helped analyzing the request.

   Institutions whose Solr search language is set to German will now have German sorting of umlauts in the Browse Shelf Listing search.

   As this requires full indexing for call number, the effect of this enhancement will be seen after the November semi-annual indexing is completed.

   Best, Alma Product.

4. Search for ISBN with hyphens

   Previously, it was possible to search for ISBNs with hyphens (e.g., 978-82-693905-0-6) using the "All titles – keywords" search in Alma. However, this functionality no longer works with the release of the new title search.

   While the search still works if you manually switch from "keywords" to "ISBN," it would be much more convenient if ISBNs with hyphens were recognized in the keyword search as well. As it stands, users are forced to repeatedly switch search types, resulting in unnecessary clicks and a less efficient workflow.

   129 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Resource Management - General  ·  Delete…  ·  Admin →
   Completed  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

   Hey all, thank you for bringing this to our attention. support for keyword search for ISBN with hyphens has been added as part of the Alma November 2025 release.

   
   

5. Request Access Type in Title Report harvest

   In COUNTER R5.1, title reports are getting more important as the list of data type has been expanded. A lot of non-journal and non-book usage (e.g. conference proceedings, reports, newspapers, theses, etc.) can only be found in title reports. However, in R5.1, while data type is a mandatory attribute that vendors have to send in title reports when the reports are requested, Access type is not. Access type includes: Controlled, Open Access and Free to Read. In order to get Access type to be included in title reports, the request queries must include the request for Access type. Otherwise, they will be lacking in the reports.

   If we do not have access type included in title reports, how are we going to distinguish which usage is a result of a subscription, which usage is from open access publications? This information is crucial to calculate cost per use.

   Salesforce case: 07811212

   Desirable outcome: Request for Access Type in the request queries for Title reports when harvesting COUNTER usage reports.

   In COUNTER R5.1, title reports are getting more important as the list of data type has been expanded. A lot of non-journal and non-book usage (e.g. conference proceedings, reports, newspapers, theses, etc.) can only be found in title reports. However, in R5.1, while data type is a mandatory attribute that vendors have to send in title reports when the reports are requested, Access type is not. Access type includes: Controlled, Open Access and Free to Read. In order to get Access type to be included in title reports, the request queries must include the request for Access type. Otherwise, they… more

   16 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Acquisitions - General  ·  Delete…  ·  Admin →
   Completed  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

   Hi everyone, thank you for supporting this idea.

   I'm happy to announce it has been implemented as part of the February 2026 Alma release.

   Refer to the Alma release notes for more information.

   Best,

   Alma Product

6. Revert the changes made to Job: Update PO Lines Information Advanced

   This really pertains to Admin >> Run a Job, but please revert the change you made to the Job: Update PO Lines Information Advanced. Currently, the job will NOT run if there are invoices on the PO. Before this change was made it did not matter.
   It does not matter to the library because the terms of a continuous order can and do change (it was a subscription, now it is offered as a continuation order), how a library chooses to catalog an item can and does change (a title was a serial, then it became a monographic series) So we need to change the PO line type. That there are invoices on the PO is irrelevant - the order is continuing, we just need to change the order type. So now it is impossible to change a PO from type: Physical standing order non-monograph to type: Print Book standing order for an active order. Instead, to make this change, I have to close the existing PO AND create a new PO and send the new PO line /PO information to the vendor even though the order continues.
   The old job was very useful because a lot of our serial POs were imported into Alma with the wrong PO line type and we are still cleaning them up. So we need this job to do what it used to do.

   This really pertains to Admin >> Run a Job, but please revert the change you made to the Job: Update PO Lines Information Advanced. Currently, the job will NOT run if there are invoices on the PO. Before this change was made it did not matter.
   It does not matter to the library because the terms of a continuous order can and do change (it was a subscription, now it is offered as a continuation order), how a library chooses to catalog an item can and does change (a title was a serial, then it became a monographic series) So… more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Acquisition - PO & POLine  ·  Delete…  ·  Admin →
   Completed  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

   Hi all,

   The Update PO Lines Information Advanced job has been enhanced following the community's feedback.

   For additional information, please refer to the Release Notes

   Best,

   Liza and the Product Team

7. Support "Parent" fields in COUNTER R5.1 IR reports

   COUNTER R5.1 reports can be harvested into Alma, and then users can review these reports in Analytics.
   For ‘Item Reports’ (IR) not all “parent” fields are supported in Alma and in Analytics.

   Mandatory parent fields for IRA1 in R5.1 are:
   ParentTitle
   ParentAuthors
   ParentArticleVersion
   ParentDOI
   ParentProprietaryID
   ParentPrintISSN
   ParentOnlineISSN
   Parent_URI
   (See https://cop5.countermetrics.org/en/5.0.3/04-reports/04-item-reports.html)

   NOTE: If any parent information is included in an Item Report, the ParentDataType MUST be specified (see https://cop5.projectcounter.org/en/5.1.0.1/03-specifications/02-formats-for-counter-reports.html#report-body)

   These fields should be supported by Alma and Analytics.

   324 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Acquisitions - General  ·  Delete…  ·  Admin →
   Completed  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

   Hi everyone, thank you for supporting this idea.

   I'm happy to announce it has been implemented as part of the February 2026 Alma release.

   Refer to the Alma release notes for more information.

   Best,

   Alma Product

8. Searchability for MARC 361

   We would like to be able to search MARC-361 in Alma, if possible also specifically in subfields of the 361.

   https://www.loc.gov/marc/bibliographic/bd361.html
   https://www.loc.gov/marc/holdings/hd361.html

   107 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Resource Management - General  ·  Delete…  ·  Admin →
   Completed  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

   Hi everyone, thank you for supporting this idea.

   As of February 2026 release, Alma supports defining custom indexes for each institution based on Bibliographic data. This new infrastructure provides the flexibility for each customer to create their own search indexes tailored to their Bibliographic data.

   Refer to the Alma release notes for more information.

   Best,

   Alma Product

9. Portfolio loader and Multiple MMS

   When we load portfolios through the Portfolio Loader, Alma attempts to find a match based on the identifier in the Community Zone, in order to get the bibliographic records for the portfolios.
   When there are multiple MMS records in the CZ that match the searched identifiers, you get an error and no portfolio is loaded. Currently, there is no internal logic for the portfolio loader to choose between these records, even if some have no inventory at all.
   it would be useful to implement a logic that allow to choose between records, at least in the case that some have no inventory and some have it.

   When we load portfolios through the Portfolio Loader, Alma attempts to find a match based on the identifier in the Community Zone, in order to get the bibliographic records for the portfolios.
   When there are multiple MMS records in the CZ that match the searched identifiers, you get an error and no portfolio is loaded. Currently, there is no internal logic for the portfolio loader to choose between these records, even if some have no inventory at all.
   it would be useful to implement a logic that allow to choose between records, at least in the case that some have… more

   104 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Resource Management - Electronic  ·  Delete…  ·  Admin →
   Completed  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

   Hi all,

   I'm happy to update that this idea has been implemented as part of the November 2025 release.

   The portfolio loader now supports auto-selecting the preferred MMS (based on inventory and rank) in case of multiple matching records.

   read more about this option in the November 2025 release notes: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2025/Alma_2025_Release_Notes?mon=All#:~:text=Handle%20Multiple%20Matching%20BIB%20Records%20in%20Portfolio%20Loader

   Best, Alma Product

10. NR - Normalization rules editor -- fix display to ltr + use monospaced font

    1.
    Currently there's a problem with the NR editor when there are too many rtl characters (Hebrew, Arabic, etc.) in the NR, the whole display changes to rtl. This renders the NR unintelligible and makes editing it in Alma impossible -- you have to edit it outside Alma

    We would like the direction of the NR editor to be fixed to ltr regardless of the composition of the characters used

    2.
    We would like to have the NR editor use a monospaced font. This would make the code neater and easier to read

    •  

    24 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
    Completed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    Alma now supports XSL normalization rules, expanding its capabilities beyond the existing DROOLS support. This addition enables more advanced and intricate data normalization. The request of this idea can be addressed using the new XSL normalization rules. For detailed information on using XSL normalization rules, please refer to the May 2025 release notes available at: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2025/Alma_2025_Release_Notes

11. Purchase requests on network records

    When a purchase request is made in Primo VE from a record that belongs to the network, the purchase request shows error when clicking on Approve and order: Failed to create order.

    It should be possible to create purchase requests on records belonging to the network. The purchase request should be created in the IZ level and be managed there. The corresponding order, if the request is approved - should also be managed in the IZ level.

    5 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Acquisition - Purchase Requests  ·  Delete…  ·  Admin →
    Completed  ·  AdminZohar Shemesh (zohar.shemesh@exlibrisgroup.com, Ex Libris) responded

    Dear All,

    This is to inform you that this idea was implemented in Alma May 2025 Release:

    When ordering in Primo from the Network Zone (NZ), the purchase requests created in the Institution Zone (IZ) are now linked to the bibliographic record in the Network. Alma first checks for a local MMS ID linked to the bibliographic record in the Network. If such a record exists, Alma uses it for the purchase request. If it doesn't exist, Alma creates one and uses it.

    Thanks,

    Zohar Shemesh

    Alma Product Team

12. Index 532 field

    MARC21 field 532 should be indexed in Alma and Primo. This is important for accessibility notes.

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
    Completed  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

    Hi everyone, thank you for supporting this idea.

    As of February 2026 release, Alma supports defining custom indexes for each institution based on Bibliographic data. This new infrastructure provides the flexibility for each customer to create their own search indexes tailored to their Bibliographic data.

    Refer to the Alma release notes for more information.

    Best,

    Alma Product

13. General electronic service in Get It should built with information from the main bib and not from related record

    General electronic services are built using data from the context object.

    When there are related bibliographic records, the context object is sometimes created with the related record's information.

    As a result, the general electronic service has the related records information - e.g. ISBN.

    Desired outcome

    General electronic services in getit should use the main record's data and not related record's data.

    5 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    Completed  ·  1 comment  ·  Link Resolver  ·  Delete…  ·  Admin →

14. Add Alma support for microlanguages and language codes recognised by Library of Congress, including Austlang

    Alma’s support for Language for search indexing, facet, and display is hardcoded for 041 to the 3 digit MARC Code List for Languages.
    This excludes languages recognised by Library of Congress, such as Austlang languages which were recognised more than 6 years ago in 2018.
    This issue has been addressed in Primo in 2021 and 2022 with customer advocacy efforts, but remains a glaring omission within Alma.
    See details: https://igelu.org/primo-support-for-austlang-and-iso-639-3/

    The only option currently within Alma for searching this data is to use the keyword field to search by information such as C15, and then use the Language filter to limit to Australian languages (by MARC code aus).
    Even then, the Austlang language is not shown in the displayed metadata.
    Attempting to use the simple search Language field to query 041 metadata in Alma records when not on the MARC Code List is unexpectedly zero results.
    
    And for the advanced search Language field, Alma offers only a hardcoded dropdown menu of languages on the MARC Code List.

    Successful delivery of this idea would be:
    • Alma’s simple search by the Language field also returns results for all languages entered in the 041
    • Alma’s advanced search by the Language field also allows for text to be entered, and also returns results for all languages entered in the 041
    • Alma’s search results also displays in the Language field all languages entered in the 041
    • Alma’s Language facet also includes all languages entered in the 041 from results returned

    This is fundamental to reconciliation efforts to correctly recognise and represent First Nations peoples languages in the work of libraries worldwide, as well as hindering practical efforts by library staff to address past practices and report effectively on successful progress towards this in library systems.

    Note: This submission is related but not fully covered by https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/46338445-add-iso-639-3-microlanguage-names-to-alma-title-se

    Alma’s support for Language for search indexing, facet, and display is hardcoded for 041 to the 3 digit MARC Code List for Languages.
    This excludes languages recognised by Library of Congress, such as Austlang languages which were recognised more than 6 years ago in 2018.
    This issue has been addressed in Primo in 2021 and 2022 with customer advocacy efforts, but remains a glaring omission within Alma.
    See details: https://igelu.org/primo-support-for-austlang-and-iso-639-3/

    The only option currently within Alma for searching this data is to use the keyword field to search by information such as C15, and then use the Language filter to… more

    • 

    83 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    9 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
    Completed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    Hello all,

    I want to clarify the decision made regarding this request, as it should help make things clearer.

    First, we added the option to upload Controlled Vocabularies using a CSV or Excel file, making the process much easier than before.

    In addition, we enhanced the 041 $a OTB Controlled Vocabulary list to include ISO 639-3 languages, in addition to the existing MARC21 standard list. This extended list supports search, facets, and other functionality — offering more capabilities than most other lists in Alma. Any additional language codes (e.g., Austlang) can be added to this list by each institution according to its specific needs.

    Please note that due to a performance issue, the full functionality will be available in the February 2026 release. For more information on how to use it, please refer to the release notes and online help.

    Erez

15. Separate new and deleted portfolios behaviors of "Activate new portfolios associated with service automatically"

    "Activate new portfolios associated with service automatically?" has just 2 options (Yes and No), and it doesn't just control what happens when new portfolios are added to the collection; it also controls what happens when portfolios are deleted from the collection. I think there are probably additional use cases besides these as well.

    If "Activate new portfolios associated with service automatically?" is set to "Yes":
    
    New portfolios added to CZ collection are automatically activated in IZ
    Portfolios deleted from CZ collection are totally deleted from IZ

    If "Activate new portfolios associated with service automatically?" is set to "No":
    New portfolios added to CZ collection are not automatically activated in IZ
    Portfolios deleted from CZ collection become local and inactive in IZ and get a special status on the CZ updates task list, giving us a chance to check and either re-activate or activate in a different collection (say, if the portfolio moved to a different provider).

    We find these 2 options aren't granular enough for an important use case: There are many cases where we subscribe to a package that consists of all the titles offered by the publisher. We have perpetual access to the content published during the years we subscribe, and when the publisher issues a new title, it automatically joins our package. After entering our perpetual access data into our portfolios in these collections, we'd like to make sure they're not deleted by any CZ processes (as they're perpetual, so we want them to stay in our IZs!). However, we still want to make sure that when the provider adds a new title to the CZ collection, it is automatically added to our IZ.

    So, we want the "Yes" behavior for new portfolios but the "No" behavior for deleted portfolios, but there's no way to do that in Alma at present. An improved setup would have separate settings for new portfolios and deleted portfolios that each library could control, as shown in the attached mockup.

    As you can see, I have mocked up a new field "Delete portfolios removed from service automatically?" with the options "No, make local and inactive," and "Yes, delete completely." With this improvement, "Activate new portfolios with service automatically?" would just control the behavior of new portfolios, and the new "Delete portfolios removed from service automatically?" field would control the behavior of deleted portfolios.

    I shared this suggestion with colleagues in the CZMG, and I received support for the perpetual access use case as well as a suggestion of another use case: if a library has attached CZ portfolios to local records, they may wish to be able to control the additions and deletions behaviors separately so they are able to more closely control the portfolios attached to the local records.

    "Activate new portfolios associated with service automatically?" has just 2 options (Yes and No), and it doesn't just control what happens when new portfolios are added to the collection; it also controls what happens when portfolios are deleted from the collection. I think there are probably additional use cases besides these as well.

    If "Activate new portfolios associated with service automatically?" is set to "Yes":
    
    New portfolios added to CZ collection are automatically activated in IZ
    Portfolios deleted from CZ collection are totally deleted from IZ

    If "Activate new portfolios associated with service automatically?" is set to "No":
    New portfolios… more

    •  

    191 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Resource Management - Electronic  ·  Delete…  ·  Admin →
    Completed  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

    Hi all, Happy to share that starting from the May 2025 release it will be possible to define auto-activation and auto-deletion behaviors separately on services activated from the Community Zone. As before, all updates will be reflected in the CZUTL.

16. Create Alma search queries and sets with relative dates

    Give customers the ability to query Alma using relative dates. This functionality is currently only available in Alma Analytics, but we would like it to also be available for repository search.

    This functionality would be especially useful for creating sets, particularly logical sets that can be used to populate logical collections. One of the most common uses for collections is to showcase new materials (e.g., books, journals, databases, etc. acquired in the last 90 days). However, there is currently no way to build a logical set like this. The best one can do is to select the current year and then commit to updating the query each year. To be completely free of the need to manually update the collection, customers need a way to build queries using relative/non-fixed dates (current date minus 90 days). Ideally, this option should be available for all date types but, for the purpose of this use case, should at least include creation date, activation date, and publication year.

    An alternative solution to this problem would be to allow customers to create a logical set/collection from an Analytics report. This would give customers the ability to use relative dates in addition to providing access to Analytics' more powerful array of query options.

    Give customers the ability to query Alma using relative dates. This functionality is currently only available in Alma Analytics, but we would like it to also be available for repository search.

    This functionality would be especially useful for creating sets, particularly logical sets that can be used to populate logical collections. One of the most common uses for collections is to showcase new materials (e.g., books, journals, databases, etc. acquired in the last 90 days). However, there is currently no way to build a logical set like this. The best one can do is to select the current year and… more

    175 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    11 comments  ·  Other  ·  Delete…  ·  Admin →
    Completed  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

    Hey all,

    Thank you for submitting and supporting this idea!

    Starting from the May 2025 release, Date-related search indexes in the Users advanced search now include new options to search within a moving range of days. This enhancement allows you to create dynamic "moving-window" sets (for example, a logical set of users who expired in the last 30 days).

    We're planning to expand this functionality to additional search indexes in upcoming releases.

    If there are specific search indexes where you'd like to see this feature implemented, please weigh in on this related idea: Search possibilities as "Received X weeks ago" or "Available X weeks ago".

17. Add a configuration option to make Alma send e-mails in plain text only

    It should be well known among responsibly acting software vendors that HTML e-mails pose a serious risk for IT security. Anyone who sends HTML e-mails (even such containing a plain text layer) tempts recipients unaware of this risk to do take potentially risky actions in their e-mail client. We as a library should be able to opt-out from tempting our users to do potentially risky things so please add a configuration option to make Alma send plain text only messages.

    51 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    Completed  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

    Hi everyone, thank you for supporting this idea.

    I'm happy to announce it has been implemented as part of the February 2026 Alma release.

    Refer to the Alma release notes for more information.

    Best,

    Alma Product

18. Add "equal" option to the title search "Authority id" index

    When searching for titles by authority ID, currently the search supports searching with: Contains keywords, contains phrase, is empty, not contains keywords, not contains phrase, is not empty.
    Add the option to also search by "equals".

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Metadata Management  ·  Delete…  ·  Admin →
    Completed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    This request has already been fulfilled; the equals operator is implemented and available in the Authority ID index.

19. Add "General Notes" at the collection, service, and portfolio levels to Analytics

    Please add the following note fields to Analytics:

    Electronic Collection:
    - General notes (multiple entries)
    Electronic Service:
    - General notes (multiple entries)
    Electronic Portfolio:
    - General notes (multiple entries)

    Why is this necessary?
    You can search for many fields in Alma itself, but not all of note fields can be exported from Alma. But this is particularly important for note fields!

    Thank you very much in advance!

    Note: this is a follow-up idea to:
    Add "General Notes" at the collection, service, and portfolio levels as indexable/searchable fields
    https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/46387843-add-general-notes-at-the-collection-service-an

    125 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    7 comments  ·  Analytics  ·  Delete…  ·  Admin →
    Completed  ·  AdminHadas Granot (Product Manager, Ex Libris) responded

    Hello,

    We are happy to inform the community that the E-Inventory subject area now includes the "General Notes" for electronic collections, services and portfolios.

    Regards,

    Hadas

20. Search possibilities as "Received X weeks ago" or "Available X weeks ago"

    Libraries sometimes wish to build logical sets from constantly changing data. For example, a logical set of items received in the last 30 days or a logical set of ebook portfolios activated in the last 15 days. The "Receiving date" (Physical items) and "Activation Date" (Electronic portfolios) search indexes only accept a specific date (selectable from a calendar) and only allow the operators "Equals", "Not Equals", "Before", "After", "Is Empty", and "Is Not Empty". It is therefore not possible to build 100% logical sets based on items received in the last 3 weeks and associate them with a collection for the Collection Discovery feature, for example with a view to promoting that content. Using Analytics is not necessarily the best way of doing things like this.

    On the other hand, Rialto offers powerful search indexes such as "Added X weeks ago", "Available X weeks ago" or "Published X years ago" and operators "Less than or equal to", "Equal to" and "Greater than or equal to". Combining the two creates relevant logical sets that are updated automatically.

    It should be possible to search the Alma Repository using an approach similar to that used in Rialto.

    Libraries sometimes wish to build logical sets from constantly changing data. For example, a logical set of items received in the last 30 days or a logical set of ebook portfolios activated in the last 15 days. The "Receiving date" (Physical items) and "Activation Date" (Electronic portfolios) search indexes only accept a specific date (selectable from a calendar) and only allow the operators "Equals", "Not Equals", "Before", "After", "Is Empty", and "Is Not Empty". It is therefore not possible to build 100% logical sets based on items received in the last 3 weeks and associate them with a collection for… more

    155 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    5 comments  ·  Resource Management - Physical  ·  Delete…  ·  Admin →
    Completed  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

    Hi all,

    thank you for supporting this idea!

    happy to inform that as of November 2025 release, It is possible to search for titles and inventory using a relative date range, such as titles created in the last month.

    read more in the Alma release notes: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2025/Alma_2025_Release_Notes?mon=All#:~:text=Relative%20Date%20Searches%20Support%20in%20Repository%20Search

    Best, Alma Product.