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 ~
1754 results found
-
Receiving note for electronic resources
It would be fantastic if a receiving note option was included for electronic resources as it is for print resources (a field which can be extracted for analytics). The current notes field can not be accessed via analytics and it is therefore difficult to track trends in usage, information about cohorts using different resources, reasons for purchasing, etc.
35 votes -
Alma to support Hold Information in SIP2 checkin reponse
We have a sort assistant (RFID equipment) that displays the next step/destination of an item on screen. It also generates a hold slip (with the hold patron name if there's a request for that item) or a transit slip (if it needs to be sent to another library).
However the hold information is not provided in the SIP2 checkin response which means having to scan in the item again in Alma to get this information.Could the following SIP2 extension fields be added to resolve this issue:
CY - Hold Patron Id
DA - Hold Patron Name84 votes -
Facet for PO Lines Secondary & Tertiary Reporting Codes
We'd really like the ability to facet in PO Lines by the Secondary & Tertiary Reporting Code fields. It's possible to facet by the main Reporting Code but not by the other two reporting codes.
10 votes -
Renewal Operator in Analytics
It would be useful to include Renewal Operator details in the Fulfillment Analysis area on Alma Analytics. This would allow us to identify and report on the number of renewals that took place at the circulation desk, via self service or via Primo.
19 votes -
Field for academic year in user profile
It would be good if there were a field in the user's profile that states the user's academic year, e.g., YEAR 1, YEAR 2, YEAR 3, etc.
112 votes -
Job and/or API to unlink a set of bib records from the CZ
We would like the ability to run a job or use an API that would unlink a set of bib records from the CZ. There are currently both a job and an API that will unlink records from the NZ, but not the CZ.
Use case: ebook portfolio records provided from vendors can be extremely brief, missing many points of discovery (e.g., no subjects, tables of contents, etc.). When portfolio bibs are linked to the CZ, we are forced to update each of these portfolios one at a time, which is painstaking and inefficient. We already have scripts that use the Bib API to update physical records; if there was a CZ equivalent of the "op=unlinkfromnz" API parameter, we would be able to unlink these inferior records from the CZ, add necessary fields, and update the bib record, all using the Bibs API.
We would like the ability to run a job or use an API that would unlink a set of bib records from the CZ. There are currently both a job and an API that will unlink records from the NZ, but not the CZ.
Use case: ebook portfolio records provided from vendors can be extremely brief, missing many points of discovery (e.g., no subjects, tables of contents, etc.). When portfolio bibs are linked to the CZ, we are forced to update each of these portfolios one at a time, which is painstaking and inefficient. We already have scripts that use…
30 votes -
Make Manage Fulfillment Activities the same thing as Manage Patron Services
I found this idea buried in a comments section and felt it deserved its own idea since my team keeps encountering the same problem.
Iain Gray said: "After finding a user it would be useful if when clicking on Manage Fulfillment Activities you were presented with the same screen as though you had used the Manage Patron Services screen. Instead you do not see the option to pay Fines and Fees from here and have to re-enter users details again."
I'll add that it would be great if Manage Patron Services and Manage Fulfillment Activities were the same page and named the same thing. The staff user experience is tedious:
1) Patron comes to desk with scant details about their account,
2) Staff runs a user search in the persistent search,
3) Staff reads out list of checked out items and fines owed,
4) Patron wants to pay fines, and then
5) Staff run a new search in Manage Fulfillment Activities from the “Fulfillment” dropdown.Re-entering the user details over and over again into different search fields has become a hassle for desk staff, especially here in an academic library at the end of a semester when everyone's trying to settle their debts with us in the same week.
I found this idea buried in a comments section and felt it deserved its own idea since my team keeps encountering the same problem.
Iain Gray said: "After finding a user it would be useful if when clicking on Manage Fulfillment Activities you were presented with the same screen as though you had used the Manage Patron Services screen. Instead you do not see the option to pay Fines and Fees from here and have to re-enter users details again."
I'll add that it would be great if Manage Patron Services and Manage Fulfillment Activities were the same page…
60 votes -
Improving usability of the inventory section for citations
Currently, it’s impossible to tell how ‘Digital’ and ‘Other’ inventory may be configured in the Inventory section of a citation. The green indicator shows the inventory exists but not whether it has been used for the citation.
Digital example:
You can’t see whether a digital representation has been selected via the ‘Manage Digital Representations’ option or whether a representation is Active or Inactive. The green indicator stays green even if the representation is Inactive or if it hasn’t been selected via Manage Digital Representations.Other example:
You can’t see whether the Link Resolver has been disabled via Edit > Citation Parameters > Disable Resolving. The green indicator stays green even when you disable resolving.As a result, when a citation isn’t behaving as expected in Leganto it’s time consuming to identify the cause. If there were enhanced indicators within the Inventory section, you would be able to tell at a glance what the problem may be (e.g. the representation has been set to Inactive, it hasn’t been selected via ‘Manage Digital Representations’ or link resolving has been disabled).
Currently, it’s impossible to tell how ‘Digital’ and ‘Other’ inventory may be configured in the Inventory section of a citation. The green indicator shows the inventory exists but not whether it has been used for the citation.
Digital example:
You can’t see whether a digital representation has been selected via the ‘Manage Digital Representations’ option or whether a representation is Active or Inactive. The green indicator stays green even if the representation is Inactive or if it hasn’t been selected via Manage Digital Representations.Other example:
You can’t see whether the Link Resolver has been disabled via Edit > Citation…26 votes -
Bibliographic records editing history
Here is an enhancement request concerning bibliographic records editing history.
Currently, the "View Versions" can only tell the different version of a bib. record. However, this cannot tell logging history of updating/editing the bib. records, e.g. who add/remove a MARC fields/who suppressed/released the bib. record etc. This is no history tab to keep tracking the changes of a bib. record which is unlike other history tab functionality available in other Alma pages, e.g.
• The PO Line Summary page when editing a PO line
• The Physical Item Editor page when editing item records
• The License Terms Details page when editing license detailsIt is good to know logging history of updating/editing the bib. record for a record life cycle.
Here is an enhancement request concerning bibliographic records editing history.
Currently, the "View Versions" can only tell the different version of a bib. record. However, this cannot tell logging history of updating/editing the bib. records, e.g. who add/remove a MARC fields/who suppressed/released the bib. record etc. This is no history tab to keep tracking the changes of a bib. record which is unlike other history tab functionality available in other Alma pages, e.g.
• The PO Line Summary page when editing a PO line
• The Physical Item Editor page when editing item records
• The License Terms Details page…131 votes -
Make "additional code" for vendors searchable
Using the additional code field to track changes in the Vendor Code field make sense, but has limited use if we can not search it in any meaningful way.
22 votes -
KBART export from Alma to include title level URL
As we from time to time need to interface with software and services outside the ExLibris suite, it would be great if the KBART Schema for export would include a proper title level URL as specified in the KBART Recommended Practice:
"[Title level URL] Indicate the URL of the title’s homepage.
For journals, this page should be a listing of the available volumes and issues. "37 votes -
Preferred term correction - correct coding when flipping LCSH to LCGFT
When a 655 field is coded for LCSH and matches a non-preferred term in LCGFT, Alma flips the heading to the preferred LCGFT term but does not update the coding (it should change the 2nd ind to 7 and add $2 lcgft).
The problem is limited to cases where:
A bib heading 655/_0 matches a non-preferred term in an LCGFT authority
What happens is:
The PTC job flips the heading to the LCGFT preferred form, but it does not change the 2nd-indicator from 0 to 7, and does not add $2lcgft
What is not a problem:
655/0 headings that already match preferred LCSH/LCGFT form
655/7, $2 lcgft (these get controlled appropriately)
655/7, $2 fast (these get controlled appropriately)
655/7, $2 any other vocab (these do not get controlled)Example of the bug:
Before: 655/0 $a Dissertations, Academic
After: 655/0 $a Academic theses.When a 655 field is coded for LCSH and matches a non-preferred term in LCGFT, Alma flips the heading to the preferred LCGFT term but does not update the coding (it should change the 2nd ind to 7 and add $2 lcgft).
The problem is limited to cases where:
A bib heading 655/_0 matches a non-preferred term in an LCGFT authority
What happens is:
The PTC job flips the heading to the LCGFT preferred form, but it does not change the 2nd-indicator from 0 to 7, and does not add $2lcgft
What is not a problem:
655/0 headings that…
74 votes -
delete pol
We really have the requirement to delete a POL attached to a PO in our daily work, we will have to reopen the POL and then cancel it and then delete it, it’s kind of complicated and can we delete it directly?
13 votes -
Change default in loan history to fulfillment activities
In loan history the default radio button is item changes. Better to have fulfillment activities as default because it displays displays loans, returns and in-house-use.
16 votes -
Adding a Parameter to Partner Record
We would like to add the parameter Library Type to the Partners e.g. CL=College Library, UL=University Library, HL=Hospital Library etc..
24 votes -
Electronic Portfolios - can we have a new coverage line where free access can be added ?
At present in the coverage tab, there are the global dates, local, and perpetual (if the collection has been identified as having some perpetual access) Some of these titles have free access, which is not technically perpetual but is also not part of a subscription. Could a new line be added to include these free years/volumes, with the option to display these dates (or not) ? It would allow us to reduce the number of Free collections we have which all take users to the same place, and identify why we have access to journal years outside of our subscription dates
At present in the coverage tab, there are the global dates, local, and perpetual (if the collection has been identified as having some perpetual access) Some of these titles have free access, which is not technically perpetual but is also not part of a subscription. Could a new line be added to include these free years/volumes, with the option to display these dates (or not) ? It would allow us to reduce the number of Free collections we have which all take users to the same place, and identify why we have access to journal years outside of our subscription…
11 votes -
Add " Additional e-mails " fields to " Report to ex libris " form in Alma
In Salesforce the customers can use "Additional e-mails" feature to let colleagues know that they have (already) opened a case for a specific issue. This makes teamwork easier.
For SF cases opened using the "Report to ex libris" feature, this is not possible. Plase add 5 "E-mail 1" - "E-mail 5" as in SalesForce.
17 votes -
export sets into Analytics
I appreciate the ability to export Analytics results directly into an Alma set, but I would like to be able to export a set of records directly into Analytics without having to recreate my Alma search (if I can) in Analytics. This would also be very helpful for working on sets of records that other people at my institution have created!
56 votes -
Update import profiles, so portfolios are listed in ALMA & Primo in the same order as the 856 fields in the bibliographic record
Currently electronic portfolios are generated from the 856 fields in the bibliographic record, but they appear in reverse order in ALMA and Primo. Vendors often have 856 for multiple volumes in their records and they often list URLs in the order of their importance. In my attached example, the vendor includes a link to browse the particle resource first, then links to search the collections which contains the resource. The links are listed in order of importance. It is confusing to the user to list v.2 before v.1 and less important searching options before the most direct way of access the material. This should be corrected.
Currently electronic portfolios are generated from the 856 fields in the bibliographic record, but they appear in reverse order in ALMA and Primo. Vendors often have 856 for multiple volumes in their records and they often list URLs in the order of their importance. In my attached example, the vendor includes a link to browse the particle resource first, then links to search the collections which contains the resource. The links are listed in order of importance. It is confusing to the user to list v.2 before v.1 and less important searching options before the most direct way of access…
61 votes -
Keep suppressed records without items that have received more than one purchase request
We have detected this case that we consider is an incorrect behavior of Alma.
When a purchase request is generated, a non-visible bibliographic record is created. The problem is that if a second purchase request for the same document is generated, Alma automatically makes the bibliographic record visible, even though we still do not have copies of it. Therefore this record appears visible in Polibuscador but without funds.
We request that the bibliographic record should only be visible when the issue or copies are available to the user, meanwhile, even if more than one purchase request has been made, it should remain suppressed.
We have detected this case that we consider is an incorrect behavior of Alma.
When a purchase request is generated, a non-visible bibliographic record is created. The problem is that if a second purchase request for the same document is generated, Alma automatically makes the bibliographic record visible, even though we still do not have copies of it. Therefore this record appears visible in Polibuscador but without funds.
We request that the bibliographic record should only be visible when the issue or copies are available to the user, meanwhile, even if more than one purchase request has been made, it…
38 votes
- Don't see your idea?