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
Service PointsCate Boerema (Deactivated)Unknown
  • Should develop a feature to inactivate service points similar to the inactivate locations feature
  • Should have the ability to generate reports showing all the places this service point is used. Data warehouse reports would be okay for this purpose but we need to be sure there is good documentation outlining all the places where service points can be used (e.g. locations, users, requests etc)
  • Service points have so many associations with valuable data you definitely don't want to delete unless they haven't been used anywhere
  • The location inactivation is a model that works well
  • Data warehouse reports will give you a sense of all the cleanup you want to do
  • Deprecating a service point happens infrequently enough that you don't need a fancy in-app report with the ability to take action
  • But we definitely need documentation on where SPs are used so ppl know which kinds of data warehouse reports to generate

  • It was also noted that, when we integrate the locations into the circ rules, we need to define what should happen when you check out or renew something that has an inactive location







Notes