2021-10-05 - Sys Ops & Management SIG
SysOps SIG NFRs Initiative & Integrations Work Group Meeting
Date
Attendees
Chris Rutledge (second half)
...
Meeting Link
- https://zoom.us/j/591934220
- Password: folio-lsp
Goals
- Push forward our NFRs initiative / Define and describe top 3 NFR requirements that cause most pain and need to be worked on
- Integrations initative: Collect integrations from more Implementers, group and prioritize.
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
Note Taking: Ian ; Ingolf | |||
FOLIO infrastructure / NFRs | Ingolf | Next Steps // ToDos // What we should focus on I.) Define 1 - 3 NFR requirements
| |
Is this in the scope of SysOps, or more for SMEs/POs/SIGs? It is between SMEs and architects. Circulation may be a good example of this; so much information about loans, inventory and patrons has to be consulted to perform circulation actions. Can some of those calls be reduced? Users shouldn't require circulation. | |||
Is this Domain Boundaries in another form? Yes. Can I run a big module independently of the rest of these things ? | |||
mod-source-record-storage has been re-engineered to be more relational to improve performance | |||
FOLIO Integrations | Status of the work of the Integrations Working Group
Goal: rank integration pain points... maybe not ready to do that yet today. SSO seems like a possible high priority. Much work has been done on INN-Reach. Much is apart from the capacity planning process. One Option is: Hire EBSCO, IndexData or some other vendor. E.g. only very few institutions have remote storage; not main stream modules. Other examples: CAIASOFT, Dematic. Capacity Planning is only one possible group to work with; we're empowered to push our own institutional needs (provided we provide the necessary resources to make it happen). Cap Planning cannot provide resources for the entire project. The FOLIO module mod-remote-storage abstracts the need for particular vendors to manage remote storage. The edge modules specify the integrations for particular vendors edge-caiasoft, edge-dematic. The vendors pour their resources in to get the development done. | ||
Topics for future meetings |
|
Zoom Chat
Wayne Schneider: Perhaps data normalization is a better term than integrity in this context
Ian Walls: How much does it 'cost' to spin up a module in terms of cluster resources? How much of that is overhead, and how much is meaningful logic?
Wayne Schneider: That’s a great question, Ian. Of course, it depends (in large part on the data set).
That is, if you’re trying to operate on a lot of data at once, you need more heap. If you’re operating on one thing at a time (e.g. circulation), not so much.
Root, Jason M: Indeed there are some memory requirements that are determined by the module developers. I consider those the “minimum requirements” for memory at least.
Ian Walls: The topic of "making FOLIO easier to install" has been brought up in all 3 Councils several times in the last few weeks. So it's getting airtime
Philip Robinson: That’s good to hear, Ian - I knew TC was on it of course but didn’t know about the others
Action items
- Type your task here, using "@" to assign to a user and "//" to select a due date
- Get NFRs on the Roadmap
- jroot will ask Paula Sullenger to have us speak up in the Implementers Group.
- All: Pull together a list of existing JIRAs (UXPRODs, Epics) for these top NFR requirements. Post it in the Chat. Edit these JIRAs / Add more JIRAs (UXPROD, stories).