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

The FLOAT_OWNER field is not constrained and populated in different ways #7

Open
matdon17 opened this issue Nov 24, 2020 · 5 comments
Assignees
Labels
avtt Argo Vocabulary Task Team

Comments

@matdon17
Copy link

In Argo metadata, FLOAT_OWNER is in addition to PI_NAME, OPERATING_INSTITUTION, DATA_CENTRE

Variously an institution, a person’s name (or list of people), a DAC, or blank. Examples:
BRECK OWENS
MAURICIO M. MATA
UK Met Office
BRECK OWENS, STEVE JAYNE, P.E. ROBBINS
STEVE RISER
CSIRO
WHOI: WIJFFELS, JAYNE, ROBBINS
JAMSTEC
Euro-Argo

The approach in attempting to constrain this may be complicated by the multiple types of information that might be populated in this field.

@vpaba vpaba added the avtt Argo Vocabulary Task Team label Jun 3, 2021
@vturpin
Copy link

vturpin commented Sep 6, 2023

First, we could provide guidance to FLOAT OWNER.
My personal opinion is that it should be an institution not a PI, but I am sure there are many opinion here.

However, I don't think creating a variable for each agences or contributors involved in the operations, data management is the way forward.

I like the idea of, "agencies", "agencies EDMO CODE","agencies role" with a reference list for agencies roles.
Same could be apply to "contributors", "contributors role", "contributors ID", ...

@tcarval
Copy link
Contributor

tcarval commented Oct 23, 2024

@vturpin , can you propose a better definition for float_owner and float_institution ?
Below what we have in the user's manual.

<style> </style>
FLOAT_OWNER The owner of the float (may be different from the data centre and operating institution). Example: Joe Blogg
OPERATING_INSTITUTION The operating institution of the float (may be different from the float owner and data centre). Example: ACE CRC

@vturpin
Copy link

vturpin commented Oct 23, 2024

Since PI is becoming contrained to a vocabulary, I don't see need for float owner anymore. Unless this is an agency.

In that case I would call it OWNING_AGENCY to make it clearer.

The OWNING AGENCY refers to the agency that would take possession of the float if it were recovered. The OPERATING AGENCY is the agency responsible for the float's operational activities. For example, in the case of a float donated by IFREMER to the National Ocean Agency of Morocco and deployed by IFREMER in Moroccan waters, the OWNING AGENCY would be the National Ocean Agency of Morocco, while the OPERATING AGENCY would be IFREMER.

How does it sound ?

@tcarval
Copy link
Contributor

tcarval commented Oct 24, 2024

Do you propose to replace:

  • "FLOAT_OWNER" by "OWNING_AGENCY"
  • "OPERATING_INSTITUTION" by "OPERATING_AGENCY"

Can you propose a short sentence for each term ?

@vturpin
Copy link

vturpin commented Oct 24, 2024

We need to think a little bit about it i think. I am not totally convince by these definitions. But the idea to me is the following:

  • "OPERATING_AGENCY": agency in charge of the floats operations, this could include shipping, recette, deployment planning, recovery planning, etc.
  • OWNING_AGENCY": the owning agency of the float is the agency that have the responsability of the instrument. It is the agency that will get the float back if recovered, While PI has the scientific responsibility of the float, the OWNING agency have the "physical" responsibility of the float.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
avtt Argo Vocabulary Task Team
Projects
Status: No status
Development

No branches or pull requests

4 participants