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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. MDE : holding field 852 - display only the libraries in the scope of physical inventory operator

    When creating a holding in MDE, the cataloger has to choose a library in the list of libraries of the institution for completing field 852 $$b.
    The full list of all libraries of the institution in displayed for the user, even if the user has a physical inventory operator role with a scope on only one library.
    As a result he has to scroll down the list of libraries to find his own library.
    It would be much quicker if only the libraries in his scope were displayed.

    91 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Please expand the volume of Internal note fields to the Physical Item Editor

    Our library has more than three kinds of information need to be recorded in the internal note field, such as property number, new books statues notes, compensation books notes and so on.
    Hope is could add more, or became expandable let staff to select numbers of fields they needed.

    91 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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…

    87 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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!

    86 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Work orders: unnecessary message "cancel requests" when moving an item with work order

    When moving an item that has a work order from a location to another, the cataloguer receives a message "The item is in work order, moving the item will cancel the requests if the item is not requestable in the new location". Most of these messages are not pertinent, and we ask for the possibility to adjust it, so that it only appears when really necessary. It confuses cautious employees who are afraid of unintentionally deleting markers, or it is hardly noticed because too often wrong.

    86 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. List of items - when have several pages of items on a holdings, return back to active page

    I apologize if this has already been posted (I searched and searched and did not see it), but when viewing a holdings record with a list of items that have multiple pages of items (like 6-7 pages) - it would be great if Alma would default back to the page of items you were actively on, versus defaulting back to page one - every time you edit an item record on list of items page. I know that the lines on invoices that were several pages used to do the same thing (default to page one), but was fixed.

    Example,…

    82 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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_Items

    When 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…

    58 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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.

    55 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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.

    53 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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.

    44 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 44 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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.

    41 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Suppress Items from discovery for a particular physical location but keep Holding statement

    We feel that it would be useful to be able to suppress items from discovery from a particular Physical location but still display the holdings information.
    This would be extremely useful for our Journals collections, whereby we receive individual items but only want to display the holdings statement to the end user.

    41 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. When viewing an item, there should be an option to edit without leaving the item screen

    When you view an item (or click on the barcode to view an item), there should be an option on the item screen to edit the item. Instead, if we decide we need to edit the item, we have to back out of the item screen, then select Actions --> edit to edit the item. Too many clicks!

    40 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base