2018-01-31 - Consortia SIG Notes

5min

Housekeeping

• FOLIO logo voting: https://www.surveymonkey.com/r/H5WJFXN

All

Madrid developers meeting - should be a summary forthcoming

ALCTS e-forum on collab collection dev - @Paula Sullenger will either send to listserv or to Discuss

 45min

Consortial reporting needs

• review discussion/ideas/needs so far: https://wiki.folio.org/display/CONSORT/Consortial+Reporting+Needs

• what's next?

 All

 What's next

• two options:

  • flesh out report details

  • check in with Reporting SIG on current state of work

    • option #2 - @David Dahl will reach out to Reporting SIG to set up meeting

Report sharing

• added as functional need to reporting needs page

What reporting tools are planned for FOLIO - custom-built or existing product

• https://docs.google.com/spreadsheets/d/1ijqlD0AVlB11ZXtRSUGiAgfqE7LEkDL0iC6IgVqoV6g/edit#gid=0

10min

Wrap-up/planning

All

Where can the SIG make an impact on the project?

• cross SIG communication - list being set up for POs and SIG conveners (at least, might not be restricted)

• consortia are asking when features will be available

  • hard to say at this point; focus of development is single library setup

• can we prioritize the categories of consortial services? Is there a category that makes sense to start with?

  • resource sharing meeting in May - might be a good opportunity for our input

• **lots of discussion about representation of consortia in FOLIO (i.e. shared tenant versus multi-tenant)

  • need to be able to share data in a modular way - sometimes only certain pieces of data with specific libraries (or even an individual staff person)

  • haven't talked about libraries with multiple consortial relationships recently

Next week - continue Infrastructure/Systems discussion (unless we can schedule a joint meeting with Reporting SIG)

• @David Dahl will put up a Discuss post to get ideas