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.
1697 results found
-
New type of block : booking
Currently the Block Preferences in Alma have Block options to permit Blocks on :
· Block types 01 et 02= Loan and renewals
· Block type 03= Loan and renewals and request
· Block type 04 = Resource sharing
· Block type 05 = Request
It would be good to include a type of block for Booking only. It would allow us to block Booking without blocking other services for a patron.
Right now libraries can’t choose to sanction a booking abuse without blocking every other service. It is too strong a sanction for some users.
Best regards,
Nathalie Darbon
76 votes -
Lost Loan Status
Closing a lost loan changes the item's status to missing. This means that items we know are lost will turn up on lists for missing item searches, even though we know we won't find them. Not closing the loans means that we can't purge patrons from the database, even if we know that we are not going to get back the item or be paid the replacement fee.
It would be preferable if items retained a status of Lost even if the loan is closed, so that we can differentiate between items that are lost and items that just can't…
18 votes -
Add the NOT Boolean operator to the Advanced Search in Alma
Advanced Search in Alma contains currently only AND and OR Boolean operators - it would be very useful to have the NOT operator included, so that we can exclude particular records from Logical Sets, rather than creating 2 Logical sets and then combining them with NOT, resulting always in an Itemized set.
21 votes -
Add suppress functionality to context menu in list of holdings
When a staff member is looking at a list of holdings for a physical title, the right-click context menu / actions (ellipsis) menu should include a function to suppress holding.
It's inefficient to have to enter the MDE to complete this action. It's inefficient to have to run a job for just a few holdings at a time.
34 votes -
Make Public Note of a Representation Translatable
The public note of a representation is not translatable. This would be useful for following use cases:
- The library wants to offer high-resolution digital reproductions of individual files from representations on demand.
- The library wants to comment on the quality of files from a representations (eg. not OCRed).
- The library wants to inform, that the digital files does not contain complete content, etc.
By now following components in relation with digital content are translatable :
- Collection name and description
- Copyright declarations
- The denied note in the access right policy
It would offer a more streamline experience to discover digital content,…
24 votes -
Undo receipt of item on a continuous type order for which "Keep in Department" was not checked
While it is currently possible to “un-receive” from the receiving workbench if the item is still in the Acquisitions Department, that will not be the case for our continuous orders.
There is no good option for undoing the accidental receipt of a serial issue, at least not that our trainer was able to show us in our Alma Functional Workshop.
66 votes -
Alma User Role for Editing/Deleting only Quick-Cataloged Records
Scenario:
Library staff frequently need to create records for resources using the Quick Cataloging feature. Often, those records need to be edited after creation, due to mismatching resource types, updated information, operator input errors, etc. Most of the staff using the Quick Cataloging feature are not trained as catalogers, and do not have cataloging roles in Alma.Problem:
Quick-Cataloged records are not editable by staff without cataloging roles in Alma - who are frequently the creators/managers of these records. This has led to several different workarounds at various institutions:Some institutions have given their non-cataloging staff full cataloging permissions to…
65 votes -
Enhance Convert to Resource Sharing function on Pick From Shelf List
When you don't find a requested item at your institution, it is great to be able to 'convert it to a resource sharing request' -- however that function should mark the item missing from our institution. Since pick from shelf does NOT display barcode and once we select the item to be converted to resource sharing request, it disappears from the pick from shelf list, so it is very difficult and time consuming to find the item and toggle it to missing. Also, the resource sharing request might be canceled because the item at our institution shows up as 'item…
67 votes -
Enable the customization of the label of Unpaywall API link.
The unpaywall link displays with the label of "Unpaywall" in the ViewIt window of Primo. This may not be an intuitive description for some users.
We would like the option to change the service label as we do for other services in Alma.
29 votes -
Create resource sharing integration with DOCLINE
Create integration for borrowing and lending requests to be pushed/pulled to/from DOCLINE.
See https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/37290289-alma-to-docline-oai-pmh-integration for holdings integration to DOCLINE.
53 votes -
Use preferred email from Partner record for shipping digital Lending Requests
Often the Requester Email in a Lending Request is not the email that we can ship a digital item to (or sometimes the Requester Email is empty). Instead, the email address we use is from the preferred email address in the Partner record. We would like configuration to be made available so institutions could choose to use the preferred email address from the Partner record in Alma when shipping digitally instead of the Requester Email address that comes with the Lending Request.
37 votes -
Suggestions for Normalization Rules (NR) functions
Hello,
Please see the attached file.
We would appreciate it if the suggested Normalization Rules functions would be developed in Alma.Thanks
221 votesDear all, since this idea combines various very different enhancement requests for Alma's normalization rules infrastructure, we are unable to add these to our roadmap at this time. This may change as we get more information on prioritization and needs. In the meantime, we suggest opening dedicated ideas for specific enhancements you would like to promote.
-
Enable automated floating collections by allowing 'reshelve without transit' rules to update temporary library and location
Enable automated floating collections by allowing 'reshelve without transit' rules to update temporary library and location values
Currently, implementing floating collections between libraries requires manual intervention to set or update the temporary library and location values.
I would like to see functionality added to the 'reshelve without transit' rules definition, to allow the setting of a temporary library and location, in addition to preventing the transit of the item.
24 votes -
Ability to View Fines/Fees Transactions History from Fines/Fees Section of Patron Account
Currently the Fines/Fees tab of a patron's account shows current or historical fines and fees, and the user has to click on each individual fine to see whether it was paid, waived, etc. It would be helpful to have a Fines/Fees Transactions History in the patron account, where a user could easily view the history of all payments and waives performed on the account by date.
32 votes -
Expose 'Export to Worldcat' management tag to Analytics
We would like to be able to access the 'Export to Worldcat' management tag in analytics, in the same way we can access the 'Suppress from Discovery' management tag. This would allow us to gather records for which the Export tag has been set incorrectly, and use a job to Republish them to OCLC.
28 votes -
Attach printed letters to user record
We send our bill notice to a central email account for price checking before sending onto the user.
Request is for any notice to be added to a users record in the attachment tab, whether it is emailed or sent to print.
38 votes -
add next year as option in serials subscription date range picker
As many serials subscription ranges begin with the next calendar year, add NEXT YEAR as an option in the Subscription Date Range date picker. NEXT YEAR would start 1/1/[NEXTCALENDARYEAR] and end 12/31/[NEXTCALENDARYEAR].
38 votes -
An availability calendar for booking request showing the times when booking request can be made
When we request a booking, the availability calendar doesn’t show the hours when booking request can be made, it only indicates the hours when the booking is not available.
25 votes -
Option to define which library will serve a patron digitization request with priority
We allow patrons to place digitization requests on print journal articles. For this we use a central digitization department that serves several libraries of the institution. Since the request can be placed on the journal title it often occurs that several libraries could fulfill the request. At the moment the system picks the serving library randomly. Since our central digitization department is located at our central library, it would be extremely helpful, if we could define that items of the central library fulfill the requests with priority. This way we could eliminate unnecessary transfers of items between libraries and speed…
41 votes -
Improve OpenURL generation to remove blanks and duplicates
Openurls generated could by Alma/Primo be shorted by:
- Not sending duplicate parameters.
- Not sending empty parameters.
Background:
We have noticed that OpenURLs produced by Alma/Primo (which are then sent on to our ILLiad server, which can require redirection to get the patron authenticated) can be VERY long. So long in fact, that they can produce errors for our ILLiad web server. The ILLiad server will end up reporting "Request header is too large", and the user is left with a HTTP Status 400 Bad request error.
We believe the responsibility here is on the Alma/PRimo side as the urls generated…
15 votes
- Don't see your idea?