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.
1914 results found
-
Publishing of alternative call number from Alma to Primo
Currently item-level information is not published from Alma to Primo. As a result creating of call number search and browse indexes that include both permanent as well as alternative call number is not possible.
182 votesDear all, I would like to update that after consulting with our colleagues in Primo on this development, it was decided that this idea will be closed as we are not developing new functionality enhancements for Alma-Primo, and will not be adding this to the existing “publishing to Primo”. Future new Alma-Primo enhancements will be done for Primo VE only.
-
Enable desk operators to select from a predetermined list of loan periods.
We would like desk operators to have the option of selecting from a list of predetermined check out periods for items in certain collections.
Boston College Libraries currently provide approximately 80 laptops to community members, which can be borrowed for a fixed loan period. For many patrons this static loan period is either too short or too long, adding some loan period choices would enable us to easily meet the needs of more patrons.
Currently in Alma, offering a variety of loan periods would require the creation of additional locations and terms of use. Doing so would enable us to…180 votesAdding more than one policy to a TOU would add a lot of complexity to TOU and loan rules management. Perhaps it is simpler to change a due date manually at loan time
-
Reporting PO Line Notes
Currently, there no option to report PO Line Notes in Alma Analytics. Given the possibility to add many and various Notes to each PO Line, this seems a valuable opportunity missed.
Could other Alm users make use of this reporting option too?
Regards
Wayne
177 votes -
Calculation of due date for recalled lending requests should be consistent with fulfillment loan recalls.
When setting recall period on a fulfillment loan to "No recall due date", the original due date is kept, while renewal of the recalled loan is blocked.
For some reason, a different logic is applied to lending requests. Setting "No recall due date" as the recall period policy for lending requests, results in the due date being set to the date of the recall. The result is unpredictability for the borrower.
We propose that that these two very similar workflows are better alligned and that setting "no recall period" for recall should result in no change to the due date…
174 votesThe lender’s recall options are:
- Not to recall requested items. This can be done by removing the recall option from the relevant workflow profile.
- To recall requested items. The new due date will be set as per the recall due date policy.
In either case, a the borrower request to extend the loan of an item that has been requested by a patron on the lender side will be rejected.
The only functional implication of recalling without change in due date is the notification to the borrower that the item may no longer be renewed (which is the case anyhow). Do note that a lender’s item may be nonrenewable for any lender internal reason that the borrower may not be aware of.
The complexity of built-in configuration support for this option (i.e. not via the mentioned workaround) is probably beyond the functional benefit.
Moshe
-
make location type „unavailable“ functional: items in these locations should be shown as unavailable in Alma and Primo
We need the possibility to show items as unavailable in Primo without creating requests (work orders) for them.
Our use cases are
- items which have been restituted (via a provenance research project) and are no longer in the library
- items which are blocked for usage for years
- items which are not usable for certain reasons
All of these have to be shown in the discovery interface, although users won't get them for a long time or at all.Now, all of these items have a "green" availability status in Primo and we struggle to put information about…
174 votesNon available items must be in some process. Using work orders enables setting a description for the work order to indicate why the item is not available.
-
Be able to edit comment field of an active fine or fee posted to a patron's account
Sometimes, when posting a fine or fee to an account, the barcode gets scanned before entering info into the comments field requiring the removal of the fine and then having to re-post it into the patron's account. Would like an edit option in the ellipses to be able to go back into the fine and edit the comments field.
170 votesEnabling the altering of fine information may be sensitive, as it damages the creditability of information that is logged in fines.
-
SIP2 over https
SIP2 further development: To provide ability to develop more versatile and agile self-service concepts and processes for the staff, it would be useful to take into use ‘SIP2 over HTTPS’ in Alma. The basic message between library automation and Alma would still be in accordance with the standard 3M/NISO, but message pairs would be encapsulated in XML.
169 votesThis depends on the adoption of http by self check machine vendors. We will need to collaborate with such a vendor.
-
Include the full physical item's History - Item Changes in analytics
Analytics captures a Physical Item's Modified By and Modification Date, however this only tracks the most recent change to an item, and it does not describe the change made.
I'm hoping Analytics can be expanded to include all of the detail that can be found on the item's History - Item Changes report within Alma, including:
*Date
*Operator
*Field Name
*Old Value
*New Value145 votesWe are closing this request as this is data that can be found in Alma and is very large which would demand high effort which can be utilized for more useful developments.
-
Adjust the Analytics report generation time to include events occurring after 8 PM.
Currently, the Analytics report is generated around 8 PM Taiwan time, which is earlier than the library's closing time. As a result, events that occur after 8 PM are not included in the statistics for the following day. This prevents the library from obtaining complete statistics for the previous day. If the report generation time could be delayed by at least 2 hours, it would be very helpful for Taiwan users.
141 votesWe appreciate your feedback on how ETL timing impacts your workflows and the request to adjust the ETL processing time from 20:00 to 22:00.
Given that there are institutions in various time zones, delaying the ETL time by two hours would have a broader impact across other libraries.
We carefully evaluated the potential effects and risks of this change and decided to continue with the current schedule of the ETL process.
We are closing this idea so that you will be able to use your votes for other enhancements you would like to promote.
-
Local Authorities for Network Zone linked records
Alma provides the possibility of local authorities for cataloguing in an Institutional Zone and its local records. Unfortunately I cannot use those local authorities if I work in a Network Zone environment for records linked to the Network Zone.
I would like to:
a. define the local authority in the Institution Zone.
b. Link to this local authority in a local field 6XX (= with $$9LOCAL) via F3 in MDE even if the bibliographic record is linked to the Network Zone.139 votesDear community,
We analyzed this suggestion and the possible ways to implement it.
Due to technical limitations and risks we will not be able to implement this request in the near future.
-
Ability to report all MARC tags and subfields in bibliographic, holdings and authority records
I can no longer vote for the originally posted idea with this title, as it has been marked as "Already supported"
I would, however, argue that creating sets in Alma and MARC export capability is NOT the same as reporting capability. Please reconsider this suggestion.
We need this functionality in ANALYTICS in order incorporate the data (i.e. to append notes from the holding record to a shelf list report, or to limit results by something in the fixed fields) efficiently into our reports.
138 votes -
Change Repository Search "Contains" to drop-down to enable searching "Contains Phrase", "Starts With", and "Equals"
In the repository search simple search, the only search operator you can use when searching available indexes is contains (e.g., FIND all titles WHERE title CONTAINS ____.
We would like to request that the CONTAINS operator be turned into an advanced-style dropdown menu to enable searches like this:
FIND all titles WHERE title CONTAINS PHRASE ____
FIND all titles WHERE title STARTS WITH ____
FIND all titles WHERE title EQUALS _____In many cases, an advanced search is not required, it is simply the contains operator that needs to be modified, and performing an advanced search just to modify the…
136 votesThis idea was discussed with the Alam UX focused working group and it was agree it is lower priority. We will consider this request in future changes we might do in the search.
-
Allow sorting of itemized set members similarly to logical set results.
In Manage Sets, enable sorting the members of itemized record sets by title, creator, and publication date, similar to the criteria available for sorting results of logical sets. Currently our only option for sorting the members of an itemized set is by exporting to Excel and manipulating the resulting spreadsheet, which doesn't allow for clean sorting by the same criteria.
135 votesDear Community,
Thank you for your suggestion to allow sorting of itemized set members.
Unfortunately, after a thorough analysis, we have concluded that supporting full-set sorting for itemized sets is not technically feasible within the current architecture.
However, we recognize the importance of enhanced usability in managing sets, and as part of ongoing UX improvements, we will gradually introduce page-level sorting capabilities for itemized sets, across different set types.
We appreciate your engagement and continued contributions to the Idea Exchange.
Thanks,
Uri Beladev
Product Manager, Library Platform
-
Provide email address information in search results of patron search
When searching for patrons through Fulfilment>Manage Patron Services, it would be useful if the search results included the patron's email address so that library staff had a unique identifier to check against when there a multiple patrons with the same name.
132 votesDisplaying email address in a pick listmay be considered a privacy issue. It is better protected inside a patron edit form, or as a configurable element in the pop up card. It is not possible to control pick list columns by institution.
-
Incorporation of All Indigenous Syllabics from the Canadian Aboriginal Syllabics Unicode Block
I have a case open with Ex Libris (# 00517082) regarding this. Not all Indigenous syllabics render in Alma, and thus, do not render in Primo either. As an important aspect of Canadian Libraries' commitments to Truth and Reconciliation, and as it is UN's International Year of Indigenous Languages, it would be excellent if Ex Libris could prioritize resolving this issue so that we can allow Indigenous users full discoverability of resources in their own languages.
131 votesNo response received. Idea Exchange is closed.
-
Improve Alma Link Resolver’s performance with Pubmed IDs (PMIDs)
Improve Alma Link Resolver’s performance with Pubmed IDs (PMIDs) such that it is as good or better than Serials Solutions’ 360 Link performance with Pubmed IDs. Areas where this is currently a problem include translation of OpenURL data from Pubmed over to Illiad through Alma Linker and Primo, item level linking between Pubmed, Alma Linker and Cochrane Library, and probably many other areas.
130 votesHi all,
This idea was opened back in 2017, several rounds of improvements to the link resolver were done since.
In 2024 we asked for more specific examples to better understand the root cause and the options for improvement. Since we received no additional information since, we are closing this idea.
If you feel like this is still an issue, please provide as with detailed examples so we can analyze it.
-
Add "Print Slip Report" action to the "Resource Request Monitoring" screen
The Print Slip Report function is currently available from the "Pick Up Requested Resources" and "Resource Sharing Lending Requests Task List" screens. But when a hold is placed on an item that is checked out, the returning item is automatically placed on hold and the request bypasses the "Pick Up Requested Resources" screen and shows up on the "Resource Request Monitoring" screen as "On Hold Shelf". But the Print Slip Report is not available here. It does need to be available here, as well.
"Print Slip Report" is a different action than "Print Slip." The Print Slip Report is a…
121 votesHi,
The request monitor page is not intended to be the routine working space, but rather be an interface that allows searching and fining specific requests to query about their status, and run some specific actions (such as cancel). The routine work on the requests list is intended to be done via the task lists.
Thanks,
Moshe -
Recommendations for Improving User Search and Batch Update Functionality
Currently, primary identifier and identifier searches only support the "equals" operator. It is recommended to enhance flexibility by adding options such as "contains" or advanced search functionalities, including the ability to search without a primary identifier, to better support user management.
Batch processes cannot batch update user notes or perform text replacements. It is recommended that a batch update feature be provided for these functions.
120 votesIdentifiers are managed in the database under strict security, to protect personal identifying information. Therefore, this information cannot be searched with partial information.
-
Analytics report for titles daily
I would like to have the possibility of knowing the updated amount of titles daily. Alma currently updates that information only every 28 days. This does not allow having statistics updated until the previous day.
120 votesDear Colleagues,
Thank you for this idea. We appreciate your interest in staying informed.
After careful consideration, we regret to inform you that we are unable to provide more frequent updates at this time. Our priority is to maintain system stability and ensure uninterrupted functionality for all users. Frequent updates could potentially strain our infrastructure and impact overall performance.
We apologize for any inconvenience this may cause.
Thank you for your understanding.
Sincerely,
Shoshana de la Fuente
Senior Product Owner
LS Analytics
-
Browsing Dewey in MD Editor
We noticed that in Metadata editor the browsing in the 676 - Dewey field isn't available: we would like add the feature to scroll the lists from other records, as happens for the 6xx fields (subjects) and 7xx (authors).
114 votesThe F3 functionality is designed specifically for linking bibliographic headings to an authority record. When used, it opens the defined authority vocabulary in browsing mode, which allows customers to view the full authority record or link it to the bibliographic record where corrections are done (For more details on authority controlled fields in UNIMARC, please refer to the relevant documentation). This functionality is not intended for browsing bibliographic data in other records based on a search term. Browsing bibliographic data is supported through the Browse Bibliographic Headings feature.
For this reason, F3 is available for the UNIMARC 676 field only when it is used in the context of linking. In this situation, Alma checks the vocabulary code in subfield $2 and displays the corresponding authority data for selection.
If your goal is to browse the bibliographic data stored in the 676 fields of your repository, you will need to…
.jpg){kind=link}
- Don't see your idea?