SOCIB data-sources corresponds to the so-called 'deployments'. Deployments are an instrument&platform enssemble deployed (placed or released) to retrieve data from the ocean. During the time period this combo is active, the data measured by it is said to belong to the same deployment and is stored in the same netCDF and distributed together in THREDDS. SOCIB API data-source endpoint allows a quick access to the data collected by a deployment.
SOCIB data-platforms wrapp data-sources sharing the same platform which enables then a quick recovery of the latest or historical data comming from a specific platform (particularly useful in case of long-term platform-based monitoring). A certain SOCIB data-platform can be composed then by a single data-source (i.e only one deployment has been performed with it) or serveral (i.e more than one deloyment has been perfomed with it).
SOCIB data-platforms constitute the first level of abstraction build over the data-sources, being the second one the so-called SOCIB data-products.
SOCIB data-products wrapp data-sources sharing the same context into one single entity. This context can represent campaings (i.e CANALES), projects (i.e ABACUS), operations (maintenance) etc. A certain SOCIB data-product can be composed then by a single data-source (i.e such data-source was deployed lonely) or serveral (i.e data-sources deployed during the same event).
SOCIB data-products constitute the second level of abstraction build over the data-sources, being the first one the so-called SOCIB data-products.