Versions Compared

Version Old Version 10 New Version Current
Changes made by

Vinaya Mayya

Stephen Fuqua

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Participants

Expand

  • Denver Public Schools - Max Paulson

  • Ed-Fi staff & contractors

    • Adam Hopkins

    • Brad Banister

    • Robert Hunter

    • Sayee Srinivasan

    • Stephen Fuqua

    • Steven Arnold

    • Vinaya Mayya

  • Edufied - Geoff McElhanon

  • EdWise Group - Britto Augustine

  • Resultant - Joshua Impson

  • Simpat Tech - Ashish Patel

  • Utah State Board of Education - Katrina Brinkley

Agenda

  • Review the roadmap

  • Demonstration of current work

  • Design Questions

...

Note

Reviewing the list below:

  1. Which features listed “By Summit” should we prioritize to try to release sooner?

  2. Are there any features we failed to list?

Tip

Meeting notes:

  • Data Standard support

    • Prioritize 5.2 for Tech Congress; many states are moving that direction right now.

    • Nice to have support for 4.0 as well, for pilot testing with vendors who have not updated to 5.x yet.

    • 6.0 preview is not useful from a pilot testing standpoint, since no one has an integration yet.

    • In 1.0, MSP’s would like to have support for multiple data standards at the same time: a single API deployment that can store both 5.2 and 4.0 data structures, with validation based on URL route. Allows for better cost optimization.

      • (warning) Parking lot: design discussion on mechanisms for supporting this. Initial proposal to prefer separate database instances for different Data Standard versions. Maybe tie DS version into the URL routing for instances?

    • Extensions should be the next priority after authorization; would like to have by Tech Congress if possible.

  • Profiles

    • Remove “dynamic” from the list to avoid confusion (same with “XML” on “XML Composites”).

    • Agree: must have for 1.0 and not mandatory for Release Candidate at Tech Congress.

  • Level 2 validation

    • Need to explain both types better when turning the table below into a formal document.

    • For streaming data, mention observability as well.

  • ETags

    • Some client integration may be looking for _etag in the body or the ETag header on POST requests.

    • For release candidate, should at least stub out a hard-coded value to prevent breaking client integrations.

      • (warning) Design note: we plan to calculate ETags based on hashing the _lastModifiedDate. This is relatively trivial. We should simply consider ETags as a must-have feature for the spring release candidate.

  • ODS-like Views

    • This discussion helped us recognize the value of talking about (at least) two stages of pilot testing: transactional vendor integration (via the API), and downstream reporting.

    • ODS-like views are intended to support the second stage of pilot testing. States could start testing a 1.0 release without the ODS-like views. Can potentially defer until after 1.0.

  • Core database storage

    • Correction, Education Analytics is today using Aurora for the ODS/API.

  • Change Queries

    • Current usage scenarios:

      • API-to-API synchronization via API Publisher

      • Assessment rostering

      • Enable Data Union (EDU) data warehousing.

    • We should consider this a must have solution, even if the streaming architecture can provide alternative synchronization patterns. Too many integrations would break without this.

  • Authorization

    • Ownership-based authorization and combined strategies are used in multiple states. Definitely a must have for 1.0, but can live without them for the release candidate.

Data Standard and API Standard Compatibility

...

Feature

ODS/API Platform

Data Management Service

By TC

By Summit

Concurrency management with ETags

(tick)

Status
colourBlue
titleMUST HAVE

(question)

(tick)

LIMIT/OFFSET paging

(tick)

Status
colourGreen
titledone

(tick)

Cursor-based paging

(tick) (7.3)

Status
colourBlue
titleMUST HAVE

(question)

Identification code-based queries

(tick) (7.3)

Status
colourBlue
titleMUST HAVE

(question)

Identities API

(tick)

Status
colourYellow
titlecould have

Note

Need to review field usage and fitness-for-purpose before committing.

(question)

Unique ID System Integration

(tick)

Status
colourYellow
titlecould have

Note

Need to review field usage and fitness-for-purpose before committing.

(question)

Database Technologies

Feature

ODS/API Platform

Data Management Service

By TC

By Summit

Core database storage in PostgreSQL

(tick)

Status
colourGreen
titledone

The database structure is very different than the ODS database

(tick)

Core database storage in MSSQL

(tick)

Status
colourBlue
titleMUST HAVE

(tick)

GET queries using search database

(error)

Status
colourGreen
titledone

Either OpenSearch or Elasticsearch

(tick)

GET queries using relational database

(tick)

Status
colourBlue
titleMUST HAVE

Removes the requirement to run Kafka and OpenSearch or Elasticsearch

(tick)

Reporting queries using ODS database schema

(tick)

Status
colourBlue
titleMUST HAVE

Note

This will likely be a compatibility layer to ease the transition for those who have built reporting solutions on the ODS database structure.

Is this required for state-based pilot testing? Can it be finalized after the 1.0 release?

(question)

Core database storage in managed PostgreSQL-compatible databases (e.g. Aurora, Cosmos DB)

(error)

Status
colourPurple
titleSHOULD Have

Conceptually this should work, but we may need community help for testing these scenarios while the development team focuses on code-level features.

(question)

Realtime population of a data lake

(error)

Status
colourPurple
titleSHOULD Have

(question)

Redis-based caching

(tick)

Status
colourPurple
titleSHOULD Have

(question)

...

Feature

ODS/API Platform

Data Management Service

By TC

By Summit

SwaggerUI

(tick)

Status
colourBlue
titlemust have

(tick)

Admin Console

(warning) coming soon

Status
colourBlue
titlemust have

(question)

(tick)

Demonstration

Tip

Meeting notes:

Ran out of time for the demonstration. The sequence diagram below shows the interactions for client credential management.

The demonstration was going to use this file which uses the REST Client extension for Visual Studio Code. Even without VS Code, the file should be easy to follow along with while replicating the API calls in another client such as Postman.

Working Client Management and Authentication

Expand
titleMermaid diagram
Code Block
sequenceDiagram
    actor Sys Admin

    rect rgb(191, 223, 255)
    note right of Sys Admin: One time setup.

        Sys Admin->>Config Service: POST /connect/register
        Config Service->>Identity Provider: Create credentials
        note right of Identity Provider: Created with config role
        
        Config Service-->>Sys Admin: clientCredentials
    end

    Sys Admin->>Config Service: POST /v2/vendors
    Config Service->>Config Database: INSERT dbo.Vendor

    Sys Admin->>Config Service: POST /v2/applications

    Config Service->>Identity Provider: Create credentials
    note right of Identity Provider: Created with dms role
    Identity Provider-->>Config Service: clientCredentials
    Config Service->>Config Database: INSERT dbo.Application
    Config Database -->>Config Service: applicationId
    Config Service->>Config Database: INSERT dbo.ApplicationEducationOrganization
    Config Service->>Config Database: INSERT dbo.ApiClient

    Config Service-->>Sys Admin: clientCredentials

...

Design Questions

Tip

Meeting notes:

Ran out of time. Will keep these design questions for a future meeting.

What plans are there for error detection (i.e. dropped records) and correction?

...