Alma
Your feedback matters to us. Help us improve Alma by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines. Thank you.
- or
No existing idea results
- ~ No ideas found ~
1903 results found
-
Add "Vendor invoice number" to PO Line dimension in Analytics
Please add the "Vendor invoice number" from the Vendor Information section of the PO Line screen to analytics. It should be specifically added to the PO Line dimension.
This field is necessary for quickly reporting on POLs that have this information stored at the POL level, but are not attached to an invoice. Workarounds include manually looking up the PO, then searching Analytics, but we shouldn't require staff to search Alma if they could directly query Analytics with an invoice number from a PDF or an email.
13 votes -
Add/modify fields from Vendor Record for Analytics (including Account, Contact Information/Preferred Address)
Add/modify fields from Vendor Record for Analytics (including Account, Contact Information/Preferred Address)
1) Add Vendor Type: Example: I want to analyze the vendor file based on vendors that are only Access Providers/Licensors and not Material Suppliers, or just Material Suppliers.
2) Add Vendor Accounts as output, including options to output Payment Methods. Example: we recently had a campus financial system migration, and I want to isolate those vendors who pass through the ERP export vs. Credit Card vendors. Similar to Bank Transfers - if my campus has a change in policy that needs communication, I want to be able to pull these vendors together.
3) From Contact Information, Preferred Address - be able to break out State and Country fields separately from the Address Details. Example: I want to run a report of my US-based vendors and my non-US-based vendors. Output as currently programmed is only Preferred Address as a whole string where I would have to break that out.
Include Address Type as option (Billing, Claim, Order, Payment, Returns, Shipping)
Add/modify fields from Vendor Record for Analytics (including Account, Contact Information/Preferred Address)
1) Add Vendor Type: Example: I want to analyze the vendor file based on vendors that are only Access Providers/Licensors and not Material Suppliers, or just Material Suppliers.
2) Add Vendor Accounts as output, including options to output Payment Methods. Example: we recently had a campus financial system migration, and I want to isolate those vendors who pass through the ERP export vs. Credit Card vendors. Similar to Bank Transfers - if my campus has a change in policy that needs communication, I want to be able to…
25 votes -
The option to change the permanent location in the item should not be a default, it should be selectable.
To change the permanent location in the item can lead to incorrect results. If you have two holdings with different locations and then change the location of the item which is connected to the first holding to the location of the second holding, your item will be relinked to the second holding AND the first holding will be deleted automatically. If the first holding contained additional information (e.g. the call number), this information will be lost.
The option to change the permanent location in the item should therefore not be a default, it should be selectable depending on the needs of the institution. Some may find it useful, others not.To change the permanent location in the item can lead to incorrect results. If you have two holdings with different locations and then change the location of the item which is connected to the first holding to the location of the second holding, your item will be relinked to the second holding AND the first holding will be deleted automatically. If the first holding contained additional information (e.g. the call number), this information will be lost.
The option to change the permanent location in the item should therefore not be a default, it should be selectable depending on the needs…13 votes -
Publishing to OCLC: Enrich LHRs Using OCN Instead of MMS ID for Unchanged/Deleted Holdings
OCLC processes incoming Local Holding Records (LHRs) by applying a 'replace all' mechanism. If WorldCat has three holding records for an OCN and the library sends just one holding record, WorldCat will replace the three existing holdings with the single incoming holding. This is documented here: https://help-nl.oclc.org/Metadata_Services/WorldShare_Collection_Manager/Data_sync_collections/Create_an_ongoing_data_sync_collection/Local_holdings_records_collection/30MARC_21_Format_for_Holdings_Data_and_OCLC_local_holdings_records
Currently, Alma's LHR publishing job for OCLC takes this into account by enriching the publishing of modified holdings with unmodified/deleted holdings that belong to the same bibliographic record. According to the Alma documentation: "Note also that when a holdings record is updated, it is republished together with all the holdings records linked to the bibliographic record, including the deleted holdings." This is documented here: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/090Integrations_with_External_Systems/030Resource_Management/110Publishing_to_OCLC#When_are_Records_Exported.3F
However, this enrichment does not sufficiently meet our institution’s needs, as we have valid cases of multiple bibliographic records sharing the same OCN.* For example, when a holding record from bibliographic record A, which shares the OCN with bibliographic record B, will be published to WorldCat, WorldCat will delete all holdings related to bibliographic record B. This occurs because the current enrichment mechanism is based on the MMS ID. While all unmodified/deleted holdings for bibliographic record A are included in the LHR publishing, those of bibliographic record B are excluded.
In order to prevent the undesired deletion of holdings records in WorldCat, Alma's enrichment mechanism of modified holdings records with unmodified/deleted holdings records would have to be based on the OCN rather than the MMS ID.
We raised a ticket with Ex Libris about this issue (#07691519), and product management advised us to submit this enhancement request to NERS or the Idea Exchange.
We would greatly appreciate it if Ex Libris could add an option to base the enrichment of unmodified/deleted holding records on the OCN rather than the MMS ID.
(*) The reason behind this issue is that our cataloging practices differ from those of WorldCat. For example, we maintain separate bibliographic records for hardcovers and paperbacks, while OCLC/WorldCat merges them. More information is available here: https://www.oclc.org/bibformats/en/about/input.html
OCLC processes incoming Local Holding Records (LHRs) by applying a 'replace all' mechanism. If WorldCat has three holding records for an OCN and the library sends just one holding record, WorldCat will replace the three existing holdings with the single incoming holding. This is documented here: https://help-nl.oclc.org/Metadata_Services/WorldShare_Collection_Manager/Data_sync_collections/Create_an_ongoing_data_sync_collection/Local_holdings_records_collection/30MARC_21_Format_for_Holdings_Data_and_OCLC_local_holdings_records
Currently, Alma's LHR publishing job for OCLC takes this into account by enriching the publishing of modified holdings with unmodified/deleted holdings that belong to the same bibliographic record. According to the Alma documentation: "Note also that when a holdings record is updated, it is republished together with all the holdings records linked to…
8 votes -
Ability to set bib record to "Force Export to WorldCat" via the "Set Management Tag" Job
Currently the "Set Management Tag" cannot set a bib record to "Force Export to WorldCat" as you can do in the Metadata Editor. Adding this option to that job would be very helpful as currently the only way to set this option is to go to each and every record via the Metadata Editor.
1 vote -
Add purchase model to more auto-holdings.
It is great to have purchase model added automatically for Ebook Central og JSTOR Books holdings, and it would be even better if we could get purchase model also when using auto-holdings for publishers such as Elsevier, Springer, Wiley, Taylor & Francis and de Gruyter. We have evidence based acquisition agreements with all of these publishers and it would be very helpful if we could see which titles were in the EBA corpus and which we have purchased, either through the EBA or by earlier collection purchases.
88 votes -
Benefits of Protein Powder!
Discover the science behind Sunwarrior Protein Powder, designed to fuel your body with plant-based, clean nutrition. Packed with essential amino acids, this protein powder supports muscle growth, recovery, and overall health. It's an ideal choice for those seeking a natural, easy-to-digest supplement to boost their fitness journey and enhance energy levels. Read here: https://yourhealthmagazine.net/article/weight-control-nutrition-exercise/science-behind-sunwarrior-protein-powder-that-fuels-your-body/
1 vote -
Collagen for Hair, Skin and Nails
Collagen is the key to maintaining youthful skin, strong hair, and healthy joints. As the most abundant protein in our bodies, it plays a crucial role in keeping skin firm and elastic while promoting overall wellness. By incorporating collagen supplements into your daily routine, you can support your skin’s natural structure, reduce signs of aging, and boost joint health. Discover the science behind collagen and see how it can enhance your beauty and health from the inside out. Read more: https://yourhealthmagazine.net/article/beauty-skin-care-gorgeous-smiles/the-science-behind-collagen-why-you-should-include-it-in-your-routine/
1 vote -
MDE expand from template CZ records
Alma currently doesn't have the ability to "expand from template" for Community records. The option will enable MDE users to use a template to apply multiple local extension fields to CZ records, minimizing the unintentional error of changing the CZ records for everyone.
7 votes -
Please add the ability to run jobs on a representation level in digital records
Hello
Currently, the jobs for digital records run only on "Title" level.
If we run a job on a record that has more than one representation, the job will run on all the representations, even if we want it to run only on a specific one.In electronic records and physical records we have jobs that run on a portfolio level and item level.
The same should be applied on digital records.
The job should include changing information (for example public note) and deletion if needed.
This should also help the following idea:
https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/42199792-enable-withdrawing-digital-representations-job-basThanks,
Dafna77 votes -
Add barcode to Managed Deleted Repository report
It would be very helpful if the Managed Deleted Repository Report could include the barcode of the item that was withdrawn. We were recently working on an inventory project, compiling a spreadsheet with barcodes. Some items were withdrawn, but we had them in our barcode spreadsheet and needed to delete them. We thought that the Managed Deleted Repository Report would help us identify them, but the barcode wasn't in the report.
6 votes -
Alma APIs Multilingual Code-tables
We’d like to request an enhancement to the Alma API that would allow PUT and POST requests to include translation updates. Currently, only GET requests support the lang parameter for retrieving localized data, while updates ignore these descriptions. Enabling translation updates via API would streamline content management across languages, making it easier to keep localized information current and consistent.
Updating code tables for around 80 patron-facing letters in three different languages via the web UI is extremely time-consuming and inefficient. Allowing translation updates through the API would greatly improve this process, making Alma more effective for multilingual institutions.
We’d also like to highlight an inconsistency: the addressFrom field, which represents an email address, is language-dependent in the current setup. Since email addresses are universal and not language-specific, it would make more sense for this field to remain constant across all languages.
Allowing language-neutral fields like addressFrom to remain consistent would simplify multilingual management and avoid unnecessary duplication across language settings.
We’d like to request an enhancement to the Alma API that would allow PUT and POST requests to include translation updates. Currently, only GET requests support the lang parameter for retrieving localized data, while updates ignore these descriptions. Enabling translation updates via API would streamline content management across languages, making it easier to keep localized information current and consistent.
Updating code tables for around 80 patron-facing letters in three different languages via the web UI is extremely time-consuming and inefficient. Allowing translation updates through the API would greatly improve this process, making Alma more effective for multilingual institutions.
We’d also…
15 votes -
Please add 3xx field support in Bibliographic Details dimension of Alma Analytics
Currently there are many fields in the 3xx range which are not supported OTB in the Bibliographic Details dimension of Alma Analytics.
We have mapped 300 to a Local Param several years ago, but we are stymied in our work updating to RDA consistently as the desired foundation for then considering LOD work in BIBFRAME, given this is a key area with many 3xx fields utilised such as 334, 335, 336, 337, 338, 340, 344, 345, 346, 347, 380 and 382.
Although the number of Local Params increased in 2024 finally from 10 to 30 we use many of these for other important field data, and it’s not reasonable to take up more than a dozen of these just with 3xx fields.
These fields do not generally have many characters, so it is not anticipated that this would add much to the performance load for the ETL to hardcode add to the Bibliographic Details dimension for all customers.
This idea would be fulfilled by each of these mentioned 3xx fields being added to Alma Analytics as a standalone field ie not all in one field, to support bibliographic data management, maintenance, updating projects, and reporting.Currently there are many fields in the 3xx range which are not supported OTB in the Bibliographic Details dimension of Alma Analytics.
We have mapped 300 to a Local Param several years ago, but we are stymied in our work updating to RDA consistently as the desired foundation for then considering LOD work in BIBFRAME, given this is a key area with many 3xx fields utilised such as 334, 335, 336, 337, 338, 340, 344, 345, 346, 347, 380 and 382.
Although the number of Local Params increased in 2024 finally from 10 to 30 we use many of these…4 votes -
Be able to control access rights by user login combined with patron role with a specific scope at library level.
Be able to control access rights by user login combined with patron role with a specific scope at library level.
Example:
Be able to specify a parameter in the access rules that grant access to the representation on Library A if the patron is logged in and his patron role scope = Library A, meaning, only user logged in and belonging to that library are able to access that document.1 vote -
Alma - Analytics - Users - Add field 'Has password' true/false
Sometimes users may have no password set. For example, in our system we have some internally managed users left with no password when Alma switched to external IDP. Filtering them in Analytics would be useful, but currently there is no way to do so.
Please add Add field 'Has password' true/false in Alma Analytics Users dimension.
15 votes -
Option for support from within EU for EU customers
There should be an option for Alma customers within the EU to allow access opportunities for Ex Libris staff in the EU only. The purpose is to increase the compliance with GDPR by
limiting access to data by US intelligence authorities as far as possible.19 votes -
Add information regarding level URL clickthroughs to Analytics
Currently only clickthrough for portfolios are being captured in Analytics. It would be great if level URL clickthrough's in Electronic Collection could also be captured.
3 votes -
Add a ToU configuration option to block renewals only once a loan becomes overdue.
We would like to be able to prevent users from renewing certain loans in Primo once they become overdue. This is often what we want for equipment, for example.
This should not be a user-level block, but rather an item-level block. Any other items the user wishes to renew should be renewable in Primo, but we want users to have to return overdue items first.
As an illustrative example, we have items that check out for 3 hours. We want these items to be returned before the library closes each day, but we want to allow online renewals throughout the day. With the current policies, if a user does not return the item by the end of the day, they are able to renew it the next day instead of returning it.
We would like to be able to prevent users from renewing certain loans in Primo once they become overdue. This is often what we want for equipment, for example.
This should not be a user-level block, but rather an item-level block. Any other items the user wishes to renew should be renewable in Primo, but we want users to have to return overdue items first.
As an illustrative example, we have items that check out for 3 hours. We want these items to be returned before the library closes each day, but we want to allow online renewals throughout the…
4 votes -
Include more than 30 or an unlimited number of local parameters in Alma Analytics
We find Analytics to be very powerful, but we are hampered by its limitation to only selected MARC and a limit of 30 local parameters.
We hope ExLibris will include more or an unlimited number of local parameters in the future.
When we signed up for Alma, our team expected all MARC bib codes would be available in Analytics and they are not. In addition, we have defined several local fields and must assign them a local parameter to be able to output them in Analytics. We have been rationing the 30-alloted local parameters ever since.
17 votes -
Add a new vocabulary in the CZ
We have in NZ of CCUC (Catalan Union Catalog) a vocabulary in Catalan that is a controlled language used for indexing the genre or form and it can be used in bibliographic records together with any other subject heading system. Its use is of interest to any library that uses Catalan as the language of the catalog (for example, libraries in Andorra, the Valencian Community, the Balearic Islands, etc.). Some of these libraries use ALMA and have requested that this vocabulary be accessible in the CZ in order to use it.
Therefore, we request the indexing of the TGFC vocabulary under the developed name: BNC - Genre/Form Terms in Catalan.We have in NZ of CCUC (Catalan Union Catalog) a vocabulary in Catalan that is a controlled language used for indexing the genre or form and it can be used in bibliographic records together with any other subject heading system. Its use is of interest to any library that uses Catalan as the language of the catalog (for example, libraries in Andorra, the Valencian Community, the Balearic Islands, etc.). Some of these libraries use ALMA and have requested that this vocabulary be accessible in the CZ in order to use it.
Therefore, we request the indexing of the TGFC vocabulary…48 votes
- Don't see your idea?