2017-09-06 - Consortia SIG Notes

Date

Attendees

Goals

Discussion items

TimeItemWhoNotes
5minHousekeeping

Product Council

  • conference presentations (ER&L suggested)
    • possible topics
      • consortia models/architecture
    • attendees are looking for presentations with concrete ideas that they can take back; at this point, we don't feel we have anything that meets this criteria

RM requirements

  • Harry: everything currently above the line will stay; some items from below may move up
40min

Consortia models

 

Current tenancy model

  • multiple but independent libraries within system
  • consortia functionality would require external software

Shared system

  • one catalog/patrons for all libraries
  • how does a library participate in multiple consortia in this model?
    • might be a distinction between a "consortium" and a "system of libraries"
    • TAMU example
  • do we need to better define consortia and related terms
    • "one-track" and "two-track"
      • two-track - organizationally independent
      • one-track - shared organization/staff
    • "library union" = shared system
  • acquisitions funds - sensitive and can't be shared between libraries
    • hbz - funds are at institutional level rather than consortial level

 

 

 

10minv1 requirements review - planning/next steps deferred
5minWrap-up 

Next steps

  • for next meeting, define "consortia" and "shared/union" - what situations are appropriate for each?
    • it would be good to have a solid draft for the PC meeting on the 14th
    • David Dahl will put together a first draft by noon on Friday; comments/adjustments from all by end of day Monday; discuss at next week's SIG meeting (9/13)
  • future meeting item: review RA extensions - are we covering both "consortia" and "shared" use cases?

Action items

  • David Dahl - draft definitions for "consortia" and "shared" models