Versions Compared

Version Old Version 11 New Version Current
Changes made by

Deb Lamb

Andrea Loigman

Saved on

Key

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

Date

...

Kimie Kester

Holly Mistlebauer

mey


Discussion tems

TimeItemWhoDescriptionGoals
5minHousekeeping

Andrea Loigman



20minRequest whitelist

Cate Boerema (Deactivated)


-Review wireframe for whitelist configuration and get initial feedback

Q2 2019 Requests Discussions PPT (with this topic and more): https://docs.google.com/presentation/d/1hNYBxUdy3pGKKpo5BkY7bJFfBEVdEG1idCecY1xVwko/edit?usp=sharing
15minAnonymized loansEmma Boettcher
Given fields on user record that are currently in place, how should this appear?
Given proposed fields on user record (statistical code/affiliation, custom fields), to what extent are these fields helpful to show on an anonymized loan (as opposed to just in reporting)
20minNotice /item history

Darcy Branchini and Cate Boerema (Deactivated)

Continuation of conversation around patron notice reportsDetermine needs for patron and item notification history.

...

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Comments

e.g. loans, fees/finesNamee.g. Q4 2018, Q1 2019Clearly stated decision
Requests

Cate Boerema (Deactivated)

Unknown

Reviewed wireframes for configurable whitelist:

  • Decided wireframes makes sense 
  • Some questioned priority and felt they might just enable all kinds of requests for all item states and then use request policies to limit what can be done
  • Others felt this would be useful and is better than what they have today
  • A few people thought it would be nice to be able to do this configuration by location or library (as opposed to by tenant)
  • But people also felt that different configurations with a single tenant invited a great deal of complexity for the system and patrons 
  • In the end we agreed by tenant made sense
RequestsCate Boerema (Deactivated)Q2 2019

Revisited decision about which requests should display in the loan action history table:

  • In light of the fact that we are designing a "circ log" with detailed info about requests on items by patrons, do we really need to display all requests in the loan action history? 
    • This is complex development
    • Developers say it would be much easier to fix the bug if we just showed requests that affect due date
  • SIG would still prefer to see all, as requests that don't change the due date can also impact the loan.  Holds may make it impossible to renew a loan, for example
  • BUT SIG agreed that if we had the circ log easily accessible and also a link to the request queue, it would be fine

LoansEmma BoettcherQ2 2019
  • Of the fields currently on an anonymized loan, display some text where a name has been scrubbed, and display the patron group always
  • Of the proposed user record fields to retain on an anonymized loan (statistical codes, custom fields such as department), show, but having them one click away is also fine
  • Further question: should what fields are retained on loans also be included in anonymization settings? 

...