-
Notifications
You must be signed in to change notification settings - Fork 0
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
Comments
First, we could provide guidance to FLOAT OWNER. 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. |
@vturpin , can you propose a better definition for float_owner and float_institution ?
|
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 ? |
Do you propose to replace:
Can you propose a short sentence for each term ? |
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:
|
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.
The text was updated successfully, but these errors were encountered: