2018-01-04 - System Operations and Management SIG Notes

Date

04 Jan 2018

Time	Item	Who	Notes
5	Welcome	Ingolf	Meeting will commence at 9 AM EST ; Steve was assigned to be the note taker.
15	Go through action items		Todd posted a list of integrations available here: https://folio-org.atlassian.net/wiki/display/SYSOPS/List+of+Integrations Other integrations we may want to add: Institutional repository Digital Collections management Knowledge Base Culture of direct database access discussion Lots of people still expect direct database access. Built-in tools in RDBMS often don’t meet needs Librarians used to writing SQL queries Data warehouse may be a good solution to allowing ad-hoc querying of data (possibly fully indexed by a tool such as elastisearch or solr) Discussion of how we get our list of desired integrations into development pipeline. We need a product owner for SysOps. Ingolf will bring this issue to the product council. Agreement to pull together a list of integration work that needs development time that we can take to the PC. Chris M will do a rough draft over the next couple days, and we'll talk about it next week, before the PC meeting.
20	Deployment environments
	Migrations		Migration discussion: SysOps SIG is definitely going to be responsible for many aspects of migration ETL tool of some sort/who is responsible? Developed and shared by different institutions? API specification requests by SIG?

Ingolf Kuss : appeal to the Product Council (chair), that we need a PO for Sys Ops. Maybe we need more than one PO: * for EBSCO's internal staff. * for the broader community
Ingolf Kuss : appeal to the PC (chair), that the SIG has additions to the FOLIO Feature Backlog (formerly: V1 Dev & Milestone plan 2) (in significant amount and quality)
Chris Manly : review List of Integrations
add lines to FOLIO Feature Backlog below the line or create separate spreadsheet.
group: discuss new lines for FOLIO Feature Backlog. Ingolf Kuss : Add topic in FOLIO Discuss for this,