2018-09-21 - System Operations and Management SIG Agenda and Notes

• Determine note taker: Patty
• Review action items

Jakub explained the Q3 release philosophy and documentation.

Q3 will be released on October 1. We are -10 from the release and there are a few critical issues to be resolved.

You can see the code at folio-q3.aws.indexdata.com (login and password same as testing)

There won't be snapshot builds of this release. The dev/snapshot/testing stream will continue separately.

The release is built off released packages

github.com/folio-org/platform-complete

branch for the release includes the lists of apps and their version.

For the backend you can reference okapi-install/json

Release notes and links to jiras at github.com/folio-org/folio-install - will have a branch for the q3 rlease

The intention is for this release to be easy to build repeatedly.

The FOLIO -install includes the Reference data (i.e. bootstrap) and the sample data.

There's a filter in JIRA for the q3 branch

Only bug fixes will be released to this branch.

    - new reference data (=bootstrap data), new sample data

 - Filter in JIRA "Known critical Q3 issues"

Discussion

Conern (Dale): Need more frequent release cycles. Need to deploy more recent modules

Jakub: Need to use snapshots. Snapshots will be more stable now, but still not suitable for production.

I

Notes from Holly's OLE report on the Q3 release for reference:

Jakub Skoczen gave us an overview on the timeline of the Q3 release. He gave us insight to the current status of development and walked us through the github repos that will hold the release for download. There will be a new repo “platform-complete”. This new repo will host a bundle of independent platforms, supplying not only the code developed by the core team, but also from Acquisitions, E-Holdings and finally also ERM. ERM will not be integrated in Q3, yet, it will be in Q4.  Q3 will be bug-fix free. Subsequent snapshots will be more stable than previous ones, but yet not suitable for production.

Plans of SIG members about how to deploy it.

mplementers plan to use Q3 instances to populate with local data. Anne Highsmith at TAMU and Dale Arntson at UCHI have already written scripts to load instance, holdings and items.

We discussed doing some acceptance style testing !

Dale: Q3 will become stale quickly. Need be repeatedly build and be stable.

Patty: Let's exchange self-written extraction scripts; TAMU is on Voyager. TAMU has loaded location data, user data, inventory / records / items.

Dale: Users, Vendors, Permissions, Inventory have been loaded at Chicago. Giving permissions to users.

Can use ModDataLoader for binary MARC already now, Batch Loader will be capable of MARC-XML.