Outcome: share information about planning and how to submit ideas
Jesse is serving as the OLF WOLFCon Coordinator. WOLFcon is August 22-24 at the University of Chicago. Early-bird rate of $400 through June 15. After that, $450. The email you get from registration will have suggestions for hotels including discount codes for WOLFcon attendees.
New form for WOLFCon Submissions. FOLIO makes up many of the sessions...feel free to start using this form to announce the sessions you are planning. There will be Council meetings outside the WOLFcon dates. SIGs can have working group meetings; use the form for planning those.
FOLIO WOLFCon Coordination Group:
Deadline for initial submissions: June 5
From Tod: the earlier we find out about the meetings before and after the main WOLFcon dates, the easier it will be to find space for planning. PC is planning on having meetings before and after.
The planning committee is planning for between 200 and 250 attendees. (There were about 170 in-person and 200 virtual attendees in Germany for last year's conference.)
Desired Outcome: make a decision about the inclusion of new consortia functionality
"Enhanced Consortia Support (ECS) Functional Overview for Product Council" for Poppy Release. Some of the modules are further enough along in development to be shown.
All of this work is covered in Jira using
For Poppy, the bulk of the work is in login and affiliations (meaning users connecting to more than one tenant—as a staff user, I have permissions in one or more tenants). The user login is a single entry point, and the user's primary affiliation becomes their active affiliation on login. Users with more than one affiliation can switch their active affiliation...changing the context of their experience. The Users app has a new "Affiliations" accordion (which won't appear unless the consortia modules are installed). "User Permissions" also changes to show which permissions a user has for each affiliation.
Changing affiliations explained: when a user is affiliated with a tenant, a "shadow user" is created...a different kind of user that will give some control over what data is shown to an affiliate user. Descriptive data is copied, but there is local context data within a tenant. There is discussion happening in TC about this:
Local admin staff with the appropriate permissions are able to configure system settings for their libraries. Consortium settings appear in the Settings app ONLY for users with the appropriate permissions and only when a user is in the consortia tenant; this will list the member tenant names and codes. (At the moment, creating the relations between tenants is something that the hosting provider needs to do; the user interface for that will come later.) A Consortium Manager app will allow for configuration changes for multiple members at one time. In this app, the form compares values from the selected members; settings can then be applied to member tenants (with a confirmation dialog box).
For the future: policies and templates can be saved to one or more members or saved records are copied to members so that members can edit locally.
Does the existence of the Consortia Settings app mean that there are now new variations of the flower releases?
Release Management Stakeholder for the new Critical Service Patch
The Support SIG also has questions about representatives in the group (see Slack). (If there is someone from the Support SIG, the Support SIG members thought it should be from a library and not from a service provider.) Should there also be representation from self-hosted institutions? (Also noting that Holly's seat was not filled after she retired from the project.)
The group also discussed the level of testing of service patches before they are released (so they don't introduce new bugs).
The next meeting is on the 15th, but there isn't information posted in the wiki about this.
|5 min||Agenda items for the future||Data Import discussion coming on May 26?|