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

1830 results found

  1. Copy and paste multiple MARC fields into the metadata editor

    We would like to be able to copy multiple lines from MARC records and paste them into the metadata editor so that multiple MARC fields are pasted into the record in one action. This would help us enormously with our workflow of importing MARC authority records from LibrariesAustralia into Alma.

    For us, this is necessary because the LibrariesAustralia headings are not in the community zone and are unlikely to ever be included there and Alma does not allow for Z39.50 import of authority headings.

    We have this functionality of copying and pasting multiple fields in the LibrariesAustralia Cataloguing Client and…

    542 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,

    I believe we now understand the requirement better: To be able to paste a block of text in MARC 21 format, and have Alma parse it and populate the MARC tags, indicators and subfields accordingly.

    This is a larger development, but we hope to be able to add a solution for it to our future roadmap.

  2. Allow user to ‘Withdraw’ and ‘Open Predicted Items’ from the ‘Received Items Screen’.

    Currently, ‘Withdraw’ and ‘Open Predicted Items’ functions cannot be performed from the ‘Received Items List’, during normal receiving operations.

    https://drive.google.com/file/d/1qdNSY1xkPr71R7XJzPp8QtQJEa_h-00i/view?usp=sharing

    Instead, a user must back out of the receiving windows, perform a title search, and access these features through the ‘List of Items’ window.

    https://drive.google.com/file/d/17yB9XwMI6MYAmnHq95mna6cOUMpXzlbq/view?usp=sharing

    This drastically decreases efficiency in performing routine tasks in Prediction, Receiving, and Weeding.

    What should be changed: As Serials Processors, we would like to see the ‘Withdraw’ and ‘Open Predicted Items’ functions added to the ‘Received Items List’ window, so that all serials management tasks can be done from one screen. This would eliminate the…

    536 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 community, as part of the ongoing UX improvements in Alma, the "Receive new material" screen (aka Receiving WB) is planned to be refactored and support the need described in this idea. For more information see Alma roadmap:

    https://knowledge.exlibrisgroup.com/Alma/Product_Materials/010Roadmap/Alma_Roadmap_Highlights_(2022-2024)_-_July_2022_Update/Acquisitions#Receiving_Workbench_-_Enhanced_UX


    Thanks,

    Noam Fass | Alma product team

  3. Improve Alma Job Reports for Failed Record

    It would be extremely helpful if more details were given when there are failed records or records with exceptions on the jobs we run in Alma. Many of the job reports only report the number of failed records. It would be great if the report would provide MMSID information so the we know what records failed.

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

    We are investigating the options for enhancing the job reports as part of a general enhancement to the jobs UX, which will then allow gradually deploying report enhancements to the different jobs in Alma.

  4. Add "item policy" and "temporary location" automatically to predicted issues

    Acquisition librarians want to add automatically the "item policy" and "temporary location" to predicted issues to speed up their work and limit the number of clicks. At this moment the added value of prediction pattern functionality is being restricted by the lack of functionality (parameter setting) …
    Use case: It’s not possible to add the item policy/temporary location as a parameter to continuous pol’s. If issues are created via prediction patterns the item policy/temporary location should be indicated automatically based upon parameter settings on pol level. This would save a lot of time and additional clicks when receiving the issues.…

    492 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)
    Accepted  ·  Dana Moshkovits responded

    When creating a a POL, it will be possible to also define a default item policy and temporary location. This will be used when items are created (by a prediction pattern or manually) on POL or at receive time

  5. Closed Library Management TOU apply to Resource Sharing Request

    Currently, the RS Lending Request item due date does not take into consideration of the library closed days as there is no "Closed Library Due Date Management" option in the Lending Resource Sharing Rule TOU. As a result, the due date may fall on a library closed date where clients are unable to return the item. I have received confirmation from ExLibris (SF354784) that this will need to be an enhancement request rather than a bug fix.

    470 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Planned  ·  8 comments  ·  Resource Sharing  ·  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. New notification letter when expiry date is updated

    When updating the expiry date for items on hold shelf, we miss the opportunity to resend notification letter with the new expiry date. We are aware of the resend notification functionality, but this will not include the new expiry date.

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

    418 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. 'Not Needed After' date should be mandatory on patron physical request form.

    It would be helpful if the 'Not Needed After' date is mandatory on the patron physical request form to improve the requesting process for Patrons when there is a high demand for physical items.

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

    Hi,

    An approach we’ll be looking at is that an optional ‘Last Interest Period’ request policy will, if set, be used to set a default the last interest date (Primo and Alma). This way every request will have a last interest date set by the policy and overridable by the patron.

  9. Add "Search within results" box on a set

    Hello,

    It would be very useful if we had a search box of "Search within results", on a set we created with indication rules.

    Thanks.

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

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

    Additional 10 closed fee statuses will be mapped in a code table. Libraries will be able to change their description. Fees with any of these statuses will be considered closed for all purposes. 


    The same types will be used also for transaction types. 


    When an import from bursar is processed, each fee may optionally include a code of the status to which the fee will change.

  11. Add "Request" as a block option in Block Preferences

    Currently the Block Preferences have Block options to permit Blocks on Loan and Renewals, but it would be good to include Blocks on Requests on these blocks - specifically Patron Physical Item Requests, but conceivably other requests.

    For example is a Patron Limit is defined on Overdues or Recalled overdues, and the limits are exceeded, the relevant Block Preferences are triggered,
    i.e.
    Patron overdue limits has exceeded
    Patron overdue recall limit exceeded

    However, the only options on what patron services blocked are Loan and Renewal.
    Requests should also be added to the options so that overdues can immediately block a…

    366 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. Increase customisation options for the resource sharing request form

    User experience testing that we conducted showed that most users prefer to place resource sharing requests via the resource sharing request form in Primo. Users also expressed frustration with some aspects of the form including the format of the fields. They also expected that the Library could add notices relevant to the resource sharing service to this page.

    The current options for configuring this form do not allow us to meet the expectations of our users. We would like to have more options for customising the page the form is on and the form itself. Specifically we would like :…

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

    We are looking into improvements that can be made to the Primo VE form, such as:

    • Add a custom notice or message to the form
    • Improve the form fields’ responsiveness to the requested format (book/article and physical/digital)
    • Look into ways to enhance the configurability of the look and feel for the form
  13. 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…

    345 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, we are currently working on a design concept for a new form interface option for cataloging, which will make it easier to navigate long fields and subfields - we will take this request into account as part of this design. See our "Form Editing for MARC 21 Bibliographic Records" roadmap plans for more information: https://knowledge.exlibrisgroup.com/Alma/Product_Materials/010Roadmap/Alma_Roadmap_Highlights_(2024-2025)/Metadata_Management#Form_Editing_for_MARC_21_Bibliographic_Records


  14. Ctrl-z/Undo in the Metadata Editor

    Currently, there is no Ctrl-z/Undo function in the Metadata Editor.
    Please add this function.
    Use case:
    A record is in draft mode and the cataloger deletes a field accidentaly, there is no way of bringing it back.
    Or a cataloger works on an exisiting record, makes a lot of changes and only wants to undo the last actions, but not go back to the previous version.

    346 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. Change due date when patron account expiration date reduced

    As a Fulfillment Manager, I would like the due dates of a patron's books to be changed to their account Expiration Date if this is reduced. Eg, if a book is issued to a student for 10 weeks and they withdraw from their course, the original due date remains which can be some weeks after they have left. This can cause confusion for library staff and the patron.

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

    When a loan due date is shortened due to patron expiry, Alma will retain and internal  an indication for that on the loan record. This way when the patron expiry is updated (shortened OR extended) the loan due date will be recalculated using the loan date (i.e. as if the recalculation is happening at loan time). 


    This way, the due date may be extended or shortened according to the new expiry date.

  16. Grace Period only for open days

    Now the unit of measurement for grace period is "days". So even if the library closed on weekend, those days are included to "Grace Period". To give fair advantage of grace period, Alma should apply the grace period excluding library closed.
    For the detailed scenario as I expected, please refer to the attachment.

    Thanks.

    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)
  17. More possibilities for the Alma Color Theme

    In the new UI, libraries can manage branding in Alma by selecting one of 6 basic colors (blue, purple, red, green, brown, orange). This configuration can only be made by a General administrator and is valid for all Alma users. We would like:
    - a larger variety of colors (proposing the 216 web-safe colors would be fine);
    - the possibility for any user to define their own Color Theme: color experience may be very different from one individual to another and giving everyone the possibility the use a convenient color would be appreciated.

    330 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Planned  ·  25 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)
  18. Make 'requester' clickable after 'scan in items' step of handling a request

    It would be convenient if it was possible to click on the requester after the 'scan in items' step when managing a request.

    319 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. 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".

    316 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. Add an order action in the Purchase Request to “Approve and order from the CZ

    Add an order action in the Purchase Request to “Approve and order from the CZ.” Alma would add an alert to the citation and redirect the user to the Community Zone, to the desired portfolio.  The operator will only need to click on the  "Approve and order from the CZ". Currently the only Action is “Approve and Order” which creates a local portfolio not linked to an E-Collection. It’s cumbersome and time consuming to re-link the POL and portfolio to the correct Community Zone record.

    316 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 91 92
  • Don't see your idea?

Feedback and Knowledge Base