Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "Overarching services demand harvesting of metadata via OGC services" assertion.
- declaration considerations "Aggregated CDI records will be distributed via spra" assertion.
- declaration considerations "Access via Marine-ID authentication in the CDI service " assertion.
- declaration considerations "Metadata records available in XML" assertion.
- declaration considerations "Datafiles in ODV format are in ASCII" assertion.
- declaration considerations "Datafiles in NetCDF format are binary" assertion.
- declaration considerations "The NVS have been developed by BODC based on the SDN requirements and specifically fulfill the needs of the marine data community. However for provenance the used vocabs will be expanded with L22 (sensor type) as well as links to the Sensor Instance! (cant make this)" assertion.
- declaration considerations "SDN has developed metadata directories for organisations, cruises, research projects, databases, that are involved in, or used by, the datacenters when collecting data. In the metadata of the datasets there are refs to these metadata directories (instead of free text!)." assertion.
- declaration considerations "NVS service used as main vocabulary for parameters, instruments, etc. " assertion.
- declaration considerations "metadata for datasets in CDI format are based on ISO19115/19139, extended with the domain profile with vocabs etc. The ISO requirement originates from the overarching infrastructures that demanded inspire standards." assertion.
- declaration considerations "ODV data transport format " assertion.
- declaration considerations "NetCDF CF supported by SDN vocabs" assertion.
- declaration considerations "Now using https://www.seadatanet.org/Data-Access/License/1.0 but will be made as GUPRI under ENVRIFAIR, plus mapping to CCBY" assertion.
- declaration considerations "Now using https://www.seadatanet.org/Data-Access/License/1.0 but will be made as GUPRI under ENVRIFAIR, plus mapping to CCBY" assertion.
- declaration considerations "ISO adopted PROV-O will be investigated, but probably better fit for data products (sextant). In CDI more info about sensors will be included." assertion.
- declaration considerations "There is already provenance info in the metadata, and more info about sensors will be included." assertion.
- declaration considerations "Metadata are stored in a MongoDB database. Documents are identified by a UUID." assertion.
- declaration considerations "DOI are minted using the AERIS prefix" assertion.
- declaration considerations "Handle server hosted by AERIS with a prefix obtained from ePIC" assertion.
- declaration considerations "Internal metadata format compliant with standards, incl. ISO 19115" assertion.
- declaration considerations "community relevant" assertion.
- declaration considerations "Automatic conversion from internal metadata format to Datacite" assertion.
- declaration considerations "Automatic conversion from internal metadata format to Datacite" assertion.
- declaration considerations "rest api" assertion.
- 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 "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 "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 "Will follow ENVRI recommendations" assertion.
- declaration considerations "Will follow ENVRI recommendations" 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 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 "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 Argo SPARQL endpoint allows interoperable and semantic queries on Essential Ocean Variables (NVS, CF) and well established vocabularies such as ORCID, FOAF, SOSA (sensors) or DCAT (catalogue of services)." 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 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 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 "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 "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 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 "Cost effective solution, our data portal requires lots of PIDs due to large number of digital objects." assertion.
- declaration considerations "DOIs required for collections, e.g. yearly data sets." assertion.
- declaration considerations "Our data portal already assigns PIDs (EPIC handle) for any arbitrary data collection downloaded by the user." assertion.
- declaration considerations "EPIC handle PID points to DO landing page containing the URL of the actual file for downloading, and each file contains PID to the corresponding landing page." assertion.
- declaration considerations "EPIC handle PID points to DO landing page containing the URL of the actual file for downloading, and each file contains PID to the corresponding landing page." assertion.
- declaration considerations "It's the standard." assertion.
- declaration considerations "Easy access to data for users." assertion.
- declaration considerations "Open access required by the community. Easy access to metadata." assertion.
- declaration considerations "Open access required by the community. Easy access to data." assertion.
- declaration considerations "Implementation in progress." assertion.
- declaration considerations "It's the most widely used format." assertion.
- declaration considerations "Widely used." assertion.
- declaration considerations "Standard." assertion.
- declaration considerations "Need internal one. Not yet implemented." assertion.
- declaration considerations "Standard." assertion.
- declaration considerations "Requirement." 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 "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 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 "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 metadata access is anonymous. The download statistics from https and ftp servers are analyzed without user identification." 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 "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 "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 "We use DataCite and Schema.org for Argo data and metadata DOI" assertion.
- declaration considerations "The Argo data DOI is based on DataCite Metadata scheme" assertion.