Investigate ways to improve CTD on deployment metadata

[matdon17]

The Argo metadata field DEPLOIYMENT_REFERENCE_STATION_ID is rarely populated and of low utility when it is due to the type on content included. We need to assess pootential ways to make this field more useful in actually locating CTD on deployment information.

[tcarval]

When available, we should use the CTD URI to populate DEPLOYMENT_REFERENCE_STATION_ID
Example of the Ovide 2018 cruise CTD 62549388

• DEPLOYMENT_REFERENCE_STATION_ID = "uri:https://dataselection.coriolis.eu.org/details/PR_CT_62549388"

@RomainCancouet , @vincent.bernard, @fmerceur, does that sounds good to you ?

[tcarval]

On Ifremer side we are progressing. We can now have URI for the Coriolis CTDs
Example : the CTD cast from "Pourquoi pas?" vessel (call sign FMCY) 29/09/2022 11:32:52

• https://dataselection.coriolis.eu.org/uri/p87075054

Our next step will be to assign a PID from an independant provider (B2HANDLE from EUDAT or ePIC). The PID landing page will be the Coriolis URI (example above).
We will provide DEPLOYMENT_REFERENCE_STATION_ID in the form :

• DEPLOYMENT_REFERENCE_STATION_ID = "uri:https://hdl.handle.net/11676/B9MS0-y-1BVgYbLdcyz9oX1P"