2025_01_29

[ChrisJohnNOAA]

Attendees:
Marco Alba
Alice Cavaliere
Seth Champagne
Clifford Harms
Chris John
Vimal N
Shane St Savage
Micah Wengren

1) Action Item Review

#214

Official ERDDAP™ docker: Pull request from Shane to make it easy to build the docker image from the source tree is in. It also supports pointing to an arbitrary branch/commit and building from there. As part of this there was also better support for CORS that can be easily configured.

S3: Seth has been thinking about this, no pull request yet. Hopefully will be easy. The big question is do we want to support http links or s3 uris. The consensus on the call was both.

2) Go over the priority projects and discuss any changes we'd like to make.

Chris brought up GSoC if there's anybody interested in mentoring. Also mentioned some project ideas:

• Prometheus additional metrics and building a monitoring/alerting dashboard to use them
• Update page rendering to use a template framework
• Improved support for interacting with ERDDAP™ from scripts (particularly restricted/private datasets)

Shane brought up:

• The ability for ERDDAP™ to determine which host it is being served at via headers (solves an administrator problem that is more common with Docker).

Chris' recommendation was the private datasets from script and the ERDDAP™ host projects are both exciting things for ERDDAP™, but maybe not ideal projects for GSoC. Also they discourage individuals from running more than one project at a time in GSoC, so we'd need additional mentor volunteers to do more projects.

Clifford requested adding refactoring to make it simpler to add additional file type export formats. This would make it easier for the Navy to contribute back some of their work.

3) Java 17 support

Currently ERDDAP™ (except for Lucene dependency) should be compatible with Java 17. In order to build for Java 17 you need to edit the Java version and the Lucene version, but no code.

Shane suggested adding an automatic build step that runs all of the tests with those settings to validate compatibility of all changes with Java 17.

Seth is happy with making the pom changes for the Navy builds if official ERDDAP™ is maintaining Java 17 compatibility.

4) Make meeting quarterly

All thumbs up for scheduling Wed at noon eastern, on the last Wed of the month every 3 months.

5) 2.26 Review

The plan is to make a build soon. Some ERDDAP™ project work that is not in the build is migrating the documentation to a new system that will have better organization, search, and localization support. There's also been a lot of progress on getting an official Docker image on Docker Hub.

Changes:

• Datacite support (and other admin configurable information) Dataset Citation and display info #134 (Thanks Ayush!)

Bug Fixes:

• RSS and subscription actions will now trigger when a dataset updates due to file changes (not just reload): Have file updates trigger RSS changes and Subscription actions. #248

The things that still need to land:

• Additional Prometheus metrics

6) 2.27 Planning

Localization support, specifically something that relies only on the ERDDAP datasets.xml file. Specifically we'd parse the xml:lang attribute for dataset attributes. This would be optional so current datasets.xml would function as is. If a language is requested by end users that had localized text provided we'd display that, otherwise fallback to the default text (either the one with no attribute, lang="en", or a configurable language code).

Action Items:

• (Shane/Chris) Document setting up SSL with Docker
• (Chris) Find servers currently using S3 for questions about changes (reach out to SIG)
• (Chris) Set up meeting to be recurring
• (Chris) Add to priority projects, make it easier to add new export formats without needing to touch so many code locations.
• (Marco) Update on datasets.xml CMS (adding here to get an update next time)