2018-01-24 - Consortia SIG Notes
- David Dahl
Owned by David Dahl
Date
Attendees
Goals
- Define reporting needs around shared workflows
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 5min | Housekeeping
| All | |
| 45min | Identify reporting needs for "Shared Workflows"
| All | Reporting need: Comparison config reports for central staff - or member to member for mapping purposes or templates Templates Sharing - recovery of process -copy procedures -workflow processing --help with trouble shooting - shared queries (canned or created on fly but shareable) Shared work activity report-- example of cataloging - breakdown by person, library - what work is being assigned to other libraries /person and level of completeness -seeing how each local practice might be different than group and how it ripples through the system - so changes or how group work needs to adjust. -3rd party connections uptime and status - last time success - activity of connection - monitoring - Long over due items for all members for a given time frame- checked in or found on shelf or checked in at patron library, but not at owning library yet -shared list --- if bills need to be generated off the list it would be auto .. transit reports send exports to the discovery layer so that marc records show show in discovery show all resources in different facets - when all can access - or only members that are a part of that package- etc Reports on who/ members are mapped or using what vendors- create KB collections - encoding license - and share it out - seeing usage on these type of reports Where does the division of labor happen...track the process status ( purchase, delivery, cataloging, received, and so on - where the item is, but also library/ people that are working on it ( owning library - processing library - next step, time in process) shared collection dev - retention ( come back to this) |
| 10min | Wrap-up/next steps | All |