2017-08-02 - Consortia SIG Notes

2017-08-02 - Consortia SIG Notes

Date

Aug 2, 2017

Attendees

  • @David Dahl

  • @Hkaplanian

  • @Kirstin Kemner-Heek

  • @Martina Tumulla

  • @Michael Winkler

  • @Paula Sullenger

  • @Tania Hewes

Goals

  • Finish review of Resource Access v1 requirements

Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes

5min

Housekeeping

  • volunteer to provide weekly OLE report updates

  • Harry will convene 8/9 meeting

David

David will continue to provide updates.

Most attendees are unavailable, so there will not be a meeting on 8/9.

10min

Location hierarchy (https://drive.google.com/open?id=1jsBik8wOqt6ViJzYdtRy7yY2FGI_z2cSIdEyQLBlzzQ)

  • are four levels/layers sufficient? RA is awaiting our approval/thoughts.

All

Can multiple institutions be included? This would be necessary for consortial models #2-#4.

  • Would be good to flesh this out

  • Would it work if consortia = Institution?

    • might not need to indicate consortia; consortia could be equal to the shared system/instance/tenant

  • use case - Kirstin: GBV - Hanover hosts system for all libraries; libraries are completely independent

    • some libraries with different systems but shared user data

    • need to be able to circulate directly from another library

    • might be need to "tag" subsets of libraries within a consortia (e.g. these are the academics, etc.)

Borrowing privileges

We need to develop a document of use cases

35min

Resource Access v1 requirements review

All

  • postpone discussion until 8/16, add comments to requirements spreadsheet between now and next week (put initials next to comments)

10min

wrap-up and future agenda planning

All

No meeting next week; next meeting 8/16 - work on scenarios and review of RA requirements between now and then

Continue looking at requirements

  • Acquisitions/resource management/ERM

Reporting

  • look at reporting SIG doc

Harry is releasing a survey of "below the line" requirements - might be useful in determining our future work

Action items

@David Dahl will start a Google Doc to record scenarios