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.
127 results found
-
Permanent collections
Colecciones permanentes:
Si un título tienen todos sus ítems asignados a una colección permanente de documentos perdidos, extraviados, descartados, etc. , el sistema Alma debe evitar que el registro se recupere y visualice a través de Primo, esto a fin de que los usuarios no visualicen un recurso que no tiene la biblioteca y a fin de evitar de realizar otro proceso de cambio.Permanent collections:
If a title has all its items assigned to a permanent collection of lost, missing, discarded documents, etc. , the Alma system must prevent the registry from being recovered and viewed through Primo, so…93 votes -
Add Storage Location ID as column choice in Item View screen
We would like to view Storage Location ID in the item view screen within Alma: https://www.screencast.com/t/1fJ1IyCq
We can now access in Analytics however staff would like to be able to see this field without having to run a separate analytics report to see the data.
Thanks!
90 votes -
Make the effect of exclude process from publishing on holdings configurable
The current implementation of exclude process types from publishing has the side-effect, that a holdings record gets automatically suppressed as well if it only contains items which get suppressed based on the exclude from process types configuration.
E.g. if you have process type=acquisition, material type=issue, exclude=true all holdings which happen to only have items with material type issue in process type acquisition are suppressed no matter what. This is bad in itself, since it precludes the possibility of offering additional information to our users via the 866 field.
What makes things worse is that the bib record gets suppressed as…84 votes -
Add Material Type Mapping to Physical Inventory Import Profile
As a Copy-Cataloger I receive batch files of bibliographic records with physical inventory from a variety of vendors and some of these vendors send a variety of formats in the same file. These files contain bibliographic records with a material type of Book, Map, DVD-ROM, Issue, etc. With our current Import Profile that we use, the Library field, Location field, Barcode field, and Item policy field can be mapped with MARC21 local field. But this is not possible for Material type. So when we import this large file with multiple material types they are being imported with the Material type…
78 votes -
72 votes
-
Limit use of material types by specific library
The list of material types used across our consortium is very long. Even though we have turned off those that we don't use, we still have a list of about 65. For most of our libraries, this is overkill, as locations like our Chemistry library only use 4 or 5 at most. Catalogers have to use the full list, which increases the chance of confusion or clicking on the wrong thing for even straightforward cataloging. I want to be able to restrict the material types that can be used at any particular library. This was a feature of another ILS…
72 votes -
Enable the ability to make an item missing that has a process type
In order to mark an item 'missing' it currently has to have a status of 'item in place'. However, many items that have a status of 'item not in place' need to be marked as missing. If an item gets lost in transit from one library to another or has a process type of technical migration and cannot be found, those items need to be marked as missing.
The current process requires that these items be checked in so they do not have a process type before they can be made missing. This seems counter intuitive to check in an…
68 votes -
Update 863/864/865 when items are withdrawn
There is a crucial step missing in the Automatic Generation of the Summary Holdings Statement Based on Items process. The process is documented here:
https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/040Metadata_Management/020Navigating_the_MD_Editor_Page?uxp=true#Automatic_Generation_of_the_Summary_Holdings_Statement_Based_on_ItemsWhen items which are linked to the Holdings record are withdrawn, there is no process to update the Holdings record 863/864/865 fields to create an updated 866/867/868 field. When items are withdrawn, the user has to manually edit the Holdings records.
Since the creation of the 863/864/865 field is now automated based on received items being linked to the holdings record, there is a need for the 863/864/865 to be automatically re-created when the linked…
64 votes -
The ability to sort the "List of Items" by "Copy ID" or "Item Call Number"
Adding "Copy ID" and "Item Call Number" to the "Sort routine" in the "List of Items would be very helpful for us. We catalog various types of equipment to loan out to students. The equipment has a Permanent Call Number which designates the type of equipment and where the equipment is from using a code. Each piece of equipment belonging to that bibliographic record has an item call number so being able to sort by item call number or copy ID would make our life easier. Thank you.
62 votes -
Changing Holdings or Relinking Item is Possible Only in User Role Scope for SOURCE library
At present staff can move items from a library they don’t have a user role for, to a library they do have a user role for. For example, staff could move an item from the Rare Book Collection holding in one library to a Withdrawn holding in another library if they have the user role for the latter.
In the May 2021 release changing holdings for an item or relinking an item to a bibliographic record required the TARGET library to be within the scope of the user role. This prevents moving item or changing holdings for an item if…
62 votes -
Physical Item Editor - General Information Tab - add Chron. K (day) field
When in the Physical Item Editor (for periodicals receiving work), it would be more convenient if the General Information Tab included the field for Chronology K (for day of month), (along with the Chron. I (year) and Chron. J (month) fields). As it is, if the day of the month needs to be edited, you have to go into the separate ENUM/CHRON Information Tab.
58 votes -
Add a "delete" command in addition to the "withdraw" command
Currently, when a staff deletes an item record, the person can only use the "withdraw" command, even if the person is deleting an item record created by mistake. Adding an additional Delete command will distinguish the two purposes. We can then pull out WITHDRAW statistics in Design Analytics for the true withdrawn items, and not including the number of item records deleted for purposes of cleaning up data.
57 votes -
Need a way to perform "scan in" or other workflow operations in batch, either from an itemized set or from a .txt or .csv file
Use case: We have a large number of items which are being moved from our regular collection to our archives. We have already created a .txt file of barcode numbers and used that file to create a set in Alma, so that we might run Change Holdings and Change Physical Items jobs against the set. It would be much more efficient if we could then run a batch "scan in" or equivalent operations to actually place the items in transit to their new location and then the archives could likewise use that set to get the items out of transit…
56 votes -
Collaborative Collections - Index 583 more fully
Collaborative collecting agreements are becoming increasingly critical for libraries in managing collections and access across institutions. Formal agreements require libraries to update records with an appropriate Action Note (583 field) to note these commitments. Currently, only $a of the action note is indexed. All fields of the 583 (when present in bibs or holdings) should be indexed, or at a minimum $c, $d, $f and $5.
53 votes -
Item Material Type master List lacking several types
The master list of Item Material Types is lacking three types commonly used by Special Collections cataloging. Please add Archival material, Broadside, and Poster to the master Item Material Types list.
52 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.
52 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 -
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…
48 votes -
Check for existing barcode in import profile
I would like to see a setting in the import profile to check the IZ for the pre-existence of the incoming barcode. Publishing and importing can be a fairly blunt tool that leads either to too many or too few objects being imported. When importing large numbers of records, there should be a setting in the match tab that looks for that barcode and rejects the item if that barcode already exists. This would prevent needless duplication especially when publishing on the bib level.
44 votes -
Function to have a real time physical inventory
Real-time physical inventory:
1. Ability to choose location and general call number range
2.Displayed by call number order including title, number of charges, number of browses and current item status (missing, work order, on loan)
3.Capacity to mark items with different categories (determined by institution): missing, need preservation, archival box, annex bound, etc.43 votes
- Don't see your idea?