-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2-02 Programs/networks: addition of GOOS/DBCP entries, deadline 24.08.2019 #115
Comments
Bearing in mind that @anthoninlize is the designated JCOMMOPS rep in TT-WMD and our best available expert on this, I only checked if these entries do not yet exist (they do not) and are syntactically correct (they are). We also need the WMO306_CD for these entries. After reviewing what existis already in the table, I propose the following: There is no consistency for what is written in caps vs small-caps, but the above is in line with what we have now. I suggest there is no need for a 4-week deadline, this is purely technical. |
From what I understood did we say "technical" are only typo fixes etc., everything that really changes the codelists should not be technical?, but we can adapt the procedure here of course. So I can change the label and deadline. However, it does not really make a difference if we leave 1 or 4 weeks of deadline now - the new release is already out. If this should be part of the release going on the code registry and to the fast track we need another release. |
Hi Luisa
the difference is that, if we can agree amongst the team members, we can safely include this in OSCAR/Surface, which can be done quickly and which is a prerequisite for the M2M upload of DBCP metadata by JCOMMOPS. The release on the codes registry and official approval through the fast-Track is not so urgent in this case, it would seem.
Cheers
Jörg
…Sent from my iPhone
On 24 Jul 2019, at 15:34, LuisaIckes <notifications@github.com<mailto:notifications@github.com>> wrote:
From what I understood did we say "technical" are only typo fixes etc., everything that really changes the codelists should not be technical?, but we can adapt the procedure here of course. So I can change the label and deadline. However, it does not really make a difference if we leave 1 or 4 weeks of deadline now - the new release is already out. If this should be part of the release going on the code registry and to the fast track we need another release.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#115?email_source=notifications&email_token=AIFWXY5STCBHR666HZJWRJTQBBK7HA5CNFSM4IGNXOS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2WLERA#issuecomment-514634308>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AIFWXY64BOIHKYHN4TFP3W3QBBK7HANCNFSM4IGNXOSQ>.
|
@anthoninlize : Is there a description to be added for these entries as well? |
Yes, for some of them : \Co-sponsored\GOOS\DBCP\GDP-MF: GDPMF \Co-sponsored\GOOS\DBCP\IPAB-US: IPABUS \Co-sponsored\GOOS\DBCP\JAMSTEC-DB: JAMSTECDB \Co-sponsored\GOOS\DBCP\PORTUGAL-MB: PortugalMB |
@anthoninlize : Thank you! I will add N/A for the remaining. |
This all makes sense and consists of non-controversial additions to an existing table. |
The changes are done in issue 115. |
Reopening issue because it was not included in the previous FT cycle. |
@fstuerzl Verify consistency of branch and follow through |
@amilan17, I checked the branch and can confirm that the new entries are consistent with OSCAR. |
@anthoninlize Please verify entries in branch issue 115 (https://github.com/wmo-im/wmds/blob/issue115/tables_en/2-02.csv) are correct and add definitions where still missing. Deadline: 10 January 2021. |
@joergklausen I would need a more extended deadline because of the holidays season, and I can't get all the missing descriptions by myself, I need inputs from the team who is on holidays and I won't be able to chat with them before 10 January 2021 I'll add the ones I have already today |
Attached a copy of the file with new descriptions, when available. I'll provide more later when I can meet the team. |
Thanks, @anthoninlize, the branch is up to date now. The only descriptions still missing are the ones for "saildrone" and "SpainIEOMB". |
Great! I've seen other entries with missing descriptions from our side... More than those two ones. We'll update this as soon as possible. Thanks! |
fixed conflicts and merged with FT-2021-1-validation branch |
(352) \Co-sponsored\GOOS\DBCP\SAILDRONE |
@fstuerzl - please update branch with new descriptions and tag anna when done |
@amilan17 , @champikagallage branch updated: 7a65dfb |
Branch
https://github.com/wmo-im/wmds/tree/issue115
proposal
Dear all,
We would need the following new entries:
Thank you,
Best
The text was updated successfully, but these errors were encountered: