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. Create Fines and Fees Report: add transaction operator per row

    For the "Create Fines and Fees Report" feature added in August 2013, please add the following feature:

    Our auditor requires that the Transaction Operator/Handler ("Accepted By" information) be identified and currently that information is not in the report.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Letter sent to patron when fine waived

    Although there is a letter when a fine is paid, we'd like a letter that would automatically be sent when a patron's fine is waived.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Fines and Fees report Excel output is dumb

    Okay, in what universe does having the Fines and Fees report output the money amounts as text make any sense?

    It just adds extra steps if you want to work with it - first convert that text back into numbers, then format it as currency.

    It should be exported that way to begin with.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Allow Fines API to return closed fees in the /users/<userID>/fees/<feeID> endpoint

    Something I have noticed is that the fines API has strange behavior when it comes to returning data. /users/<userID>/fees will return only fines for a certain status supplied in the query params, which defaults to active. This makes sense and is fine, but what doesn't make sense is that /users/<userID>/fees/<feeID> doesn't return closed (paid) fees. It returns this error message
    {

    &quot;errorsExist&quot;: true,
    
    &quot;errorList&quot;: {
    &quot;error&quot;: [
    {
    &quot;errorCode&quot;: &quot;401873&quot;,
    &quot;errorMessage&quot;: &quot;Request failed: API does not support closed fees.&quot;,
    &quot;trackingId&quot;: &quot;E01-1412050816-2AZKJ-AWAE514295771&quot;
    }
    ]
    },
    &quot;result&quot;: null

    }

    This is fairly strange, I would have expected for the fine to still…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. View closed fines- order by transaction date

    When answering fines queries it would be useful to be able to arrange the 'closed' fines in the order in which they were resolved, in order to provide a chronological explanation.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Option of fine free returns

    Turns off fine accrual or loan suspensions when overdue items are returned to the library.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Progressive overdue fine calculation in Fulfillment

    The existing overdue fine settings in Alma Term of Use (TOU) can only allow library to set a 'flat' rate for fine. (e.g. $1 per day for the whole overdue period). It would be great if Alma can allow progressive overdue fine setting (e.g. $1 per first 3 days and $2 thereafter).

    This suggestion allows greater flexibility in fine setting and also encourage patrons to return overdue items earlier.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Fine and Fees notification email

    We would like the ability for a user to be notified and sent an email of the fees that they have when they come in to the library. This is done currently through a job that runs daily or weekly, but we also want the ability to send it to just one person.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. The "Fines and Fees Report" under Fulfillment

    Put in a date range too far back and "Fines and Fees" informs you that "From date is limited to 7 days before the current date."

    Except...

    Say it's January 13th. Well, Last time I checked, January 6th is seven days before January 13th...

    But in reality, "Fines and Fees" will only let you go back to January 7th, because for some reason it assumes the day you're running it on is also part of that seven days.

    That's just dumb.

    Either the warning message needs to be more accurate...or it needs to actually go back seven days. I'd prefer…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Being able to locate fines or fees owed on an item from the item record.

    This would be helpful for times when returned materials generate overdue fines that require removal or adjustment and when the staff person navigates away from the screen, the session is interrupted, or other circumstance when you need to verify if a particular item has a fine or fee attached to it.

    (This was a very useful feature in Voyager.)

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base