Skip to content

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

3 results found

  1. Add the ability to select, open, and edit more than one item record at a time.

    Currently, Alma only allows one item record to be edited at a time within cataloging. To have the ability to selected multiple items, and then open them all at the same time (either in the same screen, or pop-ups) would be a HUGE time saver. Not only for catalogers, but for binding and material physical processing users as well.

    226 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)

    As of July 2020, it is possible to run jobs on selected items from both the physical items search and the items list, according to your roles and permissions. Note that a role at the institution-scope is required to run jobs in Alma, as they may affect items from various libraries. Repository managers, who can manage sets, can also create itemized physical items sets or add the selected items to an existing set from these pages.

    For more information see: https://www.youtube.com/watch?v=V_m0zP_1JVE

  2. Job to scan in items

    Our spine labeling workflow is quite bottlenecked because we have to scan each item 3 times: once to print the label, once to scan out of Tech Services, and once into scan into place. If there were a job to scan in items, we could at least reduce the 3 scans to 2 by scanning into an .xls and then running two scan in jobs on the same file.

    31 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)

    The “Scan-in operation on item” API may be useful for this. You can use this API to scan in a bulk of items. The API is documented in the Developers Network.

    A script for performing bulk scan-in of items is also described in the Developers Network.

    Please see comment for relevant links.

  3. Automatic generation of call numbers

    The call numbers play an important role as source of information for staff and users and in the workflows, that is why we also strongly miss the automatic generation of call numbers (in Aleph the Z311 table "to register the last sequence number assigned for a sublibrary + prefix, so that the next highest number can automatically be assigned when an item record is created"). When we have to do it manually it deeply lowers the efficiency of the workflows and is open for human mistakes that cause further problems.

    20 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