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
-
Improve import profiles to create multiple holdings
The import profiles to load bibliographic records and attach holdings and items are currently limited to only ONE holdings record per bibliographic record. We would like the ability to create multiple holdings records, one for each distinctive call number. After loading records, if we have multiple copies it is manual work to create new holdings records when the holdings have all been merged into one.
27 votes -
Location color schemes
I would like to make it an option to change the color scheme of the ALMA top ribbon/possibly sidebar to differentiate locations especially between Main Circulation Desk and Acquisitions, of which I have to switch regularly. This would save me time spent on correcting errors due to being in the wrong location for a particular procedure.
52 votes -
Item Sequences Configuration: "Set Next Sequence Value"
It is currently not possible to change the sequence value to a lower one --> error message: "The new sequence value must be greater than the current value."
In order to achieve the desired result, you then have to delete the counter and set it up again.
Please change this behavior! Thanks in advance!39 votes -
Item Sequences Configuration: import option
In the area of the "Patron/User Groups" there is already an import option (Excel file) for the configuration table.
Please provide the same feature for the Item Sequences configuration table.
Since our counters contain the year and always have to start counting with 1, we have to change this table every year. Due to our sublibraries we have more than 50 active counters.55 votes -
Electronic Coverage Dates should be in a date format and be available in Analytics as such
Currently, electronic coverage dates are considered as strings and not as Dates. We request to treat them like dates and add them to Analytics, in order to base reports on these dates.
14 votes -
Send borrowers an email when they place a request
It would be good if, when someone places a request on Primo, they could be sent an email receipt to confirm what they have requested. (This is an idea for both Alma and Primo, as I assume the email would be sent from Alma).
Not only would it be useful for users to have confirmation (a lot of webforms will send users a copy of their completed form, so people half-expect one from Primo/Alma), but it would allow libraries to include important messaging.
eg. at the moment, January 2021, we're in lockdown again, so the email could ask people to bear in mind that requested books might not be retrievable if the person who has the item is off-campus/self-isolating.
It would be good if, when someone places a request on Primo, they could be sent an email receipt to confirm what they have requested. (This is an idea for both Alma and Primo, as I assume the email would be sent from Alma).
Not only would it be useful for users to have confirmation (a lot of webforms will send users a copy of their completed form, so people half-expect one from Primo/Alma), but it would allow libraries to include important messaging.
eg. at the moment, January 2021, we're in lockdown again, so the email could ask people…
40 votes -
Bulk Change Due Dates for All libraries of institution
Add the ALL LIBRARIES option to avoid having to do one after the other
36 votes -
Allow network zone administrators to unlink bibs from member institutions
In many cases member institutions share records with the NZ that go against the consortium's policy. In these cases the only recourse is to ask the member institution to "copy to catalog", which unlinks the record, allowing the NZ to delete the bib record. This can be cumbersome in a large consortium. It should be possible for the NZ admins to perform this action, i.e. while working in the NZ to unlink a bib from member IZs, as though any institutions holding that bib had selected "copy to catalog".
32 votes -
Add publication date and subject fields to 'Portfolio Details for Consortia Members' analytics table
The bibliographic publication date and subject fields would be very useful additions to the 'Portfolio Details for Consortia Members' analytics table. Please include these fields.
54 votes -
Download COUNTER data as tabular data in addition to JSON
Alma does a good job in harvesting COUNTER data via SUSHI, and Alma Analytics is a good place for analysis. Sometimes, it is necessary to work with the data in a program such as Excel. Currently, we can only download the COUNTER reports that Alma harvests as a JSON file. It is a process to convert this file into a spreadsheet format (CSV, XLSX, TSV, etc.).
I suggest that Alma offer the option to download the COUNTER reports in tabular format, as a CSV or XLSX file.
83 votes -
Add to the Purchase request's "Approve and Order" action an option to select a PO line template.
This idea was submitted on behalf of Alma's Product management team as we would like to understand the need and use cases of the idea's description below - any comment is welcome.
Currently it is possible to save PO line as a template and utilize this template any time a new order is created (using the designated "Load from template") option (see attached image 1).
The suggested idea is to allow users the option to choose a relevant PO line template when approving a purchase request (see attached image 2), this will allow the PO line created from the purchase request to be populated with relevant fields (Reporting codes/Acquisition Method/Note to vendor etc. ) which were saved as part of the template.
This will prevent the need to edit the newly created PO line and manually add the fields which will be added automatically via the template selection (see attached image 3) as part of the purchase request approval flow.
This idea was submitted on behalf of Alma's Product management team as we would like to understand the need and use cases of the idea's description below - any comment is welcome.
Currently it is possible to save PO line as a template and utilize this template any time a new order is created (using the designated "Load from template") option (see attached image 1).
The suggested idea is to allow users the option to choose a relevant PO line template when approving a purchase request (see attached image 2), this will allow the PO line created from the purchase …
115 votes -
Allow us to suppress the License from display when it is not ready with status of "Draft" or review status "In review"
For those waiting for review licenses, we will have status "Draft" and review status "In Review". These licenses are waiting to be checked and the fields are not verified for correctness. But now once the licenses are created with inventory added, all licenses are displayed out for the user, even with status “Draft” and “In Review”.
It will be great if only the licenses with “active” and “accepted” status can be displayed, but not the “Draft” and “In review” license that they are waiting to be verified.
37 votes -
Deleting Network Zone Records from and Institution Zone in Bulk
Members of Consortia (with appropriate privilege's) need to be able to delete bibliographic records managed in the Network Zone in Bulk from within the member institution Zone
19 votes -
Ability to delete/remove redundant copyright records from the Approval Requests list
We would like the ability to delete/withdraw or otherwise remove pending copyright approval requests in the Approval Requests list.
There are a few reasons why a Library may wish to do this:
-Associated citation has since been deleted
-Patron digitization request has been cancelled
-Citations with copyright records that require manual approval were added to the Approval Requests List as part of the rollover. However, some of these units will not be using Leganto and will never submit a reading list.
In these cases, rejecting copyright is not appropriate as there was no genuine request for copyright approval. Rejecting will generate incorrect metadata and may affect future requests for copyright approval.
As a result of these scenarios, the tasklist can become full of redundant citations with copyright that will never be approved or rejected, and there is no way to remove them from the List. Such is the case with our own Approval Requests list.We would like the ability to delete/withdraw or otherwise remove pending copyright approval requests in the Approval Requests list.
There are a few reasons why a Library may wish to do this:
-Associated citation has since been deleted
-Patron digitization request has been cancelled
-Citations with copyright records that require manual approval were added to the Approval Requests List as part of the rollover. However, some of these units will not be using Leganto and will never submit a reading list.
In these cases, rejecting copyright is not appropriate as there was no genuine request for copyright…27 votes -
Allow Fines API to return closed fees in the /users/<userID>/fees/<feeID> endpoint
Something I have noticed is that the fines API has strange behavior when it comes to returning data. /users/<userID>/fees will return only fines for a certain status supplied in the query params, which defaults to active. This makes sense and is fine, but what doesn't make sense is that /users/<userID>/fees/<feeID> doesn't return closed (paid) fees. It returns this error message
{
"errorsExist": true,
"errorList": {
"error": [
{
"errorCode": "401873",
"errorMessage": "Request failed: API does not support closed fees.",
"trackingId": "E01-1412050816-2AZKJ-AWAE514295771"
}
]
},
"result": null
}This is fairly strange, I would have expected for the fine to still be returned, especially considering that the status of the fine is returned as part of the body so the consumer could still see the status and do logic to filter out closed fees if they wanted. Or alternatively there could be a flag that the consumer sets (something like includeClosed = true/false) to allow the API to return these values
The use case for this is that we do a nightly reconcile of our transactions and run them again through our processors just to make sure nothing was missed, due to the sensitive nature of needing to get things to do with people's money done correctly. Our processors then do a lookup and check to see if it's a reconcile (receipt# in Alma = receipt# being processed) or if someone has done a duplicate payment somewhere along the line (receipt# in Alma is different to receipt# being processed). However this doesn't work because this endpoint doesn't allow us to lookup previously paid fees for a specific feeID
I know I could make a request to /users/<userID>/fees, with the filter of closed fines, but this is honestly a workaround and not a real solution. As I then have to search through all those closed fines in order to find the one that I want. As we continue to use Alma over the years this list could potentially be rather long for users that accrue lots of fees
tldr - behaviour seems strange for an endpoint to not return data for a fee that does exist when the endpoint's job is to return data for one specific record, no filtering required
Something I have noticed is that the fines API has strange behavior when it comes to returning data. /users/<userID>/fees will return only fines for a certain status supplied in the query params, which defaults to active. This makes sense and is fine, but what doesn't make sense is that /users/<userID>/fees/<feeID> doesn't return closed (paid) fees. It returns this error message
{
"errorsExist": true,
"errorList": {
"error": [
{
"errorCode": "401873",
"errorMessage": "Request failed: API does not support closed fees.",
"trackingId": "E01-1412050816-2AZKJ-AWAE514295771"
}
]
},
"result": null
}This is fairly strange, I would have expected for the fine to…
21 votes -
RS BORROWING : A misleading error when patron's library card has expired
When trying to receive or send a borrowing request that is already open in alma, but the patron's library card has expired since then,
The message says: NO ITEMS CAN FULFILL THE SUBMITTED REQUEST
There is no way to guess that there is a problem with the patron info.
a better message would be: "there is a problem concerning patron's card"38 votes -
Store information about request history
It is currently not possible to see whether an item has previously been requested, only that it's checked out. I want (often) to be able to tell: how many times throughout the history of this item has it been requested and in what way (page from shelf, recall, something else). It's super weird to me that this isn't present in the fulfillment history at least, and probably in analytics.
53 votes -
Allow more than 50 POLs on a PO via manual packaging
Right now, in the Purchase Order - Package screen, you can only package 50 POLs onto one PO. The "PO lines to package" screen will only display 50 POLs max, and if you select all, then go to the next screen, it removes everything from the first screen that you selected. This means only 50 POLs max can be put on a PO. This is frustrating when we put in an order for more than 50 items and have to create multiple POs for a single order. I think the easy fix would be to have those POLs remain checked when you went to the next screen.
Right now, in the Purchase Order - Package screen, you can only package 50 POLs onto one PO. The "PO lines to package" screen will only display 50 POLs max, and if you select all, then go to the next screen, it removes everything from the first screen that you selected. This means only 50 POLs max can be put on a PO. This is frustrating when we put in an order for more than 50 items and have to create multiple POs for a single order. I think the easy fix would be to have those POLs remain checked…
42 votes -
Confirmation Notice for Curbside Bookings
Alma has allowed for the Booking Request feature to be set-up and modified as a means to provide curbisde service or make appointments. However, it appears that no letter exists to confirm the appointment day/time with the user, which would be most helpful in providing user instructions, cancellation information, contact numbers, etc. I propose that this letter be added to enhance communication and expectations especially during this challenging time of changing services and delivery options. Thank you!
23 votes -
E-resources - Add Inventory number with automatic counter
To a physical item, is it possible to add an inventory number both manually or - if configured the sequence - with the function "Allocate" to enter the next number.
For the ebook acquired in way "pick and choose", it is necessary the same function, with sequence number, price and date of inventory.27 votes
- Don't see your idea?