| 40 | Discussion with Dennis about mod-consortia |
| - Is there a timeline for the app?
- 2 modules: mod-consortia and ui-consortia
- His team is mostly working on the consortia manager and technically, it's just begun
- Team had been developing functionality for the Poppy release, which has been extended until November
- First iteration in Poppy will be focused on managing reference data
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-4153 |
|---|
|
& | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-4211 |
|---|
|
- Feature which describes which areas will be manageable in the consortia manager app
- Describes ability to save a term on behalf of a member library and share terms between all libraries
- Question: Can you apply settings to a subset of libraries? Or is it all or one?
- Yes; when you enter the module, you set which members you will be managing and a header follows you to communicate that following actions are on behalf of those libraries
- Ability to modify settings is dependent on how the user/manager permissions/profile is configured
- Intended to be flexible to allow for variation in management of consortium
- Allows a manager to copy settings from one library to another
- The first iteration will not have the ability to add or delete members
- Homework for the SIG: identifying use cases for when consortium might manage memberships (addition, deletions, merges, etc.)
- Note: final name is not likely to be 'Consortium Manager'
- There is already a product commercially available called 'Consortia Manager'; need to disambiguate
- Question: Vision of who is doing the management? Central system office? Individual libraries?
- Highest priority is to create functionality for central office management, but trying to create a module flexible enough to allow multiple scenarios
- Permissions play a key role in who can access app and manage various settings
- Question that the development team is constantly keeping in mind as they move forward
- Homework for the SIG: use cases on who will be doing management
- Question: Does this tool lend itself towards a multi-tenant or single-tenant system?
- Multi-tenant; allows management of systems across tenants
- Single tenants don't differentiate some reference data between libraries (i.e. closing purchase order reasons, etc.)
- Comment: new module changes the discussion for libraries considering FOLIO and whether they need to be single or multi-tenant
- While intended to support multi-tenant situations, changes to a single-tenant could be forthcoming due to the structure needed to support this work
- Question: Does this new module have any impact on ReShare, circulation?
- This module is not initially intended to manage resource sharing
- Tool could be used to manage circulation rules of libraries, but it doesn't manage the workflow to share materials between libraries (on separate tenants)
- What further developments are planned?
- ECS Dashboard outlines what is coming up in the next release
- Not working on at the moment; likely impacted by changes to Poppy release
- WOLFCon : Do we have plans?
- Not at the moment
- Corrie & Noah will work with Dennis over Slack; he is interested in collaborating
|