TAG Meeting 2016-05-04

Owned by Eric Jansson (inactive account)
Last updated: Jul 26, 2016
2 min read

Participants

  • Erik Gomez
  • Duy Nguyen
  • Don Dailey
  • Arley Schrock
  • Dan Retzlaf
  • Geoff McElhanon
  • Josh Klein
  • Matt Warden
  • Neal Schuh
  • Eric Jansson
  • Chris Moffatt

Notes

The first topic  of the meeting was to bring the TAG up to date on the work to increase support for multiple years of data in the ODS and Dtaa Standard. The attached documents were reviewed and TAG members invited to join the SIG that will continue to pursue the technical designs. A few discussion points were brought up, including

  • Is this intended to produce a different ODS? The current directionality is "no" - this is intended to deliver a feature that can be turned on or off. This was regarded by comments as a good direction.
  • Current practice of having year specific ODS. The comments indicated that TAG members would like to see this investigation try to replace that with a multi-year system.
  • Versioning alignment. Current direction is to align with data standard v2.1. No comments indicated disagreement with that direction.
  • Transaction dates vs ability to modify historical dates ("back-dating"). Use cases were brought up supporting the need for each type of ability. For example, where there are fiscal impacts, systems often develop the capacity to manage historical dates (food service was the example), but in many other cases, transaction date is fine.
  • Audit trail needs. The sense was an audit trail was needed, but specific requirements not surfaced in the meeting.

The second topic was to look at the MI case as a way of getting TAG input on how to expand APIs over time. The use-case based composite direction was seen as a good option, but having the granular APIs as a way to "complete" anyh missing needs was seen as a good current direction.

Documents

Temporal ODS and UDM

 

Michigan - API Case Study