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

3187 results found

  1. Better management of serial prediction when publication frequency changes

    Sometimes providers change a journal’s publication frequency throughout the year. So, the prediction’s pattern selected / elaborated at the beginning of the year doesn’t work anymore in Alma. One part of predictions (date of receipt) will be ok until the change but all other predicted items will be false. Now, we can revise the prediction during the year but we must erase the items already received. We can also leave the prediction defined at the beginning of the year and edit manually the false items from the time of the prediction change.

    It would save a lot of time if…

    417 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. Bursar integration: Additional fee statuses in Alma & Allow fee status change with job Import from Bursar

    Currently there exist in Alma only the fee statuses “open”, “transferred” and “closed”. Transferred means fee was exported to external Bursar system. When the fee is imported back to Alma, it is automatically Closed. For staff it is not possible to tell if the closed fee was paid, waived, unpaid etc. without consulting the 3rd party Bursar system.
    To give the librarians and end users more transparency about the (invoice) status of a fee, we would need more differentiated fee statuses. Also, we need to be able to set this status when importing the fees back to Alma using the…

    373 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. Update URL in porfolio when attached bib record's 856 is updated

    When the URL in a bib record attached to a portfolio is updated (individually edited, or batch load/overlay of records), there should be a setting to the action so that the URL in an attached portfolio would also be updated and we don't have to remember to manually do this. We have had 2 recent instances, one where we used APIs to update bib records using our old PURL manager to use our new one, only to find that the portfolio URLs also needed to be changed separately, and one where we have a batch of vendor records with changed…

    348 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. Metadata editor: Enable moving up and down within a field using arrow keys

    It would be nice to be able to move up and down within a field using arrow keys in MDE. For example, when a lengthy 505 or 520 MARC field has many lines, the cataloger must now move to the desired line using either mouse or left/right arrow keys, since pressing up/down arrow causes the pointer to move to the previous/next field.

    My suggestion is that the pointer should be able to move within the field using up/down arrows and move only to the previous/next field when the pointer is on the first/last line of the field.

    Using up/down arrow…

    335 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. 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!

    313 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Show Pickup location in the tables "Requests" and "Loans" in Patron Services

    It would be helpful ig the information “Pickup location” could be added as a column in the tables “Requests” and “Loans” in the “Patron services” in order to see the destination chosen by the Patron. Furthermore, the "Pickup location" should be displayed in Primo in the patron’s account - also in the "Loans" not only in the "Requests".

    311 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. 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…

    292 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. 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.

    271 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. 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.

    252 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. Alma - automatic warning for users about to expire with dedicated alma xml letter

    It would be useful to activate an automatic warning for users about to expire with dedicated alma xml letter.
    The customer could simply set up the amount of days before expiration and if the letter should be sent to all users or to specific user groups. A scheduled job could be activated, so that the letter is sent every day at a specific time.

    242 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. Add "Description" to the "Change Physical Items" job so that this field can be edited in batch across sets of item records

    We would like to be able to edit (and delete) the "Description" field across large numbers of records without having to do it manually for each one. The "Rebuild Physical item description" job does not help here, since the content of the field is not necessarily based on Enumeration and Chronology data.
    Several fields have been added since we started with Alma (e.g. Alternative Call Number, Temporary Call Number, Inventory Number, etc.). Therefore, we hope that this field will also be available for this job in the near future. Thank you in advance!

    232 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. Work Orders: package of required enhancements

    Work orders are useful but often cumbersome and don't work as required. A package of enhancements/fixes would make them much more useful and useable:

    • Adding notes when creating work orders in bulk. This would enable having fewer work order types as explanatory notes could be used instead.
    • Makes notes more (immediately) visible when scanning in (pop up message?). Again would enable fewer work order types as items could be easily catergorised according to explanatory note upon receipt at managing department.
    • Select recall/not recall at work order placement (like pick from shelf), not baked into type (and in…

    227 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. Prevent change of due-date when the item is under the recalled status.

    Or have an alert message of some kind when the due date is being changed.
    Because when the due date is changed, the recalled item reverts back to its initial status making it difficult to determine if there are requests placed on the item.

    227 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. Allow configuration of quick cataloguing form required fields

    We currently only use the quick cataloguing form at circulation desks to create quick records to loan items found on the shelves but not found on Alma. The items are loaned and then the work order routes them to the cataloguing team on return. All these items already have call numbers so we'd like the call number field to be a required field in the quick cataloguing form. Sometimes returned items are incorrectly returned to the shelves and if the quick catalogue record does not include the call number they are often impossible to track down.

    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)
  15. Suggestions for Normalization Rules (NR) functions

    Hello,

    Please see the attached file.
    We would appreciate it if the suggested Normalization Rules functions would be developed in Alma.

    Thanks

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

    Dear all, since this idea combines various very different enhancement requests for Alma's normalization rules infrastructure, we are unable to add these to our roadmap at this time. This may change as we get more information on prioritization and needs. In the meantime, we suggest opening dedicated ideas for specific enhancements you would like to promote.

  16. Allow staff to override if an item type is not requestable

    We would like some books (like a reference book) to be non-requestable for a student. However, we would like for staff to be able to put in a request on a student's behalf for a reference book, or perform an override when appropriate.

    220 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. Overriding and/or deleting a continuous POL at the item level

    As a cataloger at a large research library, we frequently receive gap-fill purchases of periodical issues from third-party vendors or as gifts from donors—including for subscriptions that are still open.

    We know that we can associate a POL at the holding level, but this is undesirable for these situations where we need to trace the POL/method-of-acquisition to an individual item. Also, if you change a continuous POL at the item level, Alma changes the POL for every item attached to that same holding.

    Often we have many items purchased with different (or no) POLs—subscription, firm order, gift—together on one holding,…

    219 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. Change currency in the order

    In the order the currency can not changed when the order is saved already. See attachment too, please.

    We need a possibility to change the currency after sending the order. Here are the reasons:

    a) During the order creation it was made a mistake.
    b) For subscriptions and standing orders the currency changes during the lifecycle. First we used British pound and than we use Euro, for example. The vendor changes the currency and we also have to be able to change that.

    219 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. Alma overlap analysis tool to include different identifiers in one comparison

    We would find it useful if the overlap analysis tool compare a list that includes different identifiers. i.e. ISSN, EISSN, ISBN, EISBN, TITLE in one comparison.
    Currently it only allows you to compare overlap within just one identifier. This is very important with collections from vendors that include different kinds of material.
    Being able to conduct this kind of overlap analysis is important for us in terms of making purchasing decisions and we feel that including this kind of feature in the overlap analysis tool would make this a more efficient process within Alma.

    201 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. Library opening hours for more than 3 years

    When setting standard opening hours in library calendar Alma automatically sets the field "Valid to" for 3 years. But the opening hours do not change very often. This setting also does problems by long term loans, because now the opening hours are valid to october 2024 but the library wants to loan documents to january 2025 (documents bought from some grants and the academic staff is working with these documents for a long time). In would be nice to have a possibillity to set somewhere that library opening hours should be valid for more than 3 year e.g. for 5…

    200 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)
← Previous 1 3 4 5 159 160
  • Don't see your idea?

Feedback and Knowledge Base