For #2 - get more detail about time commitments, etc. for PO role (Paula Sullenger will bring up with the exec group and email any additional details)
For #1 -
- options
- working from Consortial Services Framework, extract individual services/functions into visioning "white papers"
- include links to existing, relevant JIRA tickets
- what about reporting? functional needs for reporting might be an additional area to "envision"
- general agreement that this is the best way to proceed; other areas may come up as we start our work
- prioritizing consortial services
- "Infrastructure" is a foundational service upon which other services are dependent; David Dahl thinks it makes sense to start there (no strong objections)
- "Resource Sharing" is an area of functionality that libraries/consortia expect to have within their shared ILS and probably makes sense to tackle after "Infrastructure". This work might be somewhat clouded by other resource sharing initiatives (e.g. Reshare, etc.) but is probably still worth envisioning.
- Buying Club, Coordinated Collections, and Shared Workflows are more aspirational areas of functionality