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.
120 results found
-
Enable 'School' address to be used for Personal Delivery
Currently, only addresses of the 'Home' and 'Office' Address Types can be used for Personal Delivery. Consequently, we can't use Personal Delivery and have to rely on a local workaround instead.
We would like to see 'School' addresses usable for Personal Delivery, with options in the Request Terms of Use to enable us to show only the Address Types that we use and therefore that we want our users to be able to see. E.g. we use 'Home' and 'School' but not 'Office', so we don't want our users to be able to choose that option.
Also, when the request…
13 votes -
Ability to assign fulfillment proxy to existing users
We recently tested the fulfillment proxy feature as we have a few departmental workflows we have been using shared internal accounts for. We find the functionality to be the inverse of what we would like to see. For example, we have about 10 users who place RS requests for the law review. We would like to add the fulfillment proxy to these existing user rather than making them new internal accounts.
12 votes -
Improve discoverability of rejected requests in the Monitor Requests page
We often have to locate cancelled patron physical and digitisation requests in the Monitor Requests page. However, these requests are difficult to locate as they can only be retrieved by Title (a non-unique field) and cannot be filtered or sorted.
Please add:
-A filter for request status which includes 'rejected'
-The ability to sort requests by date created or date updated so that recent rejected requests can be seen at the top of the page
-retain the requester id. The main search term we use to locate a rejected request is the requester name or id. However this is removed…12 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 -
Add task list- item request be rejected or be cancelled and become to "transit"
found that when the request(any request) is rejected in any way (by patron or librarian) the item's next step is "Transit", but there do not have task or list to let the librarian know.
it will cause these items stuck in "Transit" until someday we need them.
If we can add the task list to let the librarian know which item we should handle it should be better.
(according to case 06525736 )11 votes -
Allow other libraries to handle digitization
Under
Add a Library or Edit Library Information>LibrariesAdd an "Allow other libraries to handle digitization" tick box similar to the "Allow other libraries to handle personal delivery"
This intention would be that the item to be digitized would not need to be sent back to the library originally listed as the managing department.
This is particularly useful for those with multiple digitization departments in different locations. It would save on postage, time taken to complete the request and reduce manual intervention and monitoring by library staff.
For further clarification: Information on- Allow other libraries to handle personal delivery is…
10 votes -
Pages option for digitization requests
Creating a partial Patron digitization request allows you to define two "from: / to:" page intervals. Sometimes, articles are spread across more intervals, but with no space for this information, that data is lost.
We would like to see a simple text field: "Pages:" to be used in situations as this. This already exists in Lending requests and should also be available for digitization requests.9 votes -
add modification date to "Monitor Requests & Item Processes"
It would be helpful to have the modification date, not just the request date as filter on the "Monitor Requests & Item Processes" page. Now it's almost not possible to find items which are e.g. stuck in hold shelf processing.
The request date does not allow to filter for items/requests which have been processed recently.9 votes -
Free text box in request forms
In the same way that there is a generic tick box built into all of the request forms, it would be useful to have a generic input box where we can request additional information about the request without having to contact them afterwards (such as purpose of loan).
9 votes -
Not "Notify user" when canceling a "Patron physical item request"
In most situations we don’t want a request cancellation to be sent to users when we cancel a patron physical item request (Ful Cancel Request Letter). But since the checkbox “Notify user” is checked by default, the letter often gets sent by mistake, resulting in users thinking they will not receive the requested material, when in fact they will. We want the checkbox to be unchecked by default. Maybe this could be a configurable option in Alma (whether the checkbox is checked or not) so that each library can decide this for themselves?
9 votes -
When a hold expires, have them display in the task list
In the same way that requests show in the task list, it would be helpful that when the hold is expired that it will also show in the task list. People would see on their desktop if an item needs to be shelved or returned to a campus library, instead of remember to check the Expire Hold shelf.
9 votes -
Scan item barcode in Manage Patron Services
When using "Fulfillment -> Manage Patron Services" to view a user's account, the "Submit Request" button presumably could be used to put a hold request on an item for that user, but the only search index that this method allows is "All Titles". You can search for a title, and you can use the hamburger menu button to open up other options like MMS ID, ISBN, etc., but even this and the further embedded Advanced search only uses "All Titles". This means that you can't scan an item's barcode and put a request on that item using the "Physical Titles"…
8 votes -
Allow booking requests only on the quarter hour and half hour
If your booking resolution policies are set to "Minute", users can select any minute in the hour as a start and end time. We would like a configuration option that allows us to limit booking request start and end times to just the quarter hour and half hour.
7 votes -
Consider only the opening days and hours when calculating the transit time
The Transit Time Rule for Physical Item Requests calculates the transit time in calendar days.
As a result, days and times when the library is closed are also indicated as estimated delivery times for the requested media.
These times are also displayed in Primo and thus give users incorrect information.
Would it be possible to consider only the opening days and hours of the libraries when calculating the transit time?7 votes -
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 -
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 -
Library of Last Resort
Hello. On the 'Level of service required' drop-down menu, could you add 'Library of last resort' as an option? Or have it as a standalone field to tick? Thanks.
6 votes -
No requesting when available items in institution
We would very much like there to be an option in Alma fulfillment units (On Shelf Request Policy): "No requesting when available items in institution".
The meaning of which would be that if there is at least one (requestable) item available at any holding, the user will not be able to make a title request. The system will consider all items in the institution, not just one holding at a time.
Currently we use the "No Requesting from available holding" option which means that when all (requestable) items on one holding are checked out, then the user can make a…
6 votes -
Provide a configuration to limit by material type to a specific pick-up location
For institutions with multiple libraries where only one library may have A/V viewers or microform readers it would be helpful for that institution to limit the pick-up location by material type to the library that has the necessary equipment for onsite use.
This would eliminate confusion and time delay when a user makes a request to pick up a material type at a location where they cannot use it onsite.5 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
- Don't see your idea?