2023-12-08 Sys Ops & Management SIG Agenda and Meeting notes

1. Missing Indexes

Jeremy:  Warnings for missing indexes
[mod_feesfines] WARN CQL2PgJSON Doing LIKE search without index for accounts.jsonb->'status'->>'name', CQL >>> SQL: status.name == Open >>> lower(f_unaccent(accounts.jsonb->'status'->>'name')) LIKE lower(f_unaccent('Open'))
Do people manually add these indexex to the databases ? Or should we file tickets ?
It might be correlated to some kind of poor performance.
Florian switched on the slow query log. He sees slow queries because the ERM module has some performance issues. He could find some indexes that could speed up (the search).
He reported it to Owen Stevens
Jason: I found some of the tickets in mod-circulation and mod-feesfines. I think they added the index.
   There was a performance to be gained.

 https://folio-org.atlassian.net/browse/CIRCSTORE-454
  https://folio-org.atlassian.net/browse/MODFEE-319
Nils: In that case we should all start filing tickets to the developers.
Jason: A lot of these indexes will come in Poppy according to the Jira tickets.
mod-user, mod-feesfines and more modules are affected. Probably it is related to an RMB problem.
They are slowly phasing out the RMB framework.
Tod: It think it will be a long, long transition phase.
     It is worth implementing mod-users.

2. Application Formalization from WolfCon.

Ingolf; This is being discussed also in a German governance meeting group, now with the participation of SysOps. They will continue to meet regularly and work out a concept or proposal:

From the meeting notes of the German group 2023-12-04

The technical concept has received positive feedback from most people. But what about the governmental concept ? This is of most concern to the group.

The platform formalization proposal if of most interest. What platforms will be maintained ? Maybe a platform for ERM, a platform for public libraries, a platform for municipal libraries, a platform for this and that ?

The German group is mostly interested in this: Who will be responsible for what ? Who will make the decisions, e.g. what modules will be in what platform ?

So far, none of the three councils had the power to make these decisions.

What are the possible risks and side effects ?

A question which has not been touched is the one of Ownership. Module ownership, application ownership. How will it be defined and what does it mean ? We need to find a definition.

At the moment, it is virtually impossible to take on the development of a module, even if you have the resources (= developers + money). An example is : reminder notifications in acquisitions.

→ We need to anchor this already in the system architecture, that it is possible to take on the development of a module. At least for the core modules. There shall be several development teams involved in the development, not only one. It should be implemented modularly, to make it easier to take on.

It needs to have a test scenario, also for the "extended" modules. Who will take on these additional expenditures ?

Introduce badges in a marketplace. E.g. "this app is conformal to ..." , "this app is rarely being used".

Responsibilities for platforms should be taken on by the functional SIGs.

The PC should have the souvereignity to decide "what will become a part of the release".

A big risk: Some apps might need to be post-installed, which are not part of the release, if I offer a certain app (of within the release) to my client. 

Who will do a roadmap for all this ?

Documents which contain a list of questions directed towards the tri-council-group:
TC Questions: https://docs.google.com/document/d/1OLae-eGN3_dEOXbAr7Tr1cvudBzqNA7TttzH9QmvuR8/edit#heading=h.50f0f2jmdfjl
PC Questions: https://docs.google.com/document/d/1yxF-D47tpTmiusJYn8XtWbFKnk2ZapSvxH2kxEmE-F8/edit#heading=h.tlfg3xytadup
Jason: Developers will need some bare minimum to develop on.

Jason: I am setting up an Enterprise light container platform at A&M. Consolidate shared infrasctructure. I am involved in migrating the infrastructure.
      Libraries has to move on to something. We run over 18,000 containers. We have 8 K8s cluster, a lot of which are FOLIO.
      We run 4 scaled instances of FOLIO, dev, test, pre and prod.
      We need representation at FOLIO councils. FOLIO is enterprise software.

3. A glitch in emails going out on test instances
Nils: A glitch with mails going out on test instances
Jason: Reset user email addresses on test instances for mail tests:
UPDATE tamu_mod_users.users
SET jsonb = Jsonb_set(jsonb, '{personal, email}', '"folio_user@library.tamu.edu"')
WHERE jsonb -> 'personal' ->> 'email' != 'folio_user@library.tamu.edu';

Ingolf also observed this behaviour.