...
Recap & action items (5)
Meeting notes
Updates
- check-in alert spreadsheet was shared again - take a look before Wednesday
- May be worth re-evaluating meeting times
Anonymizing patron information
- Need patron group and status for reporting
- Having division (broad) would also be preferred; higher granularity might be a local configuration (but could also make it too easy to identify patrons)
- Expiration date and date enrolled are unnecessary, may make it too easy to identify patron
- Sharon Beltaine would be a useful presence at WOLFcon meeting
- Question of how this is being stored - include patron group and status in loan record, even if it's redundant with link to patron id?
- Further discussion should be done in conjunction with request history & fee/fine history
Claim returned
Questions from Holly
- Yes, need to quickly see if patron has done a lot of claim returneds
- B is the basic option to the question above, D would be preferred (assuming we understand suspended correctly)
Status or flag
- Don't need to show overdue as a status - not currently in OLE
- Could show through styling (if accessible) and calculate for reporting through other means
- If overdue is not a status, need to communicate "overdue" to discovery layer/patron's online account somehow
- Aged to lost is status, but doesn't need to co-exist in status field with Claim returned. If Claim returned is a status, then don't need to preserve the fact that it is aged to lost
- Item process statuses and flags are also potential solutions
- Item process statuses in Aleph allow for a high degree of customization and can apply to items that are loaned
Next meeting and action items
- Review check-in alert spreadsheet and add anything missing to column A
- Emma will pass on responses to Holly, consider other meeting times