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.
121 results found
-
Alma-D waitlist - allow users to remove themselves and monitor waitlist status
Currently when a user joins a waitlist for a digital object (Alma-D / Alma Digital), they have no way to remove themselves after joining. This means that when their turn comes, the entire grace period must run before the object becomes available to the next user. The Delivery Registration Status Letter should include a link to remove oneself from the waitlist. In addition, the "Library Card" area in Primo/Primo VE should show the user their place in the waitlist (with details, e.g. estimate of time remaining) and also provide a link to remove themselves from the waitlist.
56 votes -
Add Purchase Requests to blocked actions
We would like to prevent blocked users from submitting Purchase Requests. Although it is possible to ask Ex Libris to configure a blocked action for Resource Sharing Requests, it is not possible to do this for Purchase Requests. It would be useful to have a blocked action for Purchase Requests that we could use in Block Definitions.
5 votes -
restrict booking access
I would like the ability to restrict booking of equipment to certain subset of patrons. Right now, if Item is bookable, it is bookable for all patrons.
2 votes -
Sticky temp location in item record
We are running into a persistent problem, wherein our circulation staff will remove an item from a temporary location, however, while the radial button in the item record does switch from Yes to No the temporary location field sticks and doesn't re-set to blank. This is an issue with reporting. We are able to fix it by running a job but when circulation staff restore an item with a temp location, the temporary location field in the item record should also adjust to it's original status of blank instead of having the temporary location stick.
1 vote -
No request cancellation with change of item description
Actually it seems that Alma automatically cancels requests when there is a change of location (not the same FU rules anymore), of item policy (not the same TOU anymore) and a change of description (as this field is to be found in the request form).
For the latter, we would like to have a possibility to choose whether the request should be cancelled.101 votes -
Configurable hard coded date for request expiry
We've struggled with users not understanding the purpose of the 'Not needed after' date field in the various request forms linked to Primo VE. This often means we received requests with supplied 'Not needed after' dates of a few days later meaning they're cancelled before even being in transit or picked, particularly on unstaffed weekends. Relabelling the field hasn't helped matters due to users not paying attention to it and thinking it's a 'needed/collect on' mandatory date.
If possible we would like the ability to set a hard coded expiry range for non-processed requests. For example, if a recall request…
3 votes -
Monitor Requests Workbench: export
When exporting (digitization) requests via the Monitor Request Workbench, we would like an overview containing also the specific request info (chapter title, pages...). The latter info can now only be obtained by manually clicking on "Edit" per request and this is only possible for active requests. For multiple digitization requests on 1 item, it is useful have all desired pages/titles exported in one overview for swift handling. Also for completed requests, it is valuable information to have all requested pages/titles in one overview.
Desired export:
- request ID + request info
- all requests (not only active)11 votes -
Ful Resource Request Slip Letter split in two
We would like the Ful Resource Request Slip Letter printout to split in two: one letter for staff when picking material from stacks, and one for use on the hold shelf for end users to see. These two functions are difficult to combine since staff need to know who the requester is at the same time as GDPR makes anonymization of the hold shelf slip necessary.
We currently try to solve this by using the Ful Hold Shelf Request Slip Letter as the hold shelf slip. But this printout is meant only for staff and so is printed in the…
3 votes -
ILL cancel/reject workflow - "Lender Reject Email Letter"
ILL workflow scenario of a library with several sublibraries.
- Step 1: The (central) Resource Sharing Department creates a fulfillment request to receive a book from a sublibrary (to be sent via interlibrary loan).
- Step 2: The sublibrary can not or will not send the book and therefore the sublibrary cancels the request. This also triggers a "Lender Reject Email Letter" to ILL partner.However, the fulfillment request cancellation form only provides these fields:
- Cancellation reason
- Cancellation noteBut a "Lender Reject Email Letter" needs the following fields:
- Reject reason
- Note to partnerThe "Cancellation…
33 votes -
Monitor Requests & Item Processes - Library Independence
It is possible to cancel processes at libraries that you do not have any role at using the Monitor Requests & Item Processes screen. A cancel button appears next to every request.
Patron physical item requests are correctly only visible based on your role but other processes such as work orders are visible and cancellable by all staff with access to the Monitor Requests & Item Processes page.
Visibility is not a problem as the data isn't private, but the ability to cancel a process should be limited by the scope of the role.
1 vote -
Configuration of “Remote Facility” Library location
Allow an institution to override a “Remote Facility” library location from being first or last for selection to fulfill a request.
This should be an option via Configuring Transit Time Rules.
An alert could be activated to notify the operator that including a “Remote Facility” library location in transit time rules will override its designation as a first or last selection.This would be immensely helpful for institutions that require flexibility to meet the needs of their users while adapting to needs of physical facilities on campuses.
Thank you
Caroline1 vote -
Skip Location for Lending Requests
For "patron physical item requests", there is an option called "Skip location". We use this option when we don't have the requested material available at our campus library, but another of our campus libraries does. In these cases, when we click on the "Skip location"-button, the request gets automatically transferred to a library which has the material available.
We would like to have a similar "Skip location"-function for lending requests. Today we have to manually transfer the lending requests between our campus libraries, if we don't have the material available at the library which originally got the request. A "Skip…
1 vote -
Make requests for multi-volume works fulfillable at location scanned in
Hi there,
If patrons submit a request for a multi-volume work at the holdings level, only the circulation desk for the Library where the volume is held can see the 'existing holdings requests may be fulfillable by scanned in item' message when the requested volume is scanned in.
We would like all circulation desks to be able to see this message and had the option to attach the item to the request at the holdings record.
Our use case is that we have many items held at offsite storage, which is set up as a Library in Alma but is…6 votes -
Generate item-level request for reading room materials
Currently, if there is one copy of an item in general stacks and another in a reading room location, assuming both are available, Alma will prioritize the stacks copy for requests and the request form will be based on the stacks request TOU. Some institutions use reading rooms for Special Collections materials, so the items may not be interchangeable and if a patron requests the reading room copy, we want the request to be specific to that item and the form to follow the reading room request TOU (limiting the pickup location).
Giving the items unique descriptions forces item-level requests,…
4 votes -
User Requests Should Pop or Be more Visible for Cataloguers
When cataloguers are processing new books or fixing bibliographic records or item records, there is no notification that a user has requested the item we are working on. We won't know to give the item to Fullfillment so that they can put the item aside for the user.
I know there is a little number that indicates there is a request, but for new books ordered in there is already 1 request from Acquisitions. This does not pop-up and it is just a little number that you can barely see in the results screen. It should be much more obvious…
3 votes -
Time stamp on printed Resource Request Slip Letter and Hold Shelf Request Letters
Add the time stamp to Resource Request Slip Letter and on Hold Shelf Request letters when printed.
1 vote -
Configuration option to prevent Digitization request when item is on loan.
Issue: Digitization requests are typically needed “ASAP” by our users. When an item is on loan, we don’t want to recall it as it will typically take longer than the requester can wait.
Current configuration options:
When Configuring Loan Recall Requests and the following is set to “Yes” PHYSICALTODIGITIZATION - Patron digitization request for physical resource, the item will be recalled. When set to “No” the item will not be recalled, instead a hold is placed on the item.Need: A configuration option for digitization requests that does not recall or place a hold(prevent renewal) on items that…
2 votes -
Include the workflow step status of a "pick from shelf" request in the API
If a "pick from shelf" request is created in Alma, it initially has the workflow step status "new". After printing the Resource Request Slip Letter, the workflow step status switches to "in process", showing that the request is now being fulfilled (meaning an employee is now picking the item from the shelf).
If this difference was included in the API call, it could be used by a discovery system to enable patrons to cancel a request only if the Resource Request Slip Letter has not yet been printed. Thus, patrons could cancel "new" requests, but not those that are "in…
6 votes -
Ubicación temporal no prestable. Gestión de reservas
Al escanear un libro con reserva, ubicado en una localización temporal, Alma automáticamente activa la reserva y envía un correo electrónico al usuario, indicando que el libro está disponible en el estante de reservas activa.
A pesar de que la política de préstamo configurada para dicha ubicación temporal no permite realizar el préstamo.Solicitamos que cuando por política de préstamo, no sea posible realizar el préstamo de un libro reservado, no se active la reserva y no envíe correo electrónico al usuario.
18 votes -
Prioritize requests by location or fulfillment unit
When a user submits a request at the title level in Primo VE there should be a way to prioritize certain items in a holding by location or fulfilment unit. For example, if a book has copies available in a circulating location, but there are also copies available in a non-circulating collection that is managed by a Reading Room desk, the circulating item should always get priority.
17 votes
- Don't see your idea?