2017-06-23 - Consortia SIG Notes

UM SIG overview

• single db of users
  • patrons and staff all in one
  • permissions designate ability to perform staff functions
• user metadata identified
  • some configurable by tenant

Current points of discussion

• SSO
  • focuse on Shibboleth integration
  • likely to be a need for first implementers
  • also ability to have local user authentication
  • what happens to SSO users with no privileges (and stumble on FOLIO)
• bulk user import
  • focusing on transactional API to create/modify user in one step
  • assumption that sources of users will vary greatly
  • what happens when record comes in from feed on record that has been manually edited?
    • under discussion; protected fields
  • JSON as data format

Consortial considerations

• metadata field requirements
  • what fields are repeatable?
    • addresses and notes
    • for consortia, patrons need to belong to multiple patron groups
      • single patron record with multiple barcodes use case; this isn't accounted for in FOLIO currently
• are we workign with a one library per tenant model?
  • tenant awareness to define consortial relationships
  • need to not put the responsibility on the user to choose
    • how do you map users from one tenant to another? "consortia broker module" to handle mapping
  • this model might make it easier to represent multiple consortial relationships
    • observed increase in informal consortial relationships/partnerships
  • makes it easier to sever relationships too
• bulk import
  • handle multiple feed sources
  • documentation of required format for FOLIO
  • possible area of app development ("the MarcEdit of user records")
• super user - needs to be able to transcend tenants
  • other staff might need to transcend tenants too
• tenant/library relationship seems like a pretty fundamental thing to figure out

Resource access requirements preview for next meeting

• organization level