Attendees
Corrie Hutchinson (Unlicensed)Bernd Oberknapp Noah BrubakerMartina Tumulla Lloyd ChittendenLucy Harrison Hkaplanian Jaime Taylor Christine Tobias Elena OMalley
Discussion items
| Time | Item | Who | Notes |
|---|
| 4 | Announcements |
| - Corrie : Ian Ibbotson will be at the July 25th meeting to discussion GALILEO & MOBIUS ReShare work
- Lucy : GALILEO is still negotiating their contract
|
| 7 | Continuation of discussion on feedback for Dennis re: mod-consortia |
| - Consortia SIG Admin Tool / Admin Role Function List spreadsheet
- Discussion of which entries might apply to the mod-consortia app
- General understanding is that mod-consortia is to allow central management of settings; does not directly involve user or inventory records
- Do lines 6-8 apply? Can we provide more information?
- Any use cases we can think of address these?
- Do we throw everything we can think of at Dennis? Or wait for more information from Dennis in order to be more targeted?
- Spreadsheet originally created to gather broader concepts and develop use cases further along in the process
- Does mod-consortia incorporate shadow inventory records?
- Is the setting to enable this functionality in mod-consortia because it is a setting?
- 2023-06-29+Metadata+Management+Meeting+notes
- Meeting where shared record functionality was presented
- Did this grow out of a desire for a central database to manage authority records?
- What is in scope or out of scope in relation to the work that Dennis and his team are doing?
- Discussion on how best to balance SIG feedback with priorities of the ECS team
- Are all settings able to be managed via mod-consortia?
- Harry :
- Yes, but it might be limited at first while workflows are developed
- Changes to mod-consortia and other ECS apps impact other third-party apps that will need to be modified to work with the new ECS apps & functions
- Would expect that almost any app could be affected by the new consortial functionality being, including ERM
- Roadmap for ECS?
- Harry :
- Yes, this can be shared with the SIG in the future
- Will the system be able to ignore the consortial functions if a library wants?
- Harry :
- Yes. EBSCO is expecting that the consortial needs will be a part, not all of FOLIO
- FOLIO will allow libraries to turn off/on consortial functionality
- In general, the goal is to keep the UI of FOLIO as similar for consortia as it is for individual libraries; keep the changes minor
- New work does not create a 'fork' in the code
- Features will also be useful by large library systems not technically categorized as a 'consortium'; hoping and expecting applications to apply beyond a consortium
- Would ECS team be interested in knowing which apps the SIG is most interested in managing centrally?
- Harry : let me check with Dennis and get back to you
- Hard to develop apps in isolation
- For example: shared cataloging & circulation across tenants and how these workflows impact settings & configurations of centrally managed tenants are likely to be first the be rolled out
- Expect the overall process to be an evolution that continues after the first libraries implement the new ECS functions
- Discussion on rights and permissions of users in a centrally managed system
- Harry :
- Will take our questions about priorities to Dennis ; let us know which use cases would be highest priorities
|
| 40 | WOLFCon sessions related to consortial-work |
| - Dennis and other ECS team members submitted sessions : concepts, developments, etc. take time and are complicated
- As of today, the schedule is only preliminary
- Don't know yet which sessions are available virtually
|
Action items