| | | |
|---|
1 min | Scribe | All | @Jenn Colt is next, followed by @Florian Gleixner Reminder: Please copy/paste the Zoom chat into the notes. If you miss it, this is saved along with the meeting recording, but having it here has benefits. |
25 min | SHL Topics | All | SHL has provided their discussion questions in this document: Notes: Permissions question: UI delay in getting all permissions added when trying to add a lot of them at once can lead to only partial permissions being assigned. Permission sets are a common way to deal with this. Jakub from the core team or the user management sig. will the architectural changes impact this at all? With those changes it is a move away from permissions to roles so it could be less of a problem because roles group permissions. Being able to contribute dev resources would help it gone done sooner.Suggested contacts for more discussion: Amelia Sutton (Users app, mod-user-import) Khalilah Gambrell (Local password management, Create/Reset passwords)
Secondary hierarchy menu: Currently have a custom secondary menu using the <Recording> component. FOLIO usually puts all the apps across the top bar, the secondary function menu allows for more apps and links within those app. Being able to customize a set of links in this way seems valuable to cut down on clicking for users. Not sure it has been explored anywhere else in the community. Hotkeys achieve a somewhat similar behavior but not exactly the same. Can share source code for the customization. Editors: Right now only MARC is available. BIBFRAME should be coming later in the year. Have heard requests for DC editor but no work yet. BF should be in Ransoms, based on Marva editor. IndexData also doing some BF work. Chinese public libraries needed a custom MARC editor in FOLIO. Custom editor uses keys and avoids having to do a lot of work with the mouse, allows z39.50 search on one panel in the editor and the ability to copy over fields to your new record on the other panel. @Jeremy Huff has notes on the remaining questions and will post them in Slack for further discussion on questions we didn't get to.
|
25 min | NLA Topics | All | The NLA has proposed the following topics: A discussion on how / if the security model might change with the introduction of Keycloak. For example, will non SSO accounts within FOLIO which currently cannot have 2FA, is this likely to be addressed by introducing Keycloak ... this is becoming an issue for us raised by our cybersecurity team Will the introduction of Kong change anything in relation to external "apps" that we write that make use of OKAPI? We have a small eco-system of these now ... I know other libraries have these "helper" apps too that rely on using OKAPI ... will this change? Considering the topic of the hour .... anything being done in the AI space within FOLIO land? Not even sure if this is relevant.
Notes: Security model/authentication: Excited about key cloak and role based control. Challenge with 2FA. SSO login is good but non-SSO isn't 2FA. In keycloak it is a configuration to set up 2FA. Using keycloak in other applications and could use it for 2FA there, more complex than clicking a few buttons. It would be a big plus for NLA to have this adopted. Being able to have 2 factor is important. Can still have local accounts with Keycloak. Much better to use well adopted auth solution. Eureka has role based concept established. Another Eureka preview will be set up now that Q has been released. @Craig McNally can provide more information, NLA security team would like to see. It does piggy back on existing perms so if those change, things will have to change in Keycloak. More discussion about practice could help. See Folio Eureka Platform Overview as well
Introduction of Kong for external apps that are accessing Okapi: For clients, API isn't supposed to change. NLA has serials check in app for instance. Nothing should change with Eureka in this regard, have kept close eye on compatibility to make it as easy as possible to adopt. Still using same request headers. Only real difference is the request goes to Kong instead of Okapi. Will auth change? No have alternate implementation of login interface. So instead of talking to mod-authtoken, it is a drop in replacement, contracts are the same, including with RTR.
AI: Some talks at wolfcon. Libraries exploring AI but not necessarily within FOLIO. NLA also doing AI work outside of FOLIO.
|
10 min | Future Meetings in alternate time slots | All | Feedback on this meeting time and format Other potential meeting times that are more European Friendly Cadence of alternate time slot meetings
Notes: For NLA the time is good Maybe monthly or every two months for NLA How to also accommodate Europe, alternate between slots TC will have to discuss, maybe alternate a monthly timeslot Time also good for SHL
|
| Zoom Chat | | 20:14:31 From Huff, Jeremy T to Everyone:
Amelia Sutton (Users app, mod-user-import)
Khalilah Gambrell (Local password management, Create/Reset passwords)
20:26:58 From Craig McNally to Everyone:
Regarding hotkeys, here are the applicable guidelines we have documented: https://ux.folio.org/docs/guidelines/accessibility/front-end-guidelines/ (See #4)
20:35:43 From Maccabee Levine to Everyone:
Thank you SHL for the demos!
20:41:00 From Gang Zhou | SHL to Everyone:
Reacted to "Thank you SHL for th..." with 👏
20:41:55 From Maccabee Levine to Everyone:
Eureka overview including some on authentication: https://folio-org.atlassian.net/wiki/spaces/PLATFORM/pages/193134643/Folio+Eureka+Platform+Overview
20:44:35 From Jenn Colt to Everyone:
You are not alone
20:46:14 From Jenn Colt to Everyone:
Lots of discovery is not using edge
20:46:26 From Maccabee Levine to Everyone:
Reacted to "Lots of discovery is..." with 👍🏻
20:48:06 From Gang Zhou | SHL to Everyone:
When will FOLIO move to the Eureka?
20:50:18 From Jenn Colt to Everyone:
IndexData and Stanford have been playing with it
20:50:33 From Terence Ingram to Everyone:
Reacted to "IndexData and Stanfo..." with 👍
20:50:44 From Craig McNally to Everyone:
https://github.com/folio-labs/edge-ai
20:51:14 From Gang Zhou | SHL to Everyone:
I think FOLIO shall has AI strategy
20:51:42 From Craig McNally to Everyone:
Replying to "When will FOLIO move..."
that's TBD. From EBSCO's perspective we'd like to see it happen by Sunflower
20:51:53 From Jenn Colt to Everyone:
Jeremy also runs this group https://github.com/AI4LAM/metadata-working-group
20:52:22 From Craig McNally to Everyone:
Reacted to "Jeremy also runs thi..." with 👍
20:53:27 From Gang Zhou | SHL to Everyone:
Reacted to "Jeremy also runs thi..." with 👍
20:54:01 From Gang Zhou | SHL to Everyone:
Replying to "When will FOLIO move..."
Thanks |
