...
Meeting ID: 790 499 9331
Attendees:
- Dale Harris
- Jeff Braswell
- Sean Bohan
- Josh Hershman
- Nathan Southern
- Joseph Nibert
- Ash Naik
- David Reale
- Brian Hoffman
- Tsvetan Georgiev
- Peter Antley
Agenda:
- Update on openIDL Testnet/Workshops (SeanB)
- openIDL NodeBuilder Workshop 2023
- Recap last Weds session
- Today: Fabric Operator Console Introduction
- openIDL NodeBuilder Workshop 2023
- IWG update (YankoZ)
- Update on RRDMWG and internal Stat Reporting with openIDL (Peter Antley)
- Architecture Decisions in OLGA
- Other Stat Reporting Progress
- AOB:
Notes:
RRDMWG
- Next meeting this Weds 6/21
- OLGA
- big focus: edits and when editing and how many records editing (understanding user stories/experience)
- Stat Reporting
- Mason+ Commercial properties
- Data modeling and bedrock of HDS set up by end of Aug
- OLGA
- highlight risk points
- POCs to understand functions required
- in progress:
- grid component (first pass)
- large file uploads
- Big ?: how do we slay errors so users can see what errors/stat records HAVE an error and utility to address
- in SDMA, have 1 screen for stat record and 1 screen for errors
- hoping for one unified UI, error rows, update errors at same time, find a graceful way to do it
- demo stuff next Monday AWG (OLGA Demos)
Todays Discussion
- Go over some tenets, things to validate, take questions
- single page app in React (simple, doesnt have cost to compute, no need for SEO)
- MaterialUI instead of TOAST
- did not find TOAST component compliant with modern vers of React
- using prebuilt methods in AWS ecosystem, exploring
- OLGA is AWS-first app
- diff cloud environment will require work
- some AWS-specific resources, cheap for carrier to own, TCO low,
- Reco for OLGA in Azure: build azure-compliant vers of the ap
- MS has specific features like AWS, cloud agnostic app would make price to skyrocket (2x vers agnostic)
- Validated almost all functionality, biggest concern is editing and updating records that have failed validation
- Record level vs Threshold?
- sum of record level errors, overall total amt errors, contribute to those thresholds is sum of those
- wont doublecount an error
- updating and reviewing single rows at a time
- wouldn't know if hit a threshold issue?
- edit funct, hit submit to make an update
- Running totals of errors
- 1 table all the records, 1 table all the errors
Time | Item | Who | Notes |
---|---|---|---|
Documentation:
...