2018-06-29 - System Operations and Management SIG Agenda and Notes

Ingolf, Filip Jakobsen, Schwill, Carsten

We will discuss the overlap between the ToDo-App, UXPROD-599, and the Lightweight Issue Tracker, UXPROD-849 . Carsten will present refined specifications for the Issue Tracker, which include a UI Draft. There are presumably a few requirements on top of the ToDo-App resulting from the ticketing functionality.

Filip Jakobsen: ToDo app comes out of the work of the ERM group for managing sequences of tasks. Combination of assigning tasks to colleagues and to the system. E.g.: a human does something, the system does several things, then another human reviews the outcome.

Schwill, Carsten presented on issue tracking in FOLIO (see PPT linked above). Filip Jakobsen commented on a possible connection with the form building app currently being considered.

One thing that is new to the conversation about ToDo/Workflow is the idea of dynamic priority settings based on service levels.

There is large overlap between the issue tracker and ToDo. Filip Jakobsen and Schwill, Carsten will meet to work out details of functionality that are not currently in the ToDo design and present back to the group. Some functionality that is new include: custom fields, dynamic prioritization, templates for issues.

• Who will build the list (group, selected members of group (with "hands-on experience"), group plus developers (knowledgeable of system architecture)) ?
• When will we build the list ? Until when ?
• What should be in the list (content, purpose) ?
  • What do we need to know from Stripes to Okapi all the way down to how the modules work ?
  • What is missing from the documentation that we have read ? 

  • What need to be contained within the documents ?

  • What pitfalls did we encounter ?

The "laundry list" is a list of documentation that a system administrator would need to be able to install/deploy and manage a FOLIO installation. A best practices guide, or an administrator's guide, or operations guide, etc. The idea is to pull together existing documentation, identify the gaps, and write or request new documentation.

spampell proposes pulling together a small group to work collaboratively on a document (or set of documents) in the wiki. Ingolf Kuss will create a space in the wiki and TAMU and other will contribute. Collaboration with developers will be necessary.

Recommended working with David Crossley to identify existing documentation.

Technical council is also working in parallel on a similar topic.

Three action items from last week's meeting:

1. System architecture guide (John Malconian)
2. Stable, released code (Jakub Skoczen, Hkaplanian, John Malconian)
3. Best practices guide (the "laundry list" – maintained by this SIG)