Skip to content
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

New PROGRAM collection under OceanOps #80

Open
vpaba opened this issue Nov 8, 2023 · 3 comments
Open

New PROGRAM collection under OceanOps #80

vpaba opened this issue Nov 8, 2023 · 3 comments
Assignees
Labels
avtt Argo Vocabulary Task Team new collection Request for a new Argo/OceanOps NVS collection

Comments

@vpaba
Copy link
Contributor

vpaba commented Nov 8, 2023

New issue to specify requirements that evolved from #5

@vturpin Picking up on questions from that thread:

To create a collection, we need to know:

  • the Editors. So far @MKrieger29 has been the OceanOps Editor for the 'R' collections with shared governance with ADMT; who would you like to be the Editor of the PROGRAM collection? It could be more than one person
  • owner and governance - for the 'R' collections created so far we've used 'Argo Data Management Team', but I understand this will be under OceanOps governance? we can also use a different prefix to 'R'
  • the collection metadata: identifier, title, alternative title, description (e.g. 'O01', 'Network affiliations and programs', 'PROGRAM_NAME', 'A program defines a group of platforms or cruises managed by the same lead agency (generally national). It materializes the implementing, operating, and responsible team. A program is bound to: one and only one country; to one or several agencies (including one lead agency) with defined roles; to a set of contact points with defined roles. Some particular cases such as EuroArgo (European Research Infrastructure Consortium), or E-SURFMAR (EUMETNET, grouping of European National Meteorological Services) use a multinational agency and “Europe” as country.')
  • the concepts to go under that collection, and how to store the information for each concept under the IDs, prefLabels, altLabels and definition structure (which should be consistent throughout the collection) - to be taken from this?

Mappings can be added at a later stage, but we can start creating a list.

Am I right to understand that the plan is for this collection to encompass ALL programs for OceanOps-registered platforms, and not just the Argo ones? I believe there is appetite for this - at least from the BODC side.

Happy to have a chat to agree on the requirements.

Thanks,
Violetta

@vpaba
Copy link
Contributor Author

vpaba commented Mar 12, 2024

Hello @vturpin and @MKrieger29, I hope all is well! I was wondering whether we shall progress this, maybe by having a meeting first to review this proposal, and identify the questions to answer in order to proceed?
Thanks,
Violetta

@vturpin
Copy link

vturpin commented Oct 11, 2024

@MKrieger29 @vturpin will send exel sheet to Dani.
with ID - pref label - alt label - definition

@vturpin
Copy link

vturpin commented Oct 11, 2024

@danibodc I've send you the extract of Argo program for the collection
ID refers to our internal unique ID for each vocabularies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
avtt Argo Vocabulary Task Team new collection Request for a new Argo/OceanOps NVS collection
Projects
Development

No branches or pull requests

5 participants