2018-04-12 - System Operations and Management SIG Agenda and Notes

• Determine note taker
• Review of Action Items

WOLFcon Topic Proposals

Draft WOLFcon agenda

• Size of room for Installfest at WOLFcon
• Discussion of install experiences
• Discussing orchestration tools

Discussion of what to do at WolfCon. Chris suggests the first day should be unstructured hands on experience. In Chris' experience from past hackathon people can be doing installs in small groups and have opportunities for free form. Dale asks what to do if newbies come to the session. Wayne thinks that will be unlikely. General question of where the meetings will be held. Ingolf says it will be over the railroad tracks from the hotel in the historic tobacco park. We need tables and good wifi, and very little else. Tod will ask Kate Waldren about these requirements. Patty wants to know what what we should talk about for the Data Migration session. Wayne wants to talk about ETL ideas, and how to develop those collectively. Dale says that we should maximize the time together for brain storming.

Holly and Chris present LS tools, a tool set a Cornell which allows technical services do library automation tasks through a common web interface. Chris demonstrates the tool set. This is essentially an ETL tool. They have cleanup jobs, export and import jobs, and cleanup jobs. There is a specification written for each job that describes who owns it, how it is executed, what is needed, etc. The app also allows for searching of marc data with a highly granular selection capability. App is a swiss army knife of technical services activities. It has meant a huge increase in productivity for technical services staff. Dale says Chicago handles these needs using capabilites in OLE, but also using Access and MarcEdit. How do we provide these capabilities in Folio. Should they be written as an external app, or be bundled into Folio? What makes this relatively doable with existing systems is that they are talking to relational databases. Reimplementing this in Folio will be a challenge. The reporting can be handled through the reporting module, but the export / import capabilities have to come from somewhere else.