...
Item | Desired Outcome | Time | Who | Notes | Decisions | Actions | |
---|---|---|---|---|---|---|---|
1 | Record the meeting | remind Alison to record meeting | 1 | Alison | |||
2 | re-evaluate timeline in light of ucop stats timeline | deadline now in December, alter our internal timeline? | 5 |
| |||
3 | borrowing request lifecycle | results of experiment on ‘statuses borrowing requests go through’ | 30 | Sabrina & Peter | statuses: UCR: after some time, borrowing request no longer appears in Alma; borrowing request status= “deleted” other statuses important to report?? (maybe not…?): “loaned item to patron”; “Physically recieved by library” → not pertinent to AFN requests |
|
|
4 | set requirements for borrowing report | what columns are needed? (eg. institution vs library, fiscal year or other time period …) → what would be ‘look’ of completed report | pic of ‘schedule c’ template: from 2020/21 report: | need: sum per inst of digi & physical ; digi +physical total not needed some insts. need borrower library separate, eg UCI Law; |
| ||
5 | lending stats | ExL hinted that ‘lending stats' may be in ‘fulfillment’ subject area |
| ||||
6 | UCSC ‘guest spot’ | decide yes/no/maybe invite UCSC’s proposed ‘guest spot’ |
| ||||
7 | IZ Analytics Settings | what sorts of settings are impacting Analytics? (as opposed to workflows in Alma IZ) | (if time…) | Anonymization docs from ExL: SUNY guide ('clean up' jobs & ‘remove request' steps may put requests into ‘deleted’ status): | seems to put requests in ‘deleted’ status in Alma → configured per IZ; Alma options to run weekly | ||
8 | Wrap up | Review actions and decisions | 5 | next: Alison show updates to reports in NZ; possibly include brainstorming for library units (UCI Law) | |||
9 | Parking Lot | Capture important topics for future discussion | since ‘standing on head’ would have to be run by SOC (CDL), how would data/report results be distributed? dates (maybe later) → by months for reports | ||||
10 | Total | x/x |
...