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.
1812 results found
-
Common link between a POL and a License (for updating collections)
A POL has a licence connected to it. It would be great if when adding that POL to an Alma Collection, that the connecting licence would be automatically added to the collection as well. And working in reverse, when adding a licence to an Alma collection, it would be nice if the POL connected to the licence was automatically added to the collection as well (thus saving time adding two things to a collection, when they are already related).
51 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.
51 votes -
Possibility for turning off Auto-Assigning in task list when opening or editing an item without completing the task in the Alma Config.
When working in several different task-lists in Alma, you are automatically assigned to any Item that you open and/or edit and exit out of without completing the task. This applies to items in the Purchase Request, Invoices (in Review) and Electronic Activation Task list and more.
This may be perfectly logical for certain institutions' workflows, but for others it may be cumbersome to have this across all task lists.
It would be great to have the ability to turn this auto-assigning on or off for the different task lists in the Alma Configuration so that people could open/edit and close…
51 votes -
Allow request-type webhooks to be triggered only under certain conditions
We would like the ability to configure request webhooks such that they are triggered only when certain conditions are met. Request webhooks for patron physical item requests include the user’s primary ID and the title they have requested. This type of circulation information should in most circumstances stay within the library and not be shared with third parties. But it may be necessary to enable a third-party integration in order to provide needed services, such as a smart locker delivery service. Currently, request-type webhooks are triggered by any request in Alma, regardless of request type or destination. We would like…
51 votes -
Move requests and temporary locations - option to flag for processing, etc.
At present the item move requests sometimes work too seamlessly. Especially for items that are onloan when the request are made (or the item is restored to its permanent location). This is an issue when the items need manual intervention, e.g. relabelling. Items go through the process without being flagged unless another process is used, e.g. a work order or fulfillment note.
It should be possible to flag items for manual intervention when they arrive at their new or original location. A message on the lines of 'Move Request: check labels etc.,' in the manner of a fulfillment note.
51 votes -
Clicking on the 'tick' alert takes directly to the notification
Clicking on the 'tick' on the Alert column on a reading list (in the Reading List Task List) would take you directly to the list of citations filtered to 'Any Alerts', or would open the 'Notes' tab if the notification is for a Library Discussion Note at list level.
51 votes -
Improve "Select all" search results selection
When running a search within Alma, we have the option to "Select All", at which point we can accomplish various tasks like "Push selected to MDE" (for a Physical Titles search), "Add to Itemized Set" and "Create Itemized Set" (for a Physical Items search), etc.
However, when clicking "Select All", this only selects the results on that page of results, which is capped at 50. If you create a search with many pages of results, you would have to take action on each page individually. Clicking "Select All" should actually select all results, not just the results on that page--or…
51 votes -
Make restored CZ electronic portfolios local when using the Manage deleted repository tool
When using the Manage deleted repository tool to restore deleted CZ electronic portfolios, the restored portfolio should be restored as local, with the blue house icon.
Currently, the restored portfolio does not become local, but instead appears as linked to the CZ (blue person icon displays), even though the CZ portfolio no longer exists. The result is portfolios in your IZ, that look like they should be CZ linked/managed, aren't. Because the portfolios appear as CZ linked, you are unable to identify the portfolio as local through filtering/reporting and take desired follow up actions. For example, if a CZ portfolio…
51 votes -
Create new reports for Authority management
National libraries and institutions managing controlled vocabularies require robust tools to ensure the integrity of their authority files. Current Alma functionality (Authority Control Task List) focuses primarily on the link between bibliographic and authority records. We propose a new set of dedicated Authority Management Reports to identify internal inconsistencies, errors, and redundancies within the authority files themselves.
Proposed Reports & Functionality
· Orphan Authority Records: Identifies authority records without any associated bibliographic records. Crucial for cleaning up legacy data or unused headings.
· MARC Encoding Errors: Detects structural errors within authority records (e.g., missing mandatory fields like 008, invalid indicators,…
51 votes -
Add functionality to Change Item Information
It would be useful to have more options in the Scan in/Change Item Information function - for example, the ability to change Material Type and Inventory Date.
50 votes -
"Fulfilment Configuration Utility"- include specific loan date for closed days
When setting up the Closed Library Due Date Management for short loan items, it would be useful to be able to test it in the Fulfilment Configuration Utility by specifying the loan date and time rather than the only option being 'if the item was borrowed now'.
For example, in order to test the rule for our 24 hour loans when taking the weekend closed days into consideration, this can only be done on a Friday, which can mean having to wait 5 days to test the parameter.
If it were possible to select Friday 08:00 as the loan date…
50 votes -
Option to define which library will serve a patron digitization request with priority
We allow patrons to place digitization requests on print journal articles. For this we use a central digitization department that serves several libraries of the institution. Since the request can be placed on the journal title it often occurs that several libraries could fulfill the request. At the moment the system picks the serving library randomly. Since our central digitization department is located at our central library, it would be extremely helpful, if we could define that items of the central library fulfill the requests with priority. This way we could eliminate unnecessary transfers of items between libraries and speed…
50 votes -
Add "Faculty" to pop-up window
Add "Faculty" inside: Configuration Menu > User Management > General > Contact Information Pop-Up.
In order to display faculty in the pop-up window with the user information50 votes -
Change physical items job -- adding notes improvement
The "Append to field" option was added in November 2023, but two additional options are still required.
'Delimiter' should be an option.
Now, the default delimiter is ";".
Some institutions use symbols other than ";" as delimiters.
For example, we use "|".
Therefore, there is a need to make the delimiter optional.Writing forward in the note
The current specification is to write backwards.
Some institutions operate writing new information in the front of the note.
There are three reasons for this.
(1)It is easier to manually add notes at the front of the note.
(2)It is easier to see…
50 votes -
Predicted Items - Add columns in Metadata overview
When opening predicted items in the Metadata Editor, the "Predicted Items" pop-up window appears. It would be very useful if the following columns could be added to the overview presented in this window.
Currently, the following columns are shown:
- Description
- Status
- Expected arrival datePlease add:
- First level of enumeration (= Enumeration A in the physical item editor)
- Second level of enumeration (= Enumeration B)
- First level of chonology (= Chronology I)
- Second level of chronology (= Chronology J)This addition would make it easier to verify whether all relevant fields are correctly…
50 votesHi all,
Please note that this idea was mistakenly closed. It has now been reopened, and we apologize for any inconvenience caused.
-
Linked Data Enrichment Moves $e Relator Subfields to Incorrect Positions When Saving Authorities with F3
When saving a name authority record in Alma using the F3 function, the Linked Data Enrichment process is causing the $e relator subfield to move to an incorrect position within the field. Instead of maintaining the expected order (e.g., $a, $e, $1), the $e subfield is often placed at the end or in another unexpected location after $0/$1 subfields are added. This disrupts the intended structure of the authority field and creates extra manual work for cataloguers.
Attempts to correct the placement by copying and pasting the $e subfield do not work as expected—Alma consistently pastes it at the end…
50 votesCan you please confirm whether the $e subfield is always expected to appear before $0 and $1 in your workflows? If this is consistently the case, it may be possible to address the issue using an XSL normalization rule to automatically position the $e subfield before these subfields.
-
Manual Deleting of User (Patron) records and need for consistency in maintaining reportable data
At present Alma has an inconsistent method of maintaining reportable patron data when a user record is deleted. The reality is that the policies established by an institution (to keep fully reportable, or keep statistics, or fully remove) do not apply when a patron record is manually deleted - ie. Deleted in: Administration > User Management > Find and Manage Users.
“Users that are manually deleted in Alma are fully removed from the system” regardless of institution policy. The Queensland Health Libraries would like to have this situation changed so that manually deleting a user (patron) record would maintain the…
49 votes -
Barcode field should be active when "Set Barcodes" opens
When receiving physical items, "Receive and set barcodes" should open the "Set barcodes" dialog box with the barcode field active. This would remove the need to click in the field before scanning in the new barcode.
49 votes -
49 votes
-
Make Push Selected to MDE button available for Itemized Sets
'Push Selected to MDE' (pushing records in bulk to Metadata Editor) is not available for Itemized sets, but it is available for Logical sets in the current Alma implementation. While the option to Push Selected to MDE is plainly visible in the Logical Set Results view (please see the attached screenshots), it is replaced by the 'Remove Selected' button in the Itemized Sets Members’ view. We would be very interested in having the Push Selected to MDE available for both Logical and Itemized sets. Is it possible to add the 'Push Selected to MDE' to he Itemized view and keep…
49 votes
- Don't see your idea?