Page tree
Skip to end of metadata
Go to start of metadata



Discussion tems


20minDisabling and deleting service pointsCate BoeremaWhat if a SP is created by accident or is no longer in use? Deleting SPs is challenging because of the various dependencies. Should we inactivate instead? What's the expected behavior in both cases for locations, requests and loans that use the SP?
15minCall numbers on staff slips
What parts of the call number should be displayed on the staff slip? And if it just should be concatenated? 
10minPartials for patron notices.Darcy Branchini

Partials are snippets of information, such as a header, footer, signature and/or location or contact information, that would then become tokens for use in the templates.

Which partials are needed?

Meeting Outcomes

Functional Area

Product Owner

Planned Release (if known)

Decision Reached


Link to Supporting Materials


e.g. loans, fees/finesNamee.g. Q4 2018, Q1 2019Clearly stated decision
  • Because...
  • Because...
e.g. mock-up, JIRA issue
Service PointsCate BoeremaUnknown
  • 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


1 Comment

  1. Cate – disabling service points

    Inactivation necessary for v1; delete only if service point never used

    See Cate's notes on decisions and reasoning

    Darcy - call numbers on staff slips

    What components are needed – consensus potentially all components (prefix,call3,suffix,enumeration) might be needed

    Should they be concatenated? Would be OK on individually printed slips; lists need to be sortable by components

    Different slips need to be individually configurable

    Darcy - partials for patron notices Reusable snippets of information that can be used as tokens in notice templates

    Examples; header ,footer, contact information Could be mixed and matched in different notices

    A good idea, needs more definition  Eventually it would be useful to have system logic to tie partials to specific notices rather than having to repeat typing in each notice

    It would also be nice to have a batch update capability.  For instance, substitute footer2 for footer1 in all notices.-