ET ACDM 2023 1 - wmo-im/et-acdm GitHub Wiki

14 February 2023 13:00-15:00 UTC (14:00-16:00 Geneva time)

Venue

Telecon

Draft Agenda

  1. feedback to current draft (version 16 Jan 2023) of GAW IP 2024-2026 (20')

  2. assessment of progress made on action items from current GAW IP (20')

  3. work plan for 2023 in support of current GAW IP (30')

  4. ideas for action items for next GAW IP 2024-2026 (15') [postponed for lack of time]

  5. discussion and possible adoption of https://copdess.org/enabling-fair-data-project/ ?! If there is support, we would write a short position paper with an explicit commitment of the WDCs and other DCs. (10') [postponed for lack of time]

  6. implementation of topic hierarchy for WIS2 (10')

Notes

Expert Team on Atmospheric Composition Data Management

Meeting Minutes

February 14, 2023 – 14:00 – 16:00 CET

Attendance: Jörg Klausen (JK), Judd Welton (JW), Alex Vermeulen (AV), Gao Chen (GC), Kjetil Torseth (KT), Tom Kradilis (TK), Jeanette Wild (JDW), Markus Fiebig (MF), Debra Kollonige (DK), Atsuya

WMO Secretariat: Leilani Dulguerov (LD)

Absent:

Agenda available here

1.Feedback to current draft (version 16 Jan 2023) of GAW IP 2024-2026

Jörg Klausen opened the floor for any member to comment on the GAW IP.

Comment from KT: on p. 46 of IP, asking stations influenced by local pollution to store two data series – this is not done, and it does not make sense to do so.

Comment from GC: issue of data centers requiring log in, under SO/2a. the FAIR principles established log in and registration procedures – potential issue.

Comment from AV: document is vague and general about what will be done. SO/2a should maybe mention WMDR2 as well as WIS2.0. Actions should also have a signpost year for there to at least be a goal to work towards.

The ET should make a clear recommendation on this topic in the GAW IP, act prophylactically.

Comments on IP from JK: difficult document to read; too long and not specific enough. It has been communicated to Jürg Luterbacher that this document needs to be reworked after EC – this should be acknowledged to EC.

JK proposed, for the rest of the meeting, to assess what can be done in 2023 from the current IP; then look at the perspective activities in the new plan and pick out what the ET and data centers are willing to act on and drive forward.

Vote on a recommendation: Agree to recommend not to require log in for data access

AV stated that the ET should also recommend to not require a log in to search for data. In general, this recommendation should be more specifically articulated in the IP. Recommendations as part of the general principles should be mentioned.

2.Assessment of progress made on action items from current GAW IP

Postponed.

3.Work plan for 2023 in support of current GAW IP

Specific action items with milestones from the various partners that can be used to highlight commitment

A.I.: ET members to write down their ideas for actions for 2023 on a wiki page, with name/data center attached. (D: by next meeting of ET-ACDM)

A.I.: JK to share link to Github with the mailing list – helpful to have actions listed in a place they can often be referred to.

Topics/actions that the team would like to address this year that are related to but maybe not explicitly mentioned in the GAW IP

Items that should be discussed to develop a common workplan and action items for the new IP.

Comment from TK: consider how we approach WIS2 requirements – had to leave at 2pm so item 6 moved to item (4). High value of integrating with WIS2.

4.Implementation of topic hierarchy for WIS2: https://github.com/wmo-im/wis2-topic-hierarchy

Brief explanation from TK: A pilot phase is being undertaken to test the architecture, discussed at the f2f meeting in Lund.

Key component: the “topic hierarchy” – classification scheme used by data producers as part of providing data to the network. This supports the discovery, the publication of, and the subscription to data, for RT data sharing. Modeled after the Unified Data Policy.

This initiative managed by TT on WIS Metadata (led by TK) but all domain experts develop their own “Level 9” and contribute back to topic hierarchy. Good for integration of GAW into WIS2.

WIS2is providing high level hierarchy based on Levels 1-8, but it is task of ET-ACDM to develop Level 9, making sure data categorized correctly in WIS2 (designed to replace GTS).

This schema includes non-WMO type licenses. Need to find a way to accommodate attribution for those contributing observations.

Way of connecting WIGOS and WIS together, although it is still unclear where the link to WIGOS is – certain disparity between WIS (product focused) and WIGOS (observation focused). This is not advanced enough to propose efficient collaboration for eventual operationalization.

Comment from GC: existing WIGOS metadata could be used for AC sub-category.

A.I.: change link for unified data policy, still “draft resolution” (WMO Secretariat)

A.I.: JK to open an issue on Github for team to provide responses to agenda item (4).

A.I.: JK to follow up with TK to clear up expectations for contributions to this topic. Tabled for next meeting. TK to put together more information on the topic for next meeting.

Back to 3b: Topics/actions that the team would like to address this year that are related to but maybe not explicitly mentioned in the GAW IP

Uncertainty reporting: critical for data users (GC)

Follow up on above recommendations, put them on paper (GC)

Simplification of API and forms to be submitted to OSCAR + better linking of data and metadata (JW)

WMDR2 – change of model and representation necessary for certain requirements

Everyone wants simplicity, but it needs to still be powerful enough to relate information needed for certain use cases

TT on Climate Data Model has decided that climate data metadata should be based on WIGOS metadata (requires a lot of information)

Suggestions from JW for OSCAR Next Gen:

ET-ACDM should make recommendations for how cooperating and contributing networks are dealt with (in particular, remove barriers to site creation and visibility)

Issue of GAWSIS, ET-ACDM should make recommendations for what to do with GAWSIS-type interface in OSCAR

From JK: this must be articulated as specific requirements

Issue has been raised many times with EPAC-SSC, no results. Without requirements, GAWSIS may not exist at all in future. OSCAR currently doesn’t cover all functionalities of GAWSIS, as current GAWSIS homepage provides certain functionalities that OSCAR does not (e.g., specific mapping functionality). Moreover, GAWSIS currently acts as the broker for GAW IDs.

A.I.: JK to open issue on Github to collect specific requirements for GAWSIS and OSCAR to be handed over to WIGOS tools.

Question from JK to the team about keeping the three-letter GAW IDs. These are managed by the current GAWSIS. To be continued, the requirement must be specified.

The GAW Secretariat needs to fix this OSCAR issue – information is inaccurate and metadata transfer needs to be simplified. Depends on whether GAW wants to be inclusive or exclusive. WIGOS is more inclusive.

A.I.: ET to write this out as a requirement to bring to the WIGOS team.

Items (4) and (5) in the original agenda tabled to next meeting due to time constraint.