2017-10-18 - Consortia SIG Notes

2017-10-18 - Consortia SIG Notes

Date

Oct 18, 2017

Attendees

  • @David Dahl

  • @Peter Murray

  • Judy Cobb 

  • Theda Schwing

  • Steve Walker

  • @Marc Keepper

  • @Paula Sullenger

Goals

  • develop consortial needs matrix; determine use of 'categories'

Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes

5min

Housekeeping

David

10min 

Product Council meeting recap 

David and others in attendance

  •  roadmap has been updated

    • some "below the line" features have been moved "above the line"

    • "the line" represents features that are needed for v1

    • important to emphasize that this is a development roadmap; discussions/details about certain features may be necessary prior to the timeline indicated on the roadmap

    • Consortia SIG can use this document to help guide/prioritize discussions

40min

Consortial needs matrix

All

Categories

  • continuation of last week's discussion

    • attendee consensus that mapping categories to consortial services is a good approach that will resonate with consortia

    • might be interesting to create something similar to Drupal distributions - packaged versions of FOLIO that include core code plus add-on apps needed for consortial functionality

  • what does consortial administration represent?

    • possibly things like adding/removing members, defining consortial relationships, etc.

  • reporting/statistics

    • Q: should this be a category or is it a need that fits several categories? A: probably a need(s)

    • consortial wide statistics are important

    • several new needs were added to the matrix

      • libraries within a consortia need to be able to assess the value they are receiving from their consortial membership, as well as assess what they are contributing to the consortium

      • consortia need data/statistics/reporting to evaluate usage of consortial services in order to demonstrate value, refine services, etc.

Defining consortial relationships

  • so far the needs matrix doesn't represent any of our discussions about libraries having multiple consortial relationships; this was added to the spreadsheet

  • also, consortia sometimes have relationships with other consortia, so this needs to be defined not only at the individual library level but also at the consortial level

5min

Wrap-up/planning

All

For next time,

  • review categories and make sure services provided by your consortia fit within current categories (add additional categories if not)

  • add additional needs to matrix

Action items