2017-07-26 - Consortia SIG Notes

Housekeeping

• convener for 8/9 meeting
• new meeting link: https://zoom.us/j/816262954
• profile list for Consortia SIG

• David will be out the week of 8/5. David will send an email to the list for a volunteer to convene the 8/9 meeting; looks like a few other people will be out as well.
• Meeting link has been updated; calendar invites, SIG pages, etc. have been updated to reflect this
• Peter has proposed a method for displaying SIG membership dynamically: https://discuss.folio.org/t/adding-sig-membership-to-wiki-user-profile-and-dynamically-generating-sig-member-lists/1039. Members can go ahead and indicate membership in their profile. There are a few outstanding questions before Peter adds this to SIG workspaces.

Locations, collections, and consortia (oh my!)

• Locations modeling slides from Vince: https://docs.google.com/presentation/d/1jsBik8wOqt6ViJzYdtRy7yY2FGI_z2cSIdEyQLBlzzQ/edit?usp=sharing
• how does the emerging location/collection model map to our consortial models, and are those consortial models being considered in system development? (If not, how do we formalize these so that they are a consideration?) Identified consortial models are shown here: 2017-03-31 Meeting notes

• probably doesn't have much impact on #1. gets more interesting starting with #2. utilize software to create boundaries where needed; could be particularly useful for fund management
• consortial relationships don't always align with funding sources
• how are seven reasons for consortia existence impacted by model? do we need use cases for consortial services?
• need to send location information as part of API
  • example: approval plans
  • ordering of item isn't necessarily tied to location/owning library; is important for shelf-ready, though
• what controls ability to create tenants? none at this point, but it is planned and being worked on
• use case: mini-research collaborations that need a library system