Technical Board 2025_07_30

[ChrisJohnNOAA]

Attendees:
Marco Alba
Seth Champagne
Clifford Harms
Chris John
Roy Mendelssohn
Tylar Murray
Shane St Savage
Micah Wengren

1. Review 2025_04_30 #285

Marco- gave a demo of the ERDDAP™ CMS developed in conjunction with another group.
Still a work in progress, already 1 version in production, able to edit datasets.xml via web using server deployed on same machine as where ERDDAP™ is.
Working only with the Docker version of ERDDAP™.
Can also export an xml file (with a specific format)
Behind it is a python api- CMS is written in python.
Some resistance from the other group in the project to releasing open source at this time.

Navy had something that used a modified version of the generatedatasets java class.
Navy might be interested in using something that could automatically register dataset.

Seth: S3- funding came in!
Working on pulling in one or two co-workers to help tackle the back log. Hopefully a simple fix and can address it in the next month.

2. Go over the Priority Projects #158 and discuss any changes we'd like to make.

Matt (Clifford) something to start working on something soon: Better handling of overlapping times, started a GitHub Discussion: #334

Seth- stewing on a plan to allow java services to load new EDDTable or EDDGrid implementations. Inject new dataset types to the code base.
A good first step of refactoring that would be a configuration class that captures those parameters and then pass a data object that has the configuration.
Java Services Framework- from Java 5, plenty of libraries use it, manifest step to load in.
Chris mentioned the work from Shane to use reflection+annotations for loading dataset types. Behind a flag, not the default yet, but hopefully soon.

3. Review of 2.28.0

• Croissant Schema
• Prometheus dashboard

4. Plan what work we are targeting for the next release (2.29.0)

• GSoC project: MQTT
• GSoC project: JTE
• S3
• Changing to use modern java.time instead of GregorianCalendar
• Standard request filters (instead of filtering within the ERDDAP request handling).
• (maybe) Some quick UI improvements after JTE is done

Some discussion of joda.time library. They recommend using the java.time library.

5. ERDDAP™ demos

Chris' idea to try to help build awareness of changes within ERDDAP™ and community tools around ERDDAP™.
General approval for the idea, recommended maybe quarterly

Action Items

• (Chris) organize the first demo call
• (Seth) update on S3