Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "community relevant" assertion.
- declaration considerations "-" assertion.
- declaration considerations "Using Thredds data server" assertion.
- declaration considerations "-" assertion.
- declaration considerations "Using Thredds data server. We need to convert all data to the NetCDF format" assertion.
- declaration considerations "Metadata are openly available" assertion.
- declaration considerations "Using AERIS AAI server (keycloak)" assertion.
- declaration considerations "Using AERIS AAI server (keycloak)" assertion.
- declaration considerations "Using AERIS AAI server (keycloak)" assertion.
- declaration considerations "5 years min. as stated in the ACTRIS DMP" assertion.
- declaration considerations "Home made JSON format, compliant with standards" assertion.
- declaration considerations "conversion to netcdf planned" assertion.
- declaration considerations "Community relevant" assertion.
- declaration considerations "under development" assertion.
- declaration considerations "Ongoing submission of missing concepts" assertion.
- declaration considerations "Home-made metadata format compliant with standards" assertion.
- declaration considerations "Conversion from GEOMS HDF planned" assertion.
- declaration considerations "HDF4 files, a conversion to NetCDF is planned for ACTRIS but both formats will be distributed because HDF is required by NDACC" assertion.
- declaration considerations "Widely accepted. " assertion.
- declaration considerations "Will follow ENVRI recommendations" assertion.
- declaration considerations "Will follow ENVRI recommendations" assertion.
- declaration considerations "Widely used in community" assertion.
- declaration considerations "Highly community relevant." assertion.
- declaration considerations "Widely used." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "community relevant" assertion.
- declaration considerations "generally relevant." assertion.
- declaration considerations "community relevant" assertion.
- declaration considerations "widely used, no need for authentication." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "used for fully quality controlled data, open for anybody." assertion.
- declaration considerations "Project requirement." assertion.
- declaration considerations "Widely used in community." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community standard." assertion.
- declaration considerations "Community standard." assertion.
- declaration considerations "Widely used in community." assertion.
- declaration considerations "Widely used in community" assertion.
- declaration considerations "Highly community relevant." assertion.
- declaration considerations "Widely used." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "RI relevant." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "RI relevant." assertion.
- declaration considerations "RI relevant." assertion.
- declaration considerations "Community standard." assertion.
- declaration considerations "Generally relevant" assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "widely used, no need for authentication." assertion.
- declaration considerations "used for fully quality controlled data, open for anybody." assertion.
- declaration considerations "Project requirement." assertion.
- declaration considerations "Widely used in community." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community relevant" assertion.
- declaration considerations "RI needs its customized vocabulary." assertion.
- declaration considerations "Community standard." assertion.
- declaration considerations "Community standard." assertion.
- declaration considerations "Widely accepted." assertion.
- declaration considerations "Expert recommended." assertion.
- declaration considerations "This is the Argo ERDDAP server.This API provides access to Argo data and metadata. https://www.ifremer.fr/erddap" assertion.
- declaration considerations "Metadata are registered in NetCDF files available from https or ftp" assertion.
- declaration considerations "Data are registered in NetCDF files available from https or ftp" assertion.
- declaration considerations "The long term preservation of Argo dataset is shared by Ifremer and US-NCEI. Both sites preserve and mint regular DOIs of the whole dataset (monthly snapshots)" assertion.
- declaration considerations "The Argo DOI representation language is compliant with DataCite RDF schema and RDF Schema.org " assertion.
- declaration considerations "Argo metadata such as sensor type, history records are recorded in Argo NetCDF self descriptive variables. The controlled vocabularies are published on NVS vocab server." assertion.
- declaration considerations "The Argo data DOI is based on DataCite Metadata scheme" assertion.
- declaration considerations "We use DataCite and Schema.org for Argo data and metadata DOI" assertion.
- declaration considerations "The one-click download of Argo data and metadata is available from this DOI: https://doi.org/10.17882/42182.These are monthly snapshot of the whole Argo dataset (GDAC data)" assertion.
- declaration considerations "We think that a persistent identifier for individual cycle file (2 million of them) should be provided. It won't be DOI, it should be a handle." assertion.
- declaration considerations "There should be one pid per Argo float cycle. There are more than 2 million cycles. The pid will be resolved by an Ifremer 'argo data selection' web landing page." assertion.
- declaration considerations "The one-click download of Argo data and metadata is avilable from this DOI: https://doi.org/10.17882/42182" assertion.
- declaration considerations "The data and metadata organization are described in: Argo user's manual, http://dx.doi.org/10.13155/29825. It describes the NetCDF CF implementation for Argo data" assertion.
- declaration considerations "The Argo GDAC DOI (https://doi.org/10.17882/42182) uses the schema.org metadata schema." assertion.
- declaration considerations "The DOI DataCite schemas" assertion.
- declaration considerations "Google dataset search is efficient for cross domain search." assertion.
- declaration considerations "The Argo data selection is a dedicated and specialized to our Argo community" assertion.
- declaration considerations "The Argo floats dashboard interactively provides Argo metadata from the Argo GDAC. https://fleetmonitoring.euro-argo.eu" assertion.
- declaration considerations "The Argo Opensearch engine is available on : https://opensearch.ifremer.fr/" assertion.
- declaration considerations "Argo DOI is indexed on Google, Bing, Seanoe, OpenSearch, google dataset search" assertion.
- declaration considerations "This is a data selection tool with Argo specific subsetting criteria (parameters, deployment years, network). Its API is : https://dataselection.euro-argo.eu/swagger-ui.html#" assertion.
- declaration considerations "The metadata access is anonymous. The download statistics from https and ftp servers are analyzed without user identification." assertion.
- declaration considerations "The data access is anonymous. The download statistics from https and ftp servers are analyzed without user identification." assertion.
- declaration considerations "The Argo DOI representation language is compliant with DataCite RDF schema and RDF Schema.org " assertion.
- declaration considerations "The Argo community decided 20 years ago to distribute data and metadata in NetCDF files. The Argo NetCDF format is regularly improved." assertion.
- declaration considerations "The Argo vocabularies used in NetCDF files are published on NVS vocab server" assertion.
- declaration considerations "We use DataCite and Schema.org for Argo data and metadata DOI" assertion.
- declaration considerations "Argo data and metadata are distributed with a CC-By license" assertion.
- declaration considerations "Argo data and metadata are distributed with a CC-By license" assertion.
- declaration considerations "The Argo NetCDF implementation contains detailed provenance information : data state, processing state, history of adjustements" assertion.
- declaration considerations "The provenance information is recorded in Argo NetCDF implementation documented on http://dx.doi.org/10.13155/29825" assertion.
- declaration considerations "The Argo ontology uses PROV-O to record provenance information. This information can be queried from Argo SPARQL endpoint: https://sparql.ifremer.fr/argo/query." assertion.
- declaration considerations "The one-click download of Argo data and metadata is available from this DOI: https://doi.org/10.17882/42182." assertion.
- declaration considerations "We think that a persistent identifier for individual cycle file (2 million of them) should be provided. It won't be DOI, it should be a handle." assertion.
- declaration considerations "We shall investigate the use of ePIC as data identifier." assertion.