2018-09-13 Resource Access Meeting Notes
Date
Sep 13, 2018
Attendees
@Andrea Loigman
@Anya
@Cheryl Malmborg
@Joanne Leary
@Tania Hewes
@David Larsen
@Emma Boettcher
@Kimie Kester
@David Bottorff
@Wendy Wilcox
@Cate Boerema (Deactivated)
@Rameka Barnes
@Sharon Wiles-Young
Goals
Discussion items
Time | Item | Who | Notes |
|---|---|---|---|
5min | Housekeeping | @Andrea Loigman |
|
45min | Data elements review (con't) | @Emma Boettcher |
|
5min | Active loan policy changes | @Schwill, Carsten |
|
Action items
Comments
Sep 19, 2018
Notes
Further discussion of loan gaps
-need to store patron group, and custom fields like statistical category and patron department
-some patron data such as deceased flag does not need to be stored in loan;can be referenced from user module
Custom fields need to be useful beyond statistics. Potentially they could be used in loan rules, the workflow engine, determining pickup locations, etc. Folio needs to map custom fields so they can affect code execution
Tracking loan actions
-currently folio keeps all versions of a loan as it is updated; this may change to an audit trail
-what needs to be tracked in the change tracker PO's will need to tell developers for each module
RA examples: loan policy changes, patron group change, item-related changes, due dates, renewal dates (not all need to be displayed in the loan action display), overrides(staff who overrode, not original operator)