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 ~
1749 results found
-
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 has no 'Not needed by' date and the item is never returned, the request will stay open forever and will need to be manually deleted requiring more routine house keeping work. If we could tell the system to close such requests after X number of days/months it would help managing these requests.
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…
5 votes -
Add option for patron name suffixes like Jr., Sr., or III
Name searches in Alma for names containing suffixes like Jr., Sr., or III yield strange results.
Example: Someone named Joe Johnson Jr. will have first name "Joe" and last name as "Johnson Jr." When performing searches in Alma for "Joe Johnson", "Joe Johnson*", or "Joe *Jr." will not yield any results.
Alma looks for "Jr." as a last name rather than the person's surname. This isn't helpful when SIS has the suffix but the patron may not use the suffix all the time in their everyday life.
Creating the option for a patron name suffix or updating the search for the patron's surname regardless of the suffix would help resolve this problem.
Name searches in Alma for names containing suffixes like Jr., Sr., or III yield strange results.
Example: Someone named Joe Johnson Jr. will have first name "Joe" and last name as "Johnson Jr." When performing searches in Alma for "Joe Johnson", "Joe Johnson*", or "Joe *Jr." will not yield any results.
Alma looks for "Jr." as a last name rather than the person's surname. This isn't helpful when SIS has the suffix but the patron may not use the suffix all the time in their everyday life.
Creating the option for a patron name suffix or updating the search for…
4 votes -
Add a new privilege to the "Purchasing Operator" role which will prevent users with this role from being able to delete items
This Idea was submitted by ExLibris to check the community support for the following enhancemnet:
Currently, users with "Purchasing Operator" role can delete items, the existing logic behind this is, when a PO line is created (even before it is received), there is a need for the Purchasing Operator to be able to delete the item in case of an error on the order.This Idea suggest to add a new privilege to the Purchasing Operator role which will prevent this user from being able to delete items - the new privilege should be enabled by default to maintain existing functionality for all customers and, for institutions who will desire to, they can contact ExLibris support and ask to disable the new privilege and by that remove the user's option to delete items
This Idea was submitted by ExLibris to check the community support for the following enhancemnet:
Currently, users with "Purchasing Operator" role can delete items, the existing logic behind this is, when a PO line is created (even before it is received), there is a need for the Purchasing Operator to be able to delete the item in case of an error on the order.This Idea suggest to add a new privilege to the Purchasing Operator role which will prevent this user from being able to delete items - the new privilege should be enabled by default to maintain existing…
0 votes -
New role for limited user account editing
It would be helpful if we had a separate role for User Operator that could edit any user account's contact details and merge user records as well as run analytics on users BUT not change or add roles attached to that account OR delete records. This is primarily to allow circulation staff more control over user accounts but to restrict access to higher-level abilities for cybersecurity reasons.
1 vote -
Creating an invoice without PO number as invoice number
Now when I create a new invoice from PO, then at the tab Summary there is automatically filled a PO number as an invoice number. We would appriciate some setting which would cause that this field wouldn't be filled out automatically and would stay empty. Our librarians are using other invoice numbers and current setting of Alma is leading to errors because sometime the librarian forgets to change the invoice number. We would appriciate if Alma wouldn't filled out the invoice number automatically with PO number. We would like only a warning by saving the invoice that the invoice number is empty so we'll have to fill out this number manually.
Now when I create a new invoice from PO, then at the tab Summary there is automatically filled a PO number as an invoice number. We would appriciate some setting which would cause that this field wouldn't be filled out automatically and would stay empty. Our librarians are using other invoice numbers and current setting of Alma is leading to errors because sometime the librarian forgets to change the invoice number. We would appriciate if Alma wouldn't filled out the invoice number automatically with PO number. We would like only a warning by saving the invoice that the invoice number…
8 votes -
Analytics widget - customize/remove Open in a new window link
I'd like to be able to remove or customize the "Open in a new window" link that appears on top of a widget of an analytics report.
The widget can only fit a very short report. Opening this short report in full view is not that useful. It would be better to link to a longer report or a dashboard.
1 vote -
Add a link from the PO line to the "Receive" workbench
It would be helpful to have a link to the receiving workbench from a POL, to eliminate the extra step of receiving items that are ordered but already in hand. This applies especially to standing orders and gifts. We already have the items in hand at the time of order creation. With the current setup, we have to 1) create the POL, 2) write down the POL number or copy it before selecting Order Now, 3) switch to Receive to receive the item in order to close the POL. Merging step 3 into the POL creation process would save a lot of time.
It would be helpful to have a link to the receiving workbench from a POL, to eliminate the extra step of receiving items that are ordered but already in hand. This applies especially to standing orders and gifts. We already have the items in hand at the time of order creation. With the current setup, we have to 1) create the POL, 2) write down the POL number or copy it before selecting Order Now, 3) switch to Receive to receive the item in order to close the POL. Merging step 3 into the POL creation process would save a…
23 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 -
Physical PO line creation - allow the interested user defined on the PO line to place a title level request when the PO line is created
This idea was submitted by Ex Libris to evaluate the need for the enhancement specified below:
Today, when a physical PO line has an interested uset, a hold request is not created on the bibliographic title until the book is scanned in at a circulation desk (Item is received).
Customer rely on being able to see all requests on a title from the moment it is purchased. This is because they want both users and staff to be able to see the whole physical request queue from the moment a book is purchased, currently it creates uncertainties about who is in the queue. A user might not be the first in a queue even though there is no other requests on the title. As a workaround, users create the PO line and search for the title to create a title level request, this is a click heavy process.The need is to allow institutions to define a parameter which will create a title level request on the time of the PO line creation with an interested user.
This idea was submitted by Ex Libris to evaluate the need for the enhancement specified below:
Today, when a physical PO line has an interested uset, a hold request is not created on the bibliographic title until the book is scanned in at a circulation desk (Item is received).
Customer rely on being able to see all requests on a title from the moment it is purchased. This is because they want both users and staff to be able to see the whole physical request queue from the moment a book is purchased, currently it creates uncertainties about who is…0 votes -
attachement tab in e collection editor
can we have an attachements tab in e collection editor so we can attach useful docs/comms relevant to that source, thank you
3 votes -
Claiming at Item Level
Being able to claim at item-level so that we can mark an expected issue at CLAIMED/CLAIM so that magazines, journals, newspapers, and serial publication books would be easier to claim.
7 votes -
Allow AFN loans and returns via Offline Circulation
AFN (Automated Fulfillment Network) items can neither be loaned nor returned via Offline Circulation. The Offline client accepts the AFN barcodes, but when we attempt to load the file into Alma the resulting error message is "Item not found. Barcode: [barcode number]". Since non-AFN resource sharing loans are considered “local” records in Alma, they can circulate via Offline Circulation. Please add this functionality for AFN loans and returns as well.
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 are currently on loan.
Desired Outcome: TOU or Loan recall configuration option to select: Patron digitization request for physical resource when item is on loan – Yes/No?
if “Yes” then select if the request creates a recall or a hold(prevents renewal).
If “No” Item will not be requestable.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 -
Ability to exclude Primo Journal Search from display logic rules
We would like the ability to exclude the Journal Search function from display logic rules.
Why?
In the Primo view the limit of links is set to 25, and it cannot be reduced (which deserves another Idea....). The only way to reduce it is through the user of display logic rules.
However, the rules also apply to the "Journal Search" in Primo, where users actually want to see all the available full text due to differences in coverage.29 votes -
1 vote
-
Scan-in items to create an Itemized Set
For many of our workflows, we have a large batch of physical materials upon which we need to perform a bulk action (e.g. place them all on a Work Order or request a Permanent Location change, etc.) The items are on book trucks and there is no Set upon which to Run a Job unless we create a new one every time as a TXT or CSV file, which then has to be uploaded to Alma. It would save a lot of confusion, plus work and training time for staff and student workers, if it was possible to use Scan-In functionality to create a set directly in Alma. Just scan-in all the barcodes you want, and there's your Itemized Set.
For many of our workflows, we have a large batch of physical materials upon which we need to perform a bulk action (e.g. place them all on a Work Order or request a Permanent Location change, etc.) The items are on book trucks and there is no Set upon which to Run a Job unless we create a new one every time as a TXT or CSV file, which then has to be uploaded to Alma. It would save a lot of confusion, plus work and training time for staff and student workers, if it was possible to use Scan-In…
11 votes -
Allow VAT % amount greater than 100% when VAT Type is not Exclusive
We receive a 'The field VAT % contains an invalid value' error when a VAT % amount is recorded as being >100% and we cannot progress the invoice any further. This error is valid when VAT Type is 'Exclusive', because it indicates that the VAT Amount > Total Amount. But it shouldn't be invalid when the VAT type is Line Exclusive or Inclusive, because it merely indicates that the VAT Amount > the amount of the other invoice lines.
We encounter the problem when paying invoices where the invoice primarily consists of a taxed amount. This is common when receiving invoices from customs where we need to pay the tax on an item that we have already paid for on a separate invoice to a different supplier.
We have a workaround, similar to the solution that Ex Libris has offered, which is to use a field other than VAT Amount to record the VAT in these cases. However, Alma integrates with our Finance system and it's not easy to write these exceptions into the integration, and it's confusing for staff keying the invoice. We could instead continue to use the VAT Amount field to record all tax amounts if one of the following solutions were implemented:
1) display this error message only when VAT Type is ‘Exclusive’ and VAT amount >100%, because it shouldn't be invalid when the VAT type is Line Exclusive or Inclusive, or
2) give us the option to disable this error message entirely so that it shows as an Alert only, which we can ignore.We receive a 'The field VAT % contains an invalid value' error when a VAT % amount is recorded as being >100% and we cannot progress the invoice any further. This error is valid when VAT Type is 'Exclusive', because it indicates that the VAT Amount > Total Amount. But it shouldn't be invalid when the VAT type is Line Exclusive or Inclusive, because it merely indicates that the VAT Amount > the amount of the other invoice lines.
We encounter the problem when paying invoices where the invoice primarily consists of a taxed amount. This is common when receiving…
5 votes -
XML Expansion for "Ful Resource Request Slip Letter" with Data about Reshelving Status and about Expected Date when Item will be Reshelved
For fetching requested media at the stacks we are making use of the "Ful Resource Request Slip Letter" in printed form which we customized according to our needs.
Unfortunately, the data fields that contain
- the information that the requested item might currently not be at the stacks because it has just been returned and is therefore very likely on its way back to the stacks (Status = awaiting_reshelving)
- and the information when the requested item is expected to be reshelved ("reshelving_time")
are not provided in the XML data of the "Full Resource Request Slip Letter".
This information, when be presented on the "Ful Resource Request Slip Letter" printout, would be very helpful, as in our case it will avoid unnecessary walks through the shelves at the stacks.
The data fields we need for the printout are available in Alma. They can be viewed in Alma and as well as in PrimoVE and can be accessed via the Alma API. The generation of this data is based on the library's "Time to reshelving (hours)" settings. (see attached file: LibrarySettingsTimeToReshelve.gif)
You can find the information concerning the fields "awaitingreshelving" and "reshelvingtime":
- via Alma API: when quering via Bibs API in the fields "awaitingreshelving" and "reshelvingtime". (see attached files (BibsApiRequest.txt + BibsApiResponseJson.txt))
- in Alma System: when displaying information on item level you can find the information in the column "Status" (see attached file: InformationDisplayedInAlma.gif)
- in PrimoVE System: the information can be found in "Status:" of the single item (see attached file: InformationDisplayedInPrimoVE.gif)
We would be very happy about the inclusion of the two data fields into the XML data structure of the "Ful Resource Request Slip Letter".
Thank you
For fetching requested media at the stacks we are making use of the "Ful Resource Request Slip Letter" in printed form which we customized according to our needs.
Unfortunately, the data fields that contain
- the information that the requested item might currently not be at the stacks because it has just been returned and is therefore very likely on its way back to the stacks (Status = awaiting_reshelving)
- and the information when the requested item is expected to be reshelved ("reshelving_time")
are not provided in the XML data of the "Full Resource Request Slip Letter".
This information, when be presented…
57 votes -
License field for Purchase Order Line value
We would like a total values field on the Summary tab of a License that gives us the total cost of all the PO Lines which that license covers. This would tell us quickly the expenditure value of each license in Alma and enable us to prioritise license workflows by expenditure value.
1 vote -
Option to reset reloan limit at a specified time each day
We manage laptops as inventory in Alma, and as such they are governed by Terms of Use and Advanced Policies. Our policy is that a user can checkout one laptop at a time, renew it once, but then can't checkout any more in that same calendar day.
Currently the reloan limit allows blocking by "Other - you may define the time span (in the Unit of Measurement) in which the same item may not be reloaned - minutes, hours, days, weeks, or months. Note that this option includes the Parallel option and blocks both parallel loans and same item loans in the specified time span. There is no option to block reloaning without blocking parallel loans."
We would like there to be an option that resets the reloan limit everyday at a specific time. In our case, midnight would be fine, but we feel it would better if every library could specify a time when the reloan limit would reset. There are situations where specifying the block in terms of hours or minutes will not work given that our library is open 24 hours.
We manage laptops as inventory in Alma, and as such they are governed by Terms of Use and Advanced Policies. Our policy is that a user can checkout one laptop at a time, renew it once, but then can't checkout any more in that same calendar day.
Currently the reloan limit allows blocking by "Other - you may define the time span (in the Unit of Measurement) in which the same item may not be reloaned - minutes, hours, days, weeks, or months. Note that this option includes the Parallel option and blocks both parallel loans and same item loans…
3 votes
- Don't see your idea?