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

Date and Time

13 March 2023 12:30-14:00 UTC (13:30-15:00 Geneva time)

Venue

Telecon

Draft Agenda

  1. Approval of agenda and minutes of previous meeting
  2. GAW IP 2024-2026 (10')
  3. work plan for 2023 in support of current GAW IP (20')
  4. Specific requirements on GAWSIS in future deadline: mid-April 2023
  5. develop action items for next GAW IP 2024-2026 (5')
  6. implementation of topic hierarchy for WIS2 (20')
  7. 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')
  8. next meeting
    • 24 April at EGU (Room 2.61 (38)) and online 10:45 - 13:45 CEST(listen in to ad-hoc meeting at EGU)
    • 8 June 12-13:30 UTC (14:00-15:30 CEST)

Notes

Participants: Jörg Klausen (JK), Gao Chen (GC), Tom Kradilis (TK), Jeanette Wild (JDW), Markus Fiebig (MF), Debra Kollonige (DK), Atsuya Kinoshita (AK), Eduardo Landulfo (EL), Judd Welton (JW)

WMO Secretariat: Sergi Moreno (SM)

1.Approval of agenda and minutes of previous meeting - Minutes of 2023-1 meeting were made available only shortly before the meeting. Approval postponed. - Agenda approved.

2. GAW IP and EC outcome - GAW IP approved w/o much discussion - GGMI approved, funding uncertain.

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

Assessment needs to be done individually. The link belongs to the work done in the November 2022 meeting TT. Assessment can be done in the same page. An action to be done before the next meeting. What we have achieved so far? Please make it clear in the notes: https://github.com/wmo-im/et-acdm/wiki/ET-ACDM-Work-Plan-2023

4.Specific requirements on GAWSIS in future deadline: mid-April 2023

What are the requirements from the WDC regarding the GAWSIS integration into OSCAR?

GC: Develop a tool, wis 2.0 is a very high level, we can do it with our requirements. MF: How to keep our records in OSCAR updated, interface complicated: OSCAR just stops after asking for updates. It asked for identification. JK: write it down and that would be treated as a requirement. A call to please contribute to this: search capability or mapping capability? ET-WT leads the task integration of GAWSIS in OSCAR.

5. Develop action items for next GAW IP 2024-2026

Which guidance should we take to develop action items? Take the actions we have in the current IP, use that level of specificivity. Jörg asked for an comments on that.

6. Implementation of topic hierarchy for WIS2 (20')

TK:

  • Wis 2.0 provides data and (discovery) metadata via notifications

  • Example: can/eccc-msc/data/core/hydrology

  • Topic hierarchy is used for publishing, notifying, discovering or filtering

  • People can subscribe to wis 2.0 for specific channels; example: ozone or hydrology.

  • Topic hierarchy primary topic level:

  •  1-3 infrastructure

  •  4-8 ET Metadata TT-wis metadata

  •  Level 8 is earth system discipline (from cg-ex-2021)

  •  (ET-ACDM) is one of the domains

  • Where the licensing would go?

  • Not in the topic hierarchy.

  • What happens with the attribution then?

  • MF: users are more interested in the licensing. Difference in between core and recommended.

  • Gao: what happens with the low quality data?

  • TK: we probably need to have a data classification.

  • JK: national/international? Regional?

  • Recommended data with licensing, in the discovering metadata standard you can give access with access control.

  • TK: we shouldn't overengineering the tool.

  • JK: can you choose what to subscribe? TK: absolutely you choose your menu. (smart subscription)

  • TK: country is defined by ISO... in the case of WOUDC we use an extension (257- WMO Global Services)

  • GC: Titles for data? (field campaign, ground-based, etc)

  • Discussion about the 4 elements of level 9 for Atmospheric Composition, JK:

  • GC: for aerosols should we have clouds?

  • TK: revise the level 9 and make a proposal for ET-Metadata. WIS 2.0 timeline: 2023 pilot phase, 2024 preoperational, 2025 transition.

  • MF: if you construct a hierarchy, the position needs to be unambiguous, should WMO history would be on guidance for the hierarchy? ACTRIS could be an example.

  • JK: open an issue in Github related to that page or can be edited directly.

  • TK: building up the topic hierarchy, an issue tracker label for wis 2.0 could be created.

  • TK: when do the people think to have a first draft? JK: in one month, for next meeting?

  • JW: clouds and atmospheric dynamics are not Atmospheric Composition, should be capture somewhere else?

  • TK: willing to share how other groups are doing it (in response to Jörg).

  • TK: we generate the level 10 however the TT on metadata would need to deal with that.

  • TK: other domains are working at the same time with different levels? he suggested to focus in level 9 & 10.

  • JK: I-adopt as an example?

7. discussion and possible adoption of https://copdess.org/enabling-fair-data-project/

  • JK: we don't have enough time unless people had a look at it.
  • MF: can you give us a short introduction?
  • JK: COPDESS can be a competition of data archives or a complement. Is there a possibility that GAW or WMO becomes a partner?
  • MF: the rest of partners seem very high level ones.
  • JK: keep it on the agenda and a discussion can take place in the future.
  • JK: asked MF to take the lead in topic 7.