2017-06-09 - Consortia SIG Notes

Where to start?

• areas that are fully resourced; user management has a quickly approaching deadlilne
• also "raging conversation" in resource access about location (Resource Access)
  • consortia layer added; not necessarily the same thing as a library location
• resource sharing is another place to focus on

How to provide feedback?

• other SIGs
  • schedule co-meetings for areas of shared interest
• location: contact Andrea Loigman at Duke to schedule a discussion
• where to convene discussions between meetings?
  • co-edit documents on Google Drive
  • Discuss and mailing lists are probably preferred to Slack

Setup location/RA meeting; review User Management requirements

Location conversation

Patron groups (one per patron per tenant) -

• patrons with multiple affiliations; how does system choose "best privileges"

User authentication/authorization

User management - loading patrons versus referencing patrons; check in with Chris Manly.

Resource management model - codex/representation of resources; influences collections, acquisitions; metadata management SIG will/did discuss on Thursdays (convener Lynn Whittenberger). Collecting user stories right now; would be good to contribute some consortial stories. Spreadsheet: https://docs.google.com/spreadsheets/d/1M5eftff8ZHYET5-JFFARUZ-i9n7O6tAQ7mg0G0CkZQ4/edit#gid=379099638

Is spreadsheet of consortial workflows useful?

• examples: 10 authentication systems need to be considered
• Michael Winkler will create a Google Drive folder and link it from wiki

Other conversations

• more infrastructural - reporting, privacy

Suggestion: send note to other SIGs letting them know we're active and request that they reach out

• Martina Tumulla can mention on RM SIG call next Friday
• product council - distinction as a cross-functional SIG; liaison from PC to each SIG; reach out to Sharon Wiles-Young to ensure we maintain connection