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
No existing idea results
- ~ No ideas found ~
1692 results found
-
Fix Analytics request creator field to stop it changing to Alma staff primary ID when request cancelled on Alma
When a user places a request on Primo, the ‘creator’ field in the Analytics requests table shows as ‘System’. When a request is placed by a staff member on Alma, the staff member’s primary ID shows in the creator field.
If a request placed by a user on Primo is subsequently cancelled by a staff member on Alma, the creator field changes from System to the staff member’s primary ID. This means reporting on requests placed on Primo vs. requests placed by staff members on Alma is not accurate and the field is misleading (creator should refer only to creator).
I logged a Salesforce case about this (00801207) and received the following reply:
“The feedback from Development is that this behaviour is by design, for history requests the creator is indeed the cancelling operator so they can know who completed/ cancelled the request. However, we understand and brought it up to them how confusing it is and not informative since the information about how completed requests were created is being lost. PM has also been updated about this issue.
The conclusion is that Alma is currently not designed to provide the functionality you requested, so the next step is to pursue this as an enhancement.”
Hence adding this suggestion.
When a user places a request on Primo, the ‘creator’ field in the Analytics requests table shows as ‘System’. When a request is placed by a staff member on Alma, the staff member’s primary ID shows in the creator field.
If a request placed by a user on Primo is subsequently cancelled by a staff member on Alma, the creator field changes from System to the staff member’s primary ID. This means reporting on requests placed on Primo vs. requests placed by staff members on Alma is not accurate and the field is misleading (creator should refer…
19 votes -
Resource Sharing Electronic Locate for Borrowing article requests
A borrowing article request is stopped for local ownership when the library has an electronic database that may have coverage for the journal.
Currently, the borrowing locate local ownership check does not check the year, volume, or issue in the article request to determine if the library has access to this specific year in the database. The borrowing locate does not check for embargo status.
Because the citation year is not checked for local ownership, requests are stopped from being automatically sent to lending libraries that have the article. Library staff must spend time checking if their library has access to the specific year in their electronic databases.
In Alma Configuration> Fulfillment> General>Other Settings the rsuresolverlocate can be used to check a lending library’s electronic coverage.
An additional Customer Parameter should be added to allow a borrowing library to check their own library’s database coverage information. If a request is for an article that is not within the database coverage or is in an embargo the request should be sent to the lending library without staff mediation. Requests that are found in the library’s database should be kept in the Ready to be sent status for staff to review.
This was entered as NERS enhancement request 7052.
Thanks
A borrowing article request is stopped for local ownership when the library has an electronic database that may have coverage for the journal.
Currently, the borrowing locate local ownership check does not check the year, volume, or issue in the article request to determine if the library has access to this specific year in the database. The borrowing locate does not check for embargo status.
Because the citation year is not checked for local ownership, requests are stopped from being automatically sent to lending libraries that have the article. Library staff must spend time checking if their library has…
72 votes -
Update the Subscription dates range in batch for every invoice line on an invoice
I would like to be able to update the subscription dates range in batch for every invoice line on an invoice, rather than having to open and enter the data manually for each line. I'm currently entering an invoice with over 60 lines, and the subscription dates are the same for every one of those lines. Even though I can click "this year" for each one, that's still a LOT of clicking.
28 votes -
Add option "PO Line Type" in "Request attributes"
We think the possibility to choose "Order Line Type" under "Request Attributes" would be helpful when editing a purchase request
18 votes -
Adding 'own' Covers to Alma records!
Dear,
This question might be related to:
We would like to have the ability to add covers in Alma (and display those in Primo) for all kinds of records.
Br,
57 votes -
Add Related Record MARC fields 76X thru 78X to Analytics
Library personnel would like to be able to generate a list of titles and related records in Analytics so as to document title changes, facilitate research and scholarly discovery and develop research guides for use within the institution. At this time, the 76X and 78X fields that are used to display various related record types in Primo VE are not currently indexed in Analytics. Rather than use up the limited number of bibliographic local param fields available – which would still not allow for full reporting on related records – our institution proposes that the aforementioned fields and associated data be indexed in Analytics to facilitate full reporting.
Reference – Related Record Types: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/034Get_It_Configuration/Configuring_Discovery_Interface_Display_Logic_for_Primo_VE#Configuring_Related_Record_Services
Thanks
Library personnel would like to be able to generate a list of titles and related records in Analytics so as to document title changes, facilitate research and scholarly discovery and develop research guides for use within the institution. At this time, the 76X and 78X fields that are used to display various related record types in Primo VE are not currently indexed in Analytics. Rather than use up the limited number of bibliographic local param fields available – which would still not allow for full reporting on related records – our institution proposes that the aforementioned fields and associated data…
33 votes -
Purchase Requests: Create 'Archived' Tab?
Purpose: Purchase Request Management. To retain complete request history, whether approved/ordered or rejected, in a group separate from new, not-yet-assigned requests.
Controls needed: 'Archive' operation added to the Row Action Menu. Full ability to move archived requests out of the archived condition and back into the 'unassigned' state and condition, or to delete.
22 votes -
Allow multiple time zones for institutions with campuses in different time zones
We are currently implementing Alma, and have been staggered to learn that we are only allowed one time zone as our default. We understand that (it seems) most Alma institutions only have the one time zone, but in our case we have two different time zones - and one of them has a period of daylight savings every year, so that adds to the complication.
We can't see how Alma will be functional for us with Fulfillment and the like, if we can't allow both our east and west coast campuses to have their own time zones in place when working with Alma.
Are there any other institutions out there that are dealing with multiple time zones? We did wonder if this is where instituting a consortia setup would come into play - we were told early on that very few institutions do this, but since we seem to be one of very few institutions with multiple time zones (we just had to be special), perhaps we would qualify.
Any advice would be much appreciated, or else an implementation of my idea would help us out a lot.
Thanks!
We are currently implementing Alma, and have been staggered to learn that we are only allowed one time zone as our default. We understand that (it seems) most Alma institutions only have the one time zone, but in our case we have two different time zones - and one of them has a period of daylight savings every year, so that adds to the complication.
We can't see how Alma will be functional for us with Fulfillment and the like, if we can't allow both our east and west coast campuses to have their own time zones in place when…
48 votes -
If e-collection from CZ is already active in NZ, ask for validation
It is possible to activate electronic collections from the CZ more than once in your NZ. We are aware there are use cases where this is the desired behaviour.
Yet it would be nice if there was a short dialogue: "The collection is already active in your NZ. Are you sure you want to activate it again?" - just to avoid duplicate activation by mistake.
23 votes -
Limit use of material types by specific library
The list of material types used across our consortium is very long. Even though we have turned off those that we don't use, we still have a list of about 65. For most of our libraries, this is overkill, as locations like our Chemistry library only use 4 or 5 at most. Catalogers have to use the full list, which increases the chance of confusion or clicking on the wrong thing for even straightforward cataloging. I want to be able to restrict the material types that can be used at any particular library. This was a feature of another ILS that I used and was quite helpful to reduce errors.
The list of material types used across our consortium is very long. Even though we have turned off those that we don't use, we still have a list of about 65. For most of our libraries, this is overkill, as locations like our Chemistry library only use 4 or 5 at most. Catalogers have to use the full list, which increases the chance of confusion or clicking on the wrong thing for even straightforward cataloging. I want to be able to restrict the material types that can be used at any particular library. This was a feature of another ILS…
72 votes -
When a patron renews in Primo an item from other institution borrowed by the resource sharing library should create a "Task requiring your..
When a patron renews in Primo an item from other institution borrowed by the resource sharing library the staff does not get a message of this request. The only thing is that the borrowing request changes its status to "Mediated Patron Renewal"
59 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 be found. This would also improve reporting so we can keep track of how many items are lost by patrons versus missing in the library.
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 -
Resource Sharing Claims - Sending Additional Claims and Sending Claim Letter Manually
It should be possible to configure the automatic Claims job to send additional Claims every X number of days, until the status of the request is updated to Received.
In the meantime, it should be possible to send additional Claim letters manually (and not as a General Message).
23 votes -
Claiming Resource Sharing Borrowing Requests by Format Type
The new Automatic Claim feature does not differentiate between Format Types when adding "Time to Claim (days)" in the Partner record. For example, it should be possible to write 2 days for Digital requests and 5 days for Physical requests.
21 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.
27 votes -
A separate booking calendar
Now, it is not possible to establish a separate calendar for booking request, the library's opening and closing times are used.
We would like the booking request to have a separate calendar from the Library's general hours.42 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.
23 votes -
Set preferred SMS default to "Yes"
When adding users manually in Alma the phone number has a parameter called "Preferred SMS" which is automatically set to "No". It controls whether Alma sends SMS' to the patron or not. It can only be changed after the profile is first saved. Hence it is ease to forget to toggle this setting.
We would like to have the option to choose the default setting for Preferred SMS, or the option to toggle this setting before saving on the "Quick User Management" registration form.
92 votes -
Patron services – Renew all loans
When the number of loans is more than 50, they are displayed on several pages.
When we want to renew all the loans, or to modify their due date, we can’t do it all at once, but page by page.
We would like to be able to select ALL the loans, no matter how many they are, to work them on bulk.104 votes -
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.
42 votes
- Don't see your idea?