Skip to content

Sarah Marchman

My feedback

4 results found

  1. 216 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 colleagues,

    Thanks you for suggesting this idea.

    After reading it carefully, my understanding is that the need is for a new “entity” which will serve as a “bridge” between encumbrance and expenditure. This bridge will be named “Pending invoices”.

    Any POL which is invoiced will be disencumbered and the amount will be added to the “pending invoices balance”. When an invoice is approved, the amount should be reduced from the “pending invoices balance” and added as an expenditure.

    1. Is this understanding correct?
    2. Do you think that the definition of using this "bridge" should be in institution level, or might be different from invoice to invoice?

    Please note that this is a complicated addition. We will need to define the behavior in rollover, and in any place that changes balances etc.

    Thanks for your collaboration,

    Tamar Fuches

    Alma product team

    An error occurred while saving the comment
    Sarah Marchman commented  · 

    Thank you for following up, Tamar. I think your understanding of the request is correct and what you describe is what our library would want (a new "pending invoice balance" amount that removes the encumbrance according to the rules and moves to an expenditure after invoice approval). I think keeping a transaction as an encumbrance on an "in review" invoice would not be helpful for us; that would still mean these transactions are hard for us to understand.

    Sarah Marchman supported this idea  · 
  2. 25 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)
    Sarah Marchman supported this idea  · 
  3. 213 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 Elizabeth, Katie, and everyone,

    Thanks so much for sharing this idea!

    From what I understand, it includes two main parts:

    1. Allowing institutions to edit the list of values in various fields, with a specific example being the “Implemented Authorization Method” field.
    2. Adding more fields and making them reportable in Analytics, along with a request for a flexible mechanism to support this.

    Regarding the second point — adding a flexible mechanism is quite a complex change and could impact the timeline.

    If you can point out around three specific fields that are most important to add first, it might be easier.

    Looking forward to hearing your thoughts!

    Thanks again,

    Tamar

    Sarah Marchman supported this idea  · 
  4. 33 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)
    Sarah Marchman supported this idea  ·