Page Comparison

Ingolf has been working on a set of Single Server Installation instructions https://github.com/inkuss/docs/blob/R2-2021/content/en/docs/Getting%20started/Installation/R2-2021/singleserverwithcontainers.md 

Florian was interested in who is running on Kubernetes

• TAMU - on-premises kubernetes using VMWare and Rancher
• Stanford - AWS Kubernetes and folio-org/folio-helm Helm Charts
• CU Boulder - AWS Kubernetes, heading towards folio-org/folio-helm Helm Charts
• FOLIO Project is using single server on AWS (snapshot environments), and Kubernetes via Rancher using folio-org/folio-helm Helm Charts (scratch environments)

"Grooming": Work on Epic(s) and User Stories & Sub-Stories for those

Work for a subgroup.

Seems to be the proper way forward

• Intend to put together a working group to groom epics and user stories for NFRs from Operational and SysOps needs Technical needs met when standing up FOLIO installs

77 backend calls to do a checkout.

A mega session about technical debt at the next WolfCon

• The Integrations Pain Points Tab Folio Source Data and Integrations has been presented to the Implementers' Group. 
  • Chalmers, Grand Valley State University (GVSU), Stanford, Holy Cross, TAMU added columns.
  • Newly mentioned integrations: INN-Reach, Banner (Campus IdM), RapidILL, AI Virtual Assistant, ROAM (ERM); Discovery Layers
    • INN-Reach is Document Sharing; Missoury State is using this. Brooks Travis runs a Working Group about this
    • Rapid-ILL is an application (Ex Libris product). ILLIAD is done by Atlas Systems.
    • ROAM: under consideration
  • from German community: Network printers, e.g. for orders from storeroom. Other R1 Priorities of GBV&hbz&HeBIS:
    • Network printing - understand that the current recommendation is to print via browser, but that is insufficient for their needs
      • Complicated problem
    • SIP2: general functionality is there, but optional fields (e.g. sortBin) have not yet been implemented
    • RTAC/DAIA UXPROD-2423
    • Patron Portal Support / PAIA. Initiative of German FOLIO partners to develop a FOLIO-PAIA connector
    • Connection to IdM / Workflow. Existing identity management systems must be integrated and/or synchronized. Following the Chalmers model, FOLIO can act as an IdM for users. But there has to be an authentification service for the passwords which have been stored in FOLIO in order to enable the authentification to third party systems.
      • Discussion about different patterns for authentication, one of the German libraries is doing development to use FOLIO as source of user authentication (Axel is working in this area).
• Implementers' group has two weeks time to further edit the spreadsheet. SysOps SIG integrations working group will be guest in Implementers' meeting on Nov 2nd again — which is probably too early ? (we can only start to prioritize after Nov 2nd)
  • Goal of the document is to alert to pain points with the intention of highlighting best opportunities for development
  • Might want to document what is supported and what is planned/desired

• Migration scripts from other LMS/ILS to FOLIO
• Moving reference data between two instances of FOLIO; e.g. circulation rule migration
• Campus IdM management with FOLIO