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 ~
1827 results found
-
Make 'requester' clickable after 'scan in items' step of handling a request
It would be convenient if it was possible to click on the requester after the 'scan in items' step when managing a request.
320 votesWhen scanning in a requested item, the requester name appears. There will be a link to the requester’s user record if the logged in user has priveleges to access the user edit form
-
Add an order action in the Purchase Request to “Approve and order from the CZ
Add an order action in the Purchase Request to “Approve and order from the CZ.” Alma would add an alert to the citation and redirect the user to the Community Zone, to the desired portfolio. The operator will only need to click on the "Approve and order from the CZ". Currently the only Action is “Approve and Order” which creates a local portfolio not linked to an E-Collection. It’s cumbersome and time consuming to re-link the POL and portfolio to the correct Community Zone record.
316 votes -
Subdivided LCSH headings should be flipped by Preferred Term Correction
Preferred Term Correction is not flipping all LCSH headings when the authority record changes. If there is an authority record that has a subdivision, it is only flipped by PTC if the heading in the bib has no additional subdivisions. This means there is a significant gap in the PTC process that requires manual attention and handling, which is unsustainable. The PTC process needs to be more thorough.
For example, this LCSH:
$a Germany $x Politics and government $y 19th century
was updated by LC to be:
$a Germany $x Politics and government $y 1789-1900
When the authority record changed, bib headings that had the original $a $x $y (only) were flipped by PTC to have the new $y. But any headings that had additional subdivisions were not flipped.
For example, this bib heading was flipped to the new form:
BEFORE: $a Germany $x Politics and government $y 19th century
AFTER: $a Germany $x Politics and government $y 1789-1900But this bib heading was NOT flipped:
$a Germany $x Politics and government $y 19th century $v Congresses.More example of headings that were not flipped but should have been flipped:
651 0 $a Germany $x Politics and government $y 19th century $v Caricatures and cartoons.
651 0 $a Germany $x Politics and government $y 19th century $v Congresses.
651 0 $a Germany $x Politics and government $y 19th century $v Exhibitions.
651 0 $a Germany $x Politics and government $y 19th century $x In literature.
651 0 $a Germany $x Politics and government $y 19th century $v Periodicals.
651 0 $a Germany $x Politics and government $y 19th century $v Poetry.Impact of Problem: The fact that PTC does not flip these headings means that staff have to manually correct hundreds or thousands of headings. The PTC process is lacking and is not performing its function of managing authority control automatically.
Preferred Term Correction is not flipping all LCSH headings when the authority record changes. If there is an authority record that has a subdivision, it is only flipped by PTC if the heading in the bib has no additional subdivisions. This means there is a significant gap in the PTC process that requires manual attention and handling, which is unsustainable. The PTC process needs to be more thorough.
For example, this LCSH:
$a Germany $x Politics and government $y 19th century
was updated by LC to be:
$a Germany $x Politics and government $y 1789-1900
When the authority record changed,…
315 votes -
Increase the visibility of digitization requests in case of multiple requests
When there is more than one digitization request on a same item (same or different requesters), only the first request is displayed in the Task List. When this request is completed, the second request is not listed in the Task List or in the “In Process Items” page, except when the barcode is scanned again.
We think that “In process Item” page should not be empty once the first request is completed. Or least, there should be an alert informing the operator that there is another request on the same item just ready to be fulfilled...
313 votesWe’re looking at adding an indication in the Manage In Process Items next to a request where there are more digitization requests for the same item in the queue. A row action will allow the staff to complete the current active request and activate the next.
-
Invalid email address list or failed to be sent notifications
We would like Alma to indicate somewhere (in a report, in the user account or else) if an email was not delivered to a patron or a vendor due to an invalid address. This would help to locate them faster and correct this data.
Otherwise, we would like to have a list by Alma institution of users / vendor accounts with invalid email addresses.Thank you!
312 votes -
Make physical item sort routines stick
For those of us working with continuing resources:
When viewing a list of physical items, the sort routine defaults to Library/Location. The items do not appear in any particular order when the results are loaded. Often I change the sort routine to Description or Receiving Date to view the most recent serial items and order them chronologically for viewing.
It would be nice if the sort routine "sticks" so that every time I open a list of items, the sort mechanism will stay on Description (not default back to Library/Location)
This would be especially helpful when managing items in the Receiving module "Received Items List," as we constantly must sort by Description to make sure no serial issues have been missed, and that the most recent issue has been received.
This is very helpful when checking PO lines in the Claims list. From the PO line details page, I click under Ordered Items>View Items. The List of Items sort routine often "sticks" here so that every time I View Items, they are automatically sorted by my previous choice (Description, Receiving Date, etc). This is the only instance I have seen the sort routine stick!
Please, Alma, remember my sorting preferences!
For those of us working with continuing resources:
When viewing a list of physical items, the sort routine defaults to Library/Location. The items do not appear in any particular order when the results are loaded. Often I change the sort routine to Description or Receiving Date to view the most recent serial items and order them chronologically for viewing.
It would be nice if the sort routine "sticks" so that every time I open a list of items, the sort mechanism will stay on Description (not default back to Library/Location)
This would be especially helpful when managing items in the…
298 votesWe will remember the user preferences for sorting the items list, so it will be "sticky".
-
Make configurable pop-up assistance in metadata editor
Currently the po-up assistance in metadata editor for subfields 260$a$b$e$f, 264$a$b, 505$r$t and 561$a is hardcoded and it can not be deactivated. Activation/Deactivation should be configurable. We have many queries from our catalogers about that.
300 votes -
Improve 'Electronic Resource Activation Task List' Management
The Electronic Resource Activation Task List does not adequately cover the multiple tasks and steps that operators need to complete during the resource's lifecycle. For example, for most electronic resources, there are usually multiple tasks in progress simultaneously (e.g., entering the EZProxy stanza on the server, ensuring admin access to the publisher's site). But because the Electronic Resource Activation Task List allows only one status to be assigned to a resource, there is no way to manage multiple simultaneous tasks nor easily determine what task has already been completed. This results in double handling and inefficient use of managing our electronic resources.
We would like the Electronic Resource Activation Task List to be improved so that operators can display a comprehensive customizable list of tasks to attend to for the resource, the status of each task and the ability to record comments relevant to each of the tasks to be completed/in progress. Operators will be able to use the Electronic Resource Activation Task List to manage the entire eresource management workflow, not just the activation component. Operators will be able to use the Task List to assign and track multiple tasks simultaneously to accommodate the non-linear process of eresource management. Institutions will be able to add custom tasks. Operators will be able to view the status of each required task and the status will remain visible until all aspects of the management process are completed.
The Electronic Resource Activation Task List does not adequately cover the multiple tasks and steps that operators need to complete during the resource's lifecycle. For example, for most electronic resources, there are usually multiple tasks in progress simultaneously (e.g., entering the EZProxy stanza on the server, ensuring admin access to the publisher's site). But because the Electronic Resource Activation Task List allows only one status to be assigned to a resource, there is no way to manage multiple simultaneous tasks nor easily determine what task has already been completed. This results in double handling and inefficient use of managing our…
293 votesThank you for the idea, we have added it to Alma road-map.
-
Serials: Editing of Description Needed
When opening predicted items, the Description-Field is populated by the data provided in “Next Predicted Item´s information” and displays these data in a certain punctuation-logic. Unfortunately, this logic is not equal to the description- (and punctuation-) logic used in German speaking countries (which is following ZETA-Standard) – and there is no possibility to edit this. Since there has to be a correct description (for sorting etc.), the only way is to open and edit every single item once it is created by prediction pattern. This is causing a lot of unnecessary work to be done manually - we need the description template to be editable so that items with a correct description can be created automatically in the first place!
Impact of Problem: Predicted items are displayed in a certain logic, for example: “V:No(Year)” [journal] or “Year: Day” [newspaper]. Format needs to be editable to suit local format (and punctuation) logic – for example “V.Year,No” [journal] or “Year,Day” [newspaper]
When opening predicted items, the Description-Field is populated by the data provided in “Next Predicted Item´s information” and displays these data in a certain punctuation-logic. Unfortunately, this logic is not equal to the description- (and punctuation-) logic used in German speaking countries (which is following ZETA-Standard) – and there is no possibility to edit this. Since there has to be a correct description (for sorting etc.), the only way is to open and edit every single item once it is created by prediction pattern. This is causing a lot of unnecessary work to be done manually - we need the…
290 votes -
Extend the "interested users" functionality
Acquisition librarians want to extend the current "interested users" functionality in order to serve the end user in a better and faster way. The current "interested users" functionality is not sufficient enough, to become useful and really benefit from this functionality we would like to extend it with:
• The ability to sort the interested user list.
Use case: some users (e.g. academic staff) have priority and should get the issue first!
• Make it possible to create hold requests on these items regardless of the existing fulfillment policy:
Use case: some libraries don't allow requests for available items, but this means they're not able to request items for interested users during receiving. (Apparently in the beginning of going live with Alma this was possible...).
• Make it possible to automatically loan the issue to the first interested user when receiving! This way limited routing functionality is made possible for (print) journal subscriptions.Acquisition librarians want to extend the current "interested users" functionality in order to serve the end user in a better and faster way. The current "interested users" functionality is not sufficient enough, to become useful and really benefit from this functionality we would like to extend it with:
• The ability to sort the interested user list.
Use case: some users (e.g. academic staff) have priority and should get the issue first!
• Make it possible to create hold requests on these items regardless of the existing fulfillment policy:
Use case: some libraries don't allow requests for available items, but…289 votesDear community, this idea was reviewed and accepted, below you can find the suggested design, please feel free to comment if you have further suggestion:
1. It will be possible to sort the interested users list using arrows. The hold requests will be activated as per the order in the interested users tab.
2. A check mark for ‘Loan to first interested user’ will cause the received item to be automatically loaned to the first interested user when the item is received.
3. It will be possible to print the list of users (in the proper order) when the item is received
Thanks,
Noam Fass | Alma product management team -
Short Term Loans - Courtesy and Overdue Notices
The new shortloancourtesyreminder & shortloanoverduereminder cannot be configured for multiple locations. For institutions with several hourly loan locations (for example Boston College maintains 2 and 3 hour loan periods for Course Reserves and a 4 hour loan period for some technology items) this dictates that the reminder notice has to be set based on the location with the shortest loan period. The overdue notice must be timed to make sense for for the longest loan period.
In our test configuration we used the following time parameters:
shortloancourtesyreminder - 105 minutes
shortloanoverduereminder - 241 minutesHowever, this creates a situation whereby patrons borrowing from some locations will have already incurred an overdue charge before the overdue notice is sent.
In order for this functionality to provide the service is designed for, it must be robust enough to support different loan periods.
The new shortloancourtesyreminder & shortloanoverduereminder cannot be configured for multiple locations. For institutions with several hourly loan locations (for example Boston College maintains 2 and 3 hour loan periods for Course Reserves and a 4 hour loan period for some technology items) this dictates that the reminder notice has to be set based on the location with the shortest loan period. The overdue notice must be timed to make sense for for the longest loan period.
In our test configuration we used the following time parameters:
shortloancourtesyreminder - 105 minutes
short…289 votes -
add security levels to norm rules
Because all norm rules can be edited by all staff with cataloger roles, there is great room for erroneous changes for rules that are applied to batch jobs. For example, the norm rule that is applied to records being brought in from Z39.50 targets can be edited by any staff member. A single error in the rule can break the z39.50 import process for all staff until the source of the error is identified. Likewise, if we have a rule applied to import profiles and a staff member inadvertently changes it and we load 50,000 records, that could cause huge data corruption. There needs to be a way to secure a norm rule to administrators such that normal staff with cataloger roles cannot change them.
Because all norm rules can be edited by all staff with cataloger roles, there is great room for erroneous changes for rules that are applied to batch jobs. For example, the norm rule that is applied to records being brought in from Z39.50 targets can be edited by any staff member. A single error in the rule can break the z39.50 import process for all staff until the source of the error is identified. Likewise, if we have a rule applied to import profiles and a staff member inadvertently changes it and we load 50,000 records, that could cause huge…
287 votesWe are considering incorporating the idea and effect both templates and rules editing permission
-
recall
Update Lending and Borrowing Status when Recalls of Resource Sharing items are cancelled
Currently, once an item is recalled in Resource Sharing, it stays in that status even after the recall is cancelled by the patron. If this could have the same functionality as regular Fulfillment (which can be configured to have the item's original return date applied if recall is dropped), that would be ideal.
281 votes -
Ability to run user purge on a set
The current purge job does not allow for granularity beyond the user group and the number of options and filters for the Purge User Records job is very limited.
It would be helpful to be able to run patron purge on a set of user records, or alternatively for Alma to add a user delete job (under Manage Jobs and Sets > Run a Job) that runs on a set.
(see also NERS Request ID 5304)270 votesHi,
Of course ! We will add a job that will be able to run on a set of user records and purge them, using standard validations (such as no existing loans, fees).
Thanks !
-
Initiate consortium fulfillment requests for items in another institution from Alma
In our consortium, we would like to be able to place requests for items in other institutions on behalf of our patrons in Alma.
Scenario: a patron (dean, faculty member, etc) calls the circulation desk asking if an item is owned by the library. Circ operator searches Alma and finds the item in a consortium library. Circ operator SHOULD be able to request item in Alma from the patron's record. Right now, circ operator has to tell the patron to search Primo and request on his or her own.
271 votes -
Fulfillment Borrowing history: allow users to choose to opt in
Currently the library can turn borrowing history on or off, but the choice applies to all users. For privacy reasons, and in order to avoid subpoena situations, we have it off, but some users do want borrowing history on as a convenience, and are not concerned about privacy risk themsleves. Why not allow those users to opt in to borrowing history, and allow the default otherwise to being off?
By the way, this "opt in" approach is how most public libraries in Eastern Massachusetts are set up, so our users expect this level of service from us also.
It is hard to explain that we leave borrowing history off because in our system turning it on exposes all our borrowers to a privacy risk. When users can't make this personal choice and control their own privacy settings at the university the way they can in their local cities and towns, it makes our library and our online system appear very "web 1.0".
Currently the library can turn borrowing history on or off, but the choice applies to all users. For privacy reasons, and in order to avoid subpoena situations, we have it off, but some users do want borrowing history on as a convenience, and are not concerned about privacy risk themsleves. Why not allow those users to opt in to borrowing history, and allow the default otherwise to being off?
By the way, this "opt in" approach is how most public libraries in Eastern Massachusetts are set up, so our users expect this level of service from us also.
It is…
265 votesFrom the Circulation Desk user update form, it will be possible to turn on a ‘keep my loan history’ check mark.
Patrons that have this check on will not have their loans anonymized when the anonymization process runs.
It will be possible to get this indication also from API, and from Primo.
The option to turn ‘keep my loan history’ on should be a library decision
-
Re-sequence MARC fields by each tag when running a normalization rule
Currently, after running a normalization rule on a set of bib records, the bib records display the 5XX fields out of order, e.g. 500, 546, 506 etc. This occurs even after running the CnmarcBibReSequenceTask as fields between 500 and 899 are not sorted, or sorted only by hundreds (this was the information given to us by a member of staff when we reported the issue on the ExLibris Customer Portal).
Having all fields in the correct order would ease any future cataloguing needed on these records, or when staff members view the record for work purposes.
I've attached an example screenshot.
Currently, after running a normalization rule on a set of bib records, the bib records display the 5XX fields out of order, e.g. 500, 546, 506 etc. This occurs even after running the CnmarcBibReSequenceTask as fields between 500 and 899 are not sorted, or sorted only by hundreds (this was the information given to us by a member of staff when we reported the issue on the ExLibris Customer Portal).
Having all fields in the correct order would ease any future cataloguing needed on these records, or when staff members view the record for work purposes.
I've attached an example…
264 votesChanging the existing re-sequencing task would impact all libraries, whether interested in this change or not - but we will look into adding a new re-sequencing task that will handle all fields, so libraries will have a choice on which re-sequencing behavior they want to apply.
-
Add “next year” as an option in serials subscription date range drop down menu for invoice lines.
Many of the invoices we process are for serials subscriptions for the following calendar year. Having “next year” as an option, for invoice line subscription ranges would be quite helpful.
260 votesDear all,
As we are analyzing the requirements for this idea, I'd like to clarify with you what should the identification of "Next Year" be?
- Is it the next calendar year (so if selected in any date in 2024 it will return the entire 2025, meaning 1.1.2025-31.12.2025)?
- Is it the next 365 days? Including today or not including today?
- Is it the next 12 months? Including current month or not including current month?
- Other?
Many thanks,
Zohar Shemesh
Alna Product Team
-
Batch deleting PO's
There is currently no system job to delete PO's. These have to be done manually using the Acquisitions>Purchase Order>Delete PO function individually in ALMA.
We have 1000's of old orders migrated from our legacy system that are no longer required. We also now only keep 7 years worth of orders in line with current financial practice and so would like to be able to set a job to batch delete at rollover into the new fiscal period.
258 votes -
Improve the e-book purchase request workflow
The purchase request workflow needs to be improved for acqusition of electronic resources.
Currently, you can either approve or reject a purchase request. An approval automatically creates a POL and a standalone portfolio based in the Purchase Request BIB record. Both outcomes are unfortunate when working with e-books. An e-book will usually be ordered on the vendor site (e.g., the ProQuest portal) rather than through an Alma POL. It should be possible to select whether a POL is created. More importantly, we'd like the option, upon approval, to select and activeate a title from among CZ collections instead of having a standalone portfolio created.The purchase request workflow needs to be improved for acqusition of electronic resources.
Currently, you can either approve or reject a purchase request. An approval automatically creates a POL and a standalone portfolio based in the Purchase Request BIB record. Both outcomes are unfortunate when working with e-books. An e-book will usually be ordered on the vendor site (e.g., the ProQuest portal) rather than through an Alma POL. It should be possible to select whether a POL is created. More importantly, we'd like the option, upon approval, to select and activeate a title from among CZ collections instead of having…257 votes
- Don't see your idea?