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 ~
1749 results found
-
Vendor type - APC
We currently have 4 Vendor types in Alma (Material supplier, access provider, Licensor and Governmental) it would be useful to have a new type of APC vendor - we often pay different companies, who we don't use for other purchases, and the existing types don't match. It would also be useful where we have transformative deals so we can highlight that the vendor is also identified as an APC provider (whether we pay or not for them)
1 vote -
Arcanum
Arcanum Newspapers
URL: https://adt.arcanum.com/en/collections/
Provider: Arcanum4 votes -
Notifications in the Alma Mobile App
We'd like the Alma Mobile app to be able to generate a notification when a new request is placed.
1 vote -
How to List a token or coin on LBank Crypto Exchange
To list a token or coin on LBank Crypto Exchange, submit an application on their official website, including detailed information about your project, team, and tokenomics. Ensure compliance with their requirements and pass the evaluation process. For comprehensive guidance and support, consider visiting an MLM software company for additional resources and expertise.
For more information, visit: www.mlmsoftwarecompany.in1 vote -
Provide a way to duplicate a terms of use
This is especially a pain point when you are starting in Alma. When libraries are tweaking circulation rules, often you need to create a new terms of use as part of that, but what you really are doing is taking an existing terms of use and setting a new one up in the same except for one or two policies that are different. Right now, you have to have the TOUs in different tabs to make sure all the right values are matching, when having the ability to copy and then edit an existing TOU would save a bunch of time. (This is also functionality in many other places in Alma, so not having it in the TOU feels like it was skipped accidentally.)
This is especially a pain point when you are starting in Alma. When libraries are tweaking circulation rules, often you need to create a new terms of use as part of that, but what you really are doing is taking an existing terms of use and setting a new one up in the same except for one or two policies that are different. Right now, you have to have the TOUs in different tabs to make sure all the right values are matching, when having the ability to copy and then edit an existing TOU would save a bunch of…
16 votes -
Add "Prefer Open Access resources" option on the Online Services Order page
Configuring the Online Services Order (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/080Configuring_Fulfillment/090Discovery_Interface_Display_Logic/035ViewIt#Configuring_the_Order_of_Online_Services) includes several options, including an "Additional Preferences" section where one can choose whether or not to prioritize CZ collections, source service, ID based linking services, or prefer resources with a PO Line. However, there is no option for prioritizing OA resources. In order to allow libraries to make Open Access resources more readily available to end users, in this idea, I request that a preference be added to this list, "Prefer Open Access resources." Like the other "Additional Preferences" option, there would be a radio button to select "Yes" or "No." I have attached a mockup image showing how this option would be added to the Additional Preferences section.
There is an existing preference hierarchy if multiple preferences are selected:
1.Services of collections/portfolios that have a linked PO Line (i.e., subscribed services or owned).
2.ID-based linked services.
3.Source services
4.Community Zone collections.
5.Top services.
6.Bottom services.In this hierarchy, I suggest "Open Access resources" should appear as #1, above "Services of collections/portfolios that have a linked PO Line." This is because libraries that select "Yes" for "Prefer Open Access resources" want to promote Open Access and boost the Open Access portfolio over other portfolios. Libraries that want to prioritize access to paid resources over OA will select "No" for "Prefer Open Access resources" and will select "Yes" for "Prefer resources with PO Line," so their portfolios with attached PO lines will continue to be at the top of their lists.
Configuring the Online Services Order (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/080Configuring_Fulfillment/090Discovery_Interface_Display_Logic/035ViewIt#Configuring_the_Order_of_Online_Services) includes several options, including an "Additional Preferences" section where one can choose whether or not to prioritize CZ collections, source service, ID based linking services, or prefer resources with a PO Line. However, there is no option for prioritizing OA resources. In order to allow libraries to make Open Access resources more readily available to end users, in this idea, I request that a preference be added to this list, "Prefer Open Access resources." Like the other "Additional Preferences" option, there would be a radio button to select "Yes" or "No." I…
9 votes -
Enhancing Alma with ERP System Integration for Streamlined Operations
Alma is a robust library management system, but its potential could be further maximized by integrating ERP (Enterprise Resource Planning) system functionalities. By incorporating ERP features, Alma could streamline financial management, procurement, and resource allocation across library operations. This integration would not only improve efficiency but also provide a unified platform for managing budgets, tracking expenditures, and optimizing resource allocation. Additionally, an ERP system could enhance reporting capabilities, offering deeper insights into library data that could inform strategic decision-making. This approach would position Alma as a more comprehensive tool, catering to the evolving needs of modern libraries.
ERP recommendation: https://www.impactfirst.co/id/erp/software-erp
1 vote -
Implement Automatic Upload of Electronic Holdings for Perlego eBooks
Implement auto holdings (autoholding, automatic upload of e-holdings) for Perlego eBooks.
This will allow for automatic update of the collection based on most recent institutional holdings file received from Perlego.
As is already available for ProQuest, Springer, Elsevier, Wiley, and other publishers.
22 votes -
Display Open Access Indicator based on Setting at the Portfolio Level
Currently, the Open Access (OA) indicator displays in Community Zone records when the record contains a 506 field with the following formatting:
506 0_ $f Unrestricted online access $2 star
Records in the Directory of Open Access Journals (DOAJ) collection are automatically enriched with this data, but not records in any other collection. The rationale is that the OA indicator may appear on records that are not available as OA in all collections, leading to a confusing display. However, this can lead to cases where institutions do have OA access, but cannot display the OA indicator.
To avoid both of these situations, this idea proposes that Ex Libris establish a way to allow for the display of the OA indicator based on a new setting at the portfolio level. This setting should be able to be set both individually and at the service level, to assist with collections that are entirely OA. In practice, collections that are fully OA would, by default, have the OA setting turned on, but customers should be able to manually override erroneous values.
Preferably, this setting for displaying the OA icon would replace the current practice based on the bibliographic 506 field.
Note that this proposal only focuses on records with associated portfolios. It does not address the display of the OA icon in CDI records.
Currently, the Open Access (OA) indicator displays in Community Zone records when the record contains a 506 field with the following formatting:
506 0_ $f Unrestricted online access $2 star
Records in the Directory of Open Access Journals (DOAJ) collection are automatically enriched with this data, but not records in any other collection. The rationale is that the OA indicator may appear on records that are not available as OA in all collections, leading to a confusing display. However, this can lead to cases where institutions do have OA access, but cannot display the OA indicator.
To avoid both of…
193 votes -
Add Campus Name as a Field in the Course Reserves Subject Area
Currently, the only location option in the Course Reserves subject area is "Campuses Name and Participants." This field is made up of "The campus description and the number participants per campus." "Campuses Name and Participants" is misleading in that it pulls the campus description field, rather than the campus name field.
We would prefer a field that contains only the campus name, without using the description or the number of participants.
3 votes -
Add column options to 'Receive New Material' / receiving dashboard
Add more column options to the 'Receive New Material' page / receiving dashboard: expected receipt date and vendor name. Others have previously suggested brief level and item policy.
5 votes -
License Terms
Allow for users room to add institution specific license terms details as the ones provided are not always a good fit for the individual institutions needs.
6 votes -
SUSHI Havesting for Cabell's International
Cabell's International just updated SUSHI Harvesting for COUNTER 5.0 and 5.1. Please add as an authorized vendor for sushi harvesting in alma
1 vote -
Consistent use of first ISBN in MARC field 020 for electronic resources in Alma
Right now which ISBN is displayed/taken for export relating to e-resources is rather inconsistent in Alma:
.) In the results list of an All Titles search the first ISBN of MARC field 020 is displayed and subsequently used for Excel export.
.) In the results list of an Electronic Portfolio search the second ISBN of MARC field 020 is displayed (if there is one) and subsequently used for Excel export.
.) In the portfolio list of an electronic collection the second ISBN of MARC field 020 is displayed (if there is one).
.) On the portfolio tab of the Electronic Service Editor the print ISBN of MARC field 776 08 is displayed.
.) When creating an extended export of an electronic collection the ISBNs are primarily taken from 776 08 MARC field and secondarily from MARC field 020. Three ISBNs are exported at most. Depending on how many ISBNs the record contains it could be 3 print ISBNs of MARC field 776 08, 2 print ISBNs of MARC field 776 08 and the last ISBN of MARC field 020, 1 print ISBN of MARC field 776 08 and the 2 last ISBNs of MARC field 020, 3 ISBNs of MARC field 020 ...Referring to the knowledge article on display priority (https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/ISBN_(ISSN)_Display_Priority) we would like to note that priority of print ISBN over eISBN seems wrong. Instead we suggest to consistently take the first ISBN of MARC field 020 for display and export of e-resources.
Right now which ISBN is displayed/taken for export relating to e-resources is rather inconsistent in Alma:
.) In the results list of an All Titles search the first ISBN of MARC field 020 is displayed and subsequently used for Excel export.
.) In the results list of an Electronic Portfolio search the second ISBN of MARC field 020 is displayed (if there is one) and subsequently used for Excel export.
.) In the portfolio list of an electronic collection the second ISBN of MARC field 020 is displayed (if there is one).
.) On the portfolio tab of the Electronic…154 votes -
Optimizing Library Operations Through Alma API Integration
Hello everyone,
I am seeking expert guidance on effectively harnessing Alma’s API capabilities to elevate our library’s operational efficiency. As we strive to streamline processes and strengthen system integration, including mulesoft API integration. I am eager to learn from the collective wisdom of this community.
I am particularly interested in insights on:
Best Practices: Proven methods for seamlessly integrating Alma APIs with external systems to ensure optimal data flow and mitigate potential challenges.
Overcoming Obstacles: Common hurdles encountered during Alma API integration and successful strategies for resolution.
Performance Enhancement: Techniques and tools for optimizing Alma API performance, especially when handling large datasets.
Advanced API Utilization: Uncovering hidden gems within Alma’s API suite to unlock additional value for our library.Sharing your experiences and recommendations would be invaluable.
Thank you for your time and expertise.
Hello everyone,
I am seeking expert guidance on effectively harnessing Alma’s API capabilities to elevate our library’s operational efficiency. As we strive to streamline processes and strengthen system integration, including mulesoft API integration. I am eager to learn from the collective wisdom of this community.
I am particularly interested in insights on:
Best Practices: Proven methods for seamlessly integrating Alma APIs with external systems to ensure optimal data flow and mitigate potential challenges.
Overcoming Obstacles: Common hurdles encountered during Alma API integration and successful strategies for resolution.
Performance Enhancement: Techniques and tools for optimizing Alma API performance, especially when…3 votes -
Alma Purchase Request Facets - filter by fiscal year
It would be helpful to have facets in the Alma Purchasing requests to be able to filter out orders by fiscal year. The fund codes connected to the orders have fiscal years attached to them. It would be helpful to only be able to see the orders that are within the current fiscal year and not every order ever entered.
3 votes -
Add Electronic Service Information Update Job
Electronic Portfolios and Electronic Collections each have an Information Update job in Alma. Electronic services need the same functionality because they are also affected in bulk by changes.
Job Name: Change Electronic service information
Job Description: Update Electronic service information for a set of Electronic services
Job Content Type: Electronic Service
Job Type: Information UpdateUse Case: ProQuest began requiring a value for the CLIENTID parameter in the Linking Parser Parameters section of all ProQuest electronic services. With over 50 ProQuest electronic collections activated, that meant that over 50 electronic services had to be manually edited one at a time to add the same CLIENTID value in the Linking Parser Parameters section of the Linking tab.
Desired Workflow: Create a set of all affected electronic services. Run the Change Electronic service information job to edit the linking parser parameter in bulk by specifying both the parameter name (CLIENTID) and value (e.g., 12345). The job systematically updates the value of the CLIENTID parameter for each electronic service in the set.
Electronic Portfolios and Electronic Collections each have an Information Update job in Alma. Electronic services need the same functionality because they are also affected in bulk by changes.
Job Name: Change Electronic service information
Job Description: Update Electronic service information for a set of Electronic services
Job Content Type: Electronic Service
Job Type: Information UpdateUse Case: ProQuest began requiring a value for the CLIENTID parameter in the Linking Parser Parameters section of all ProQuest electronic services. With over 50 ProQuest electronic collections activated, that meant that over 50 electronic services had to be manually edited one at a time…
45 votes -
Resource Sharing Loan Due Date
It would be ideal if a Loan Due Date could be a standardized length. Currently Loan Due Date= Due Date minus transit time and holdshelf. Often this results in an inconsistent length of time. This is most evident when loan periods are short. For example, if an item has a 14 day loan policy according to the Loan TOU, and the Lending Resource Sharing TOU Due Date is set at 21 days, the loan period could be 17 days.
We would prefer that Loan Due Dates follow the pattern:
If Loan TOU is shorter than {Due Date - Transit and Holdshelf time}, loan length should= Loan TOU. Otherwise, follow existing rule for Loan Due Date.It would be ideal if a Loan Due Date could be a standardized length. Currently Loan Due Date= Due Date minus transit time and holdshelf. Often this results in an inconsistent length of time. This is most evident when loan periods are short. For example, if an item has a 14 day loan policy according to the Loan TOU, and the Lending Resource Sharing TOU Due Date is set at 21 days, the loan period could be 17 days.
We would prefer that Loan Due Dates follow the pattern:
If Loan TOU is shorter than {Due Date - Transit and…18 votes -
Corollary suggestion to "Copy POL data to new POL with different order line type"
I would like to see Rollover of POLs receive a new rollover rules-build.
It would be extremely helpful if POL rollover could be done ledger-by-ledger if desired.
In addition, I (and maybe others? vote for this!) would like an option for firm orders to roll ONLY if they're still 'open', i.e. not 'closed', and not 'invoiced' (is rollover of firm orders ordered, received, AND PAID in one fiscal year into the next EVER useful? I doubt it myself...). Voyager did something like this with firm order rollover. I can't remember whether its rules just made sense, or if I adjusted my practice to fit Voyager's rules, but I know that when I rolled firm orders, those that had been ordered, received, and paid in one fiscal period did NOT roll into the next fiscal year--as they should not, ever, for any institution.
Unless I lack imagination here and am really missing a plausible scenario? If so, please comment!
I would like to see Rollover of POLs receive a new rollover rules-build.
It would be extremely helpful if POL rollover could be done ledger-by-ledger if desired.
In addition, I (and maybe others? vote for this!) would like an option for firm orders to roll ONLY if they're still 'open', i.e. not 'closed', and not 'invoiced' (is rollover of firm orders ordered, received, AND PAID in one fiscal year into the next EVER useful? I doubt it myself...). Voyager did something like this with firm order rollover. I can't remember whether its rules just made sense, or if I adjusted…
1 vote -
Sort Option for Data Start Date or Data End Date in SUSHI Area/Vendor Details
It would be helpful to add a sort option for the 'Data Start Date and Data End Date" when analysing SUSHI reports that have been uploaded to the vendor details area/profile. When doing a custom harvest or uploading data it would make it so easy to see what date ranges have been uploaded and/or harvested. There is already sort functionality for the file name, uploaded date, SUSHI account and others, please see screen shot. I honestly think this is too important not to have been considered.
1 vote
- Don't see your idea?