Versions Compared

Key

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

Date

Attendees

...

Functional Area

Product Owner

Decision Reached

Reasoning

Link to Supporting Materials

Comments

e.g. loans, fees/finesReNameClearly stated decision
  • Because...
  • Because...
e.g. mock-up, JIRA issue
RequestsCate Boerema (Deactivated)"Pickup location" in Request record can be renamed "Pick up service point" for clarity
  • Because the pickup location menu actually contains service points - the developers were quite confused by this
  • While "pickup service point" is not language people would like to expose to patrons, they can easily relabel in patron systems


RequestsCate Boerema (Deactivated)Rows 3 - 7 of this document are approved
Item status use casesNeed follow up discussions on what data is captured when an item is checked in and how that data displays (should be on the item record somewhere)
RequestsCate Boerema (Deactivated)Rows 9 - 13 of the same document are approved
Item status use cases
  • Need follow up discussion on what "Needed for" values should be triggered by recalls (and holds, for that matter)
  • Need follow up discussion on how the system knows when and how much to truncate due dates for recalls
LoansEmma BoettcherMockup approved (first pass)
  • Adequately addresses scenarios from most of the SIG & first implementer (Chalmers)

Does not adequately address scenario of needing to assign different due dates to non-renewable items, but will address later

Notes