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

2 results found

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

    354 votes

    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.

  2. Fine for failing to pick up request

    We would like to have a fine automatically applied when a patron fails to pick up a request. The fine should be applied after the last pick-up date has passed if the request has not been picked up or cancelled. It should be possible to determine for which locations/user groups the fine will be applied.

    209 votes

    A new 'Purged request fee' will be configurable for Hold Request TOU, similar to the one that already exists for booking requests. When the Expired Hold task list is used with one of the 'Reshelve', 'Transit'  or 'Activate Next' functions then the request TOU will be consulted, and a fee will be created accordingly.

  • Don't see your idea?

Feedback and Knowledge Base