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
1106 results found
-
Add scheduled job which Recalculates Rota Assignment on Resource Sharing Borrowing Requests in Locate Failed Status
We are trying to configure a more automated workflow for Resource Sharing in our consortium. We recently reconfigured our Resource Sharing settings. Our Partners' Locate Profiles were all changed from not checking availability (so we had time to manually manage queues) to "Check for availability" so that items will pass instantly through the Rota if an item is not available at a partner. Then each of the Resource Sharing Libraries modified their Library Details from cancelling requests on locate failure to not cancelling requests on locate failure, which keeps the request Active after it passes through the Rota…
86 votes -
Report on empty viewit screens and better link resolver usage reports
I would like to be able to report on empty viewit screens.
Currently the link resolver usage area is not so useful, missing the openurl itself, and limiting the data that is being reported to very few request metadata elements.
Im missing, in addition to the openurl, the date/vol/issue details as well as request article title and book titles.
My goal is to be able to use these reports in order to analyze problem points - currently I'm missing crucial data that will help me analyze problems.
60 votesAlready Supported ·
AdminLiza Voloshin
(Product Owner, Alma Resource Management, Ex Libris)
responded
Hi all,
As stated in the comments for this idea, the Link Resolver Usage Subject Area in Analytics has been extended and now includes the OpenURL as well as specific context details like the article title. Requests without services are also recorded.
If you still require any additions to the subject area that were not added yet, please open a new Idea Exchange with specifics.
All the best,
Alma Product Team
-
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…
32 votes -
Make the email that is generated when an ILLiad resource sharing partner exports a request to a third party customizable
Unfortunately, ILLiad's email import feature does not always import emails generated by Alma properly. This happens mainly when there is a copyright symbol in the requested item's publication date. Giving us the ability to remove the publication date field from the email generated by Alma would help us manage this issue until OCLC and Atlas Systems can find a proper fix.
19 votes -
Apply Automatic Convert to RS TOU when marking an item missing
When requested items are marked Missing, there are no more copies of that title, and there is a TOU term for the patron/item that allows Automatic Convert to Resource Sharing, the request should automatically convert to RS.
Currently, there is a TOU term of "Automatically convert to resource sharing," but this functionality is very limited to the use case of an expired pick from shelf item. ExL's documentation indicates this should be possible, but it is not -- when an item is marked missing, the request is automatically canceled, so any job that runs will not catch that the …
37 votes -
Vendors : simplify Contact information and People contact tabs
Hello,
Handle vendors in ALMA is pretty twisted and not user friendly !
We can understand the distinction between Vendor details (network level) and Vendor account details (institution level).
But why distinguish Contact information and People contact in two separate tabs ?
This makes us input twice same informations.Our request : to get one tab for all Contacts ; each contact would be distinguished by a specific frame with name, first name, job description, email, postal mail and phone nember. All display in one single screen.
If you share this request, VOTE.
58 votes -
Change default value in pop-up message for shipped items in the scan in interface
This warning message was added in July 2020 release to prevent accidentally completing a lending request:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2020/Alma_2020_Release_Notes
With the introduction of Rapido, we noticed this warning message popping up a lot more often, and since the default value is on "Confirm", many requests are cancelled accidentally by double-scanning. We would like to suggest that this message be set by default to "Cancel" rather than "Confirm" or being able to configure the preselected default value.
The mapping table is under: IZ Configuration > Fulfillment > Physical Fulfillment > Scan In Messages Configuration > line 3 Complete lending request.63 votes -
Add pickup library code to On Hold Shelf Letter (FulPlaceOnHoldShelfLetter)
In our consortial environment we are maintaining a public list of libraries. The patrons can see the library contact information there for each library in our network - https://libraries.swisscovery.help.
We would like to add a URL link to this list to specific pickup library where the user has to pickup the title mentioned in the On Hold Shelf Letter (code FulPlaceOnHoldShelfLetter).
Unfortunately, the pickup library code is not available in the letter XML. There are pickup library name (request/deliveryaddress) or combination of library name and circulation desk name (request/calculateddestination_name). But these are not…
83 votes -
Allow AFN resource sharing requests filled outside the AFN to be delivered to the user's preferred pickup institution
If a user in an AFN requests that a resource sharing item be delivered to an institution other than their home institution, the request must be filled within the AFN in order for the user's preferred pickup institution choice to be honored. If it is filled by an institution outside the AFN, the preferred pickup institution reverts to the user's home institution, and the user is never notified of this change until the item is placed on hold at their home institution. Instead of placing these items on hold at the user's home institution, we would like Alma to…
41 votes -
Check for attachments in the Digitization Process
When managing Digitization Requests, there is no control in the last step (when files or URLs are attached) that a file or URL has effectively been attached or correctly uploaded. If operator clicks on 'Done', the request is completed without any alert!
If no file or URL has been attached when the operators clicks on Done, the requester receives a letter with no attachment or URL for download. Waste of time and bad service provided...
There should be a control before clicking on Done, at least one file or one URL should be attached before the request gets…59 votesIn the August 2019 Release the following change was done:
In the digitization process, a new confirmation message displays when neither a file nor a URL was supplied.
-
Ampersand symbol (&) in Repository search
It's found that the repository searches using the ampersand (&) symbol and the word 'and' produce different results. Our request is to make the ampersand symbol and the word ‘and’ interchangeable when Alma does repository searches.
SF case # 00646924
72 votes -
Analytics Reports for Deleted Purchase Requests
I would like to be able to run Analytics reports on deleted purchase requests. Currently, deleted purchase requests are not available in Analytics. Therefore, we don't want to delete any of our hundreds of purchase requests because we'd lose the ability to generate Analytics reports on them. Having hundreds of old purchase requests accumulate in Alma becomes unwieldy.
157 votes -
Display resource sharing request limit on user record
When a resource sharing limit is set, display the current number of requests a user has placed in the last academic year. We have users getting failed requests due to hitting the limit, this would make it much easier to troubleshoot.
3 votesHello All,
This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.
This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.
We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.
Alma Product Team
-
More information on Process Type Transit
In 'Item history', you can see when an item was checked in and out of transit, but not for whom or whereto. If something goes wrong with the transit, you can't get any information about the inactive/completed request.
72 votes -
Have multiple pickup locations available in Primo when requesting items from the same library
Our wish is to be able to offer several pickup locations in Primo for the same library when documents are available for loan (not linked to a reading room desk) without having to create a new virtual library. The library must be able to configure the visibility of these pickup locations based on certain user criteria (e.g., user group).
For example, a library may offer a special room whose access is reserved for teachers and doctoral students. The library would like doctoral students/teachers to be able to choose this room as their pickup location at the time of the request…
30 votes -
Adding User Type field
It will be great if the User Type field could appear once you click to see the requester details in a borrowing request in Resource Sharing and in Fulfillment once you click to see who holds a loaned book (Screenshots attached).
36 votes -
Improvements to Pick From Shelf list needed
Currently our staff spend too much time managing requests. Improvements to the interface for Pick From Shelf would help in some of these cases. We would like to see:
- A search box.
Very often we need to target a particular request, a task made more difficult by less than ideal facets (see #2). Search functionality exists under Monitor Requests & Item Processes, but not all options for handling requests are available in that view (such as "Skip Location").
- Better facets.
Two of the facets available in the Monitor Requests & Item Processes view would be…
67 votes -
Deleting requests older then a certain date
Would it be possible to have a way of deleting physical item requests older then a certain date? Now it's only possible to delete all requests on a title, but that's not very useful.
Highly requested titles on a courses reading list is often not relevant after a certain date, when the course has ended. We sometimes see that old requests, that we haven't been able to fulfill, are causing unnecessary delay in fulfilling requests that are still relevant for the new, active course.
When we had to close the library in spring 2020, we…
291 votesHi,
The new Delete Old Requests cloud app deletes old requests based on a CSV file. You can create a report in Analytics, for example by create date, export to a CSV file, and then use the app to delete.
See https://developers.exlibrisgroup.com/appcenter/delete-old-requests/
-
Hide Resource Sharing request button from all Primo records in a particular Primo View/Alma Campus
We wish to hide the Resource Sharing request button from appearing on all Primo records when viewed by a particular Primo view/Alma Campus.
We can currently set Discovery Interface Display Logic to "Hide service Resource Sharing Request" at the Institution level - which achieves what we want, but unfortunately blocks Resource Sharing requests on all of our Alma Campuses/Primo Views.
We would like to be able to configure the Discovery Interface Display Logic to "Hide service Resource Sharing Request" at the Campus Rules level, and thus achieve the above goal.
1 vote -
Manage Purchase Requests [Acquisitions > Purchase Requests > Manage Purchase Requests] menu
All user purchase requests are directed to the 'Unassigned' tab in the "Manage Purchase Requests" menu. It seems that this could be somewhat inconvenient for the staff handling acquisitions. Therefore, we would like to propose two suggestions. ① Enable the selection of multiple items within the 'Unassigned' tab for bulk assignment, either to oneself ('Assigned to Me') or to another staff ('Assigned to Others'). ② We would like purchase requests to be automatically assigned to the appropriate staff member based on the MARC format or vendor selected during the request.6 votes
- Don't see your idea?