Link to recording

Attendees

Time

Item

Who

Notes

Entire meeting

FOLIO ECS Poppy Release Highlights

Dennis Bridges

Poppy is the initial implementation of ECS workflow ; will evolve over time.

Tickets addressed in Poppy:

UXPROD-4092
- Allows a user to login to a system that is connected to more than one tenant
UXPROD-4055
- Allows a user to add affiliations (i.e. permissions) to multiple libraries/tenants
- Users with multiple affiliations can perform work for other/on behalf of other libraries/tenants
- For Poppy, only for 'staff' users (a new 'User type', which only appears in a user record in the UI in an ECS system)
  - User type = patron cannot have multiple tenant affiliations
  - Field was always present in FOLIO, but not required or displayed until Poppy for ECS
UXPROD-4044
- Allows a user to navigate between affiliated tenants with current or active affiliation presented to the user
- Allows context switching for a user without having to open a new FOLIO browser
UXPROD-4059
- Allows a user to create tenants, link the various tenants
UXPROD-4153, UXPROD-4211
- After ECS functionality is enabled, there is a central tenant and in this tenant is the Consortia Manager app
- Allows a user to control settings of all or multiple member tenants from one FOLIO tenant
- Settings can be shared between tenants or individual to a tenant and managed from a single app
UXPROD-4231
- User is able to create, edit, and compare permission sets of all member libraries and view assignments

Separate table in the Poppy release notes that specifically addresses ECS tickets and issues.
Done because not everyone needs or is interested in turning on consortial functionality.
Slide deck from today's presentation is located here

Live Demo of the ECS functionality:

Assigning new permissions for users requires a setting of which tenant to which those permissions apply
'Consortium Manager' app allows access to the Circulation, Data export, Data Import, Inventory, and Users Settings
Can view Data exports and import jobs, but cannot trigger exports or imports as of Poppy
If Settings are managed by a central tenant, i.e. loan types, then those settings which are consortial are only able to be managed by the central office and individual libraries can only add local settings.
Can manage which libraries Settings are seen, what is shared between libraries, etc. – i.e. lots of settings within setting regarding display, management
Inventory now has a 'Shared' and 'Held by' facets for instance records to look at consortial records or only local ones
- Instances have a 'Consortial holdings' accordion
- Shared instances are on the 'Central tenant' and anyone who wants to edit the shared instance must have the appropriate permissions
- Libraries can still have local instances, holdings, and items if they choose; i.e. operate as a single, separate tenant if they want
If permissions & affiliations are properly set-up, a user could catalog an item for another library by creating & editing holdings and item records
Shared records' concept also extends to authority records, as of Poppy
- Additional 'Shared' facet in the MARC authority app for local vs. shared authority records

Questions:

Is 'Central tenant' only for administration? Or is one of the libraries' tenants designated as the 'Central tenant'?
- At the moment, the 'Central tenant' is just another tenant. However, there are some minor restrictions in inventory on the 'Central tenant'. Dennis is open to feedback or ideas on how it would be used as development progresses.
- Development trying to remain flexible and allow the 'Central tenant' be whatever is best to a library/consortium/consortia
Are all of these features going to be released as part of FOLIO's code or is this something unique to EBSCO?
- Part of FOLIO's code

ECS Bugfest:

Starting November 6th
If you want to participate, add your name to this wiki page or you can test unofficially (as it's a public environment).
Unique data set required for a full test.

ECS Poppy release is set for December 15th (due to a delayed bugfest dates and time to fix bugs).

Lucy & Christine are working on the ECS functionality documentation.

None