Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Reasoning

Link to supporting materials

Comments

e.g. loans, fees/finesNamee.g. Q4 2018, Q1 2019Clearly stated decision
  • Because...
  • Because...
e.g. mock-up, JIRA issue




























Notes

  1. Darcy presents current status of patron notices, up next: combined overdue and recall
    Do we need different scenarios for "overdue then recalled" and "recalled then overdue"?
    David: what happens to the due date when a recalled item is already overdue?
    When do the fines switch to recall fines? Do patrons get a recall notice when item is already overdue? Cate will test it and report back
    Andrea: recall notice should be different
    Aged to lost notices:
    options when a notice should be sent are: when item status changes, reminder notices, when charging and adjusting fees
    do overdue notices stop or continue after aged to lost? Holly and Cheryl say they stop
    reminder notices should be possible in case the billing happens some time after aged to lost
    aged to lost items can be renewed by staff only - does that cancel the open charge automatically?
    the Lost item fee will be cancelled as long as the item is renewed before the No fees/fines shall be refunded if a lost item is returned more than <X intervals> late setting in the Lost Item Fee Policy
    The Lost item processing fee will be cancelled if the If lost item returned, remove lost item processing fee setting is 'Yes' and the item is renewed before the No fees/fines shall be refunded if a lost item is returned more than <X intervals> late setting in the Lost Item Fee Policy
    when an item is returned its status goes to available (causing a check-in notice if set up)
    all patron notice features:
    Jira Legacy
    serverSystem JiraJIRA
    jqlQueryfilter=11571
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
  2. Emma on permission escalation
    needed for every permission in Folio or just some areas/type of actions?
    possible scenarios for when this is needed:
    financial transactions
    student workers on special projects
    single overrides (renewal, checkout)
    does the supervisor override allow just one action or several? it's different in current systems, complicated with SSO
    most critical in single loans actions (that need to be done immediatly, like passing checkout or renewal blocks), but also needed for requests (reordering request queues) and fees/fines (waiving)