Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "There was already provenance info in the metadata," 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 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 "Argo data and metadata are distributed with a CC-By license." 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 "Data are registered in NetCDF files available from https or ftp" assertion.
- declaration considerations "We use DataCite and Schema.org for Argo data and metadata DOI" 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 "This is a data selection tool with Argo specific subsetting criteria (parameters, deployment years, network)." 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 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 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 "Use has been evaluated in EUDAT prototype project" assertion.
- declaration considerations "This is a legacy system that will be merged with the EISCAT_3D data portal in future. Implementation TBD." assertion.
- declaration considerations "Considered by ENVRI-FAIR" assertion.
- declaration considerations "A version of the EISCAT data download server which is an OIDC introspection enabled Checkin client has been developed." assertion.
- declaration considerations "De facto standard among legacy incoherent scatter radars" assertion.
- declaration considerations "Archived Level 3 (analysed) data have been converted to two new HDF5 based archive formats. This includes MADRIGAL version 3 which now uses a HDF5 format as standard." assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "Used in Jupyter hub and many other applications by the community for easy access to SPARQL, ontology, metadatahttps://pypi.org/project/icoscp/" assertion.
- declaration considerations "The ICOS SPARQL open endpoint https://meta.icos-cp.eu/sparql serves (read-only) the complete ICOS ontology and all metadata in RDF format. It is used by most back-end and front-end services of the ICOS Carbon Portal. A GUI version is served at https://meta.icos-cp.eu/sparqlclient/" assertion.
- declaration considerations "The m2m interfaces to interact with the meta and data services and other back end services are based on REST 'inspired' https calls. The calls are document at the CP github repository at pages https://github.com/ICOS-Carbon-Portal/meta and https://github.com/ICOS-Carbon-Portal/data" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "ICOS is set up for the long term, 20-25 years starting from 2015. Statutes and data policy mention that data and metadata should be preserved also after that. In case ICOS ERIC is wound down in the future there will be a one year period to develop the contingency plan. All current landing pages generated dynamically by our metadata system can then be generated as static html pages that will together form a frozen metadata system which can be served by a simple static website at very low cost or be integrated as sub-site in another permanent website." assertion.
- declaration considerations "ICOS is set up for the long term, 20-25 years starting from 2015. Statutes and data policy mention that data and metadata should be preserved also after that. In case ICOS ERIC is wound down in the future there will be a one year period to develop the contingency plan. All current landing pages generated dynamically by our metadata system can then be generated as static html pages that will together form a frozen metadata system which can be served by a simple static website at very low cost or be integrated as sub-site in another permanent website." assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "As defined by the CP white paper and to implement the open data sharing defined by the statutes of ICOS ERIC. " assertion.
- declaration considerations "under way" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "The m2m interfaces to interact with the meta and data services and other back end services are based on REST 'inspired' https calls. The calls are document at the CP github repository at pages https://github.com/ICOS-Carbon-Portal/meta and https://github.com/ICOS-Carbon-Portal/data" assertion.
- declaration considerations "Used in Jupyter hub and many other applications by the community for easy access to SPARQL, ontology, metadatahttps://pypi.org/project/icoscp/" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "All ICOS data is available open and free." assertion.
- declaration considerations "All ICOS data is available open and free." assertion.
- declaration considerations "ICOS is set up for the long term, 20-25 years starting from 2015. Statutes and data policy mention that data and metadata should be preserved also after that. In case ICOS ERIC is wound down in the future there will be a one year period to develop the contingency plan. All current landing pages generated dynamically by our metadata system can then be generated as static html pages that will together form a frozen metadata system which can be served by a simple static website at very low cost or be integrated as sub-site in another permanent website." assertion.
- declaration considerations "ICOS is set up for the long term, 20-25 years starting from 2015. Statutes and data policy mention that data and metadata should be preserved also after that. In case ICOS ERIC is wound down in the future there will be a one year period to develop the contingency plan. All current landing pages generated dynamically by our metadata system can then be generated as static html pages that will together form a frozen metadata system which can be served by a simple static website at very low cost or be integrated as sub-site in another permanent website." assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "Preliminary state for an institutional repository 1) Open access for published data on Dataverse repository 2) Restricted access for contributors" assertion.
- declaration considerations "Initially used in the AnaEE France community. To be extended to EU level" assertion.
- declaration considerations "Non-systematic usage among platforms IS." assertion.
- declaration considerations "GeoNetwork, in use in the AnaEE France community." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "Preliminary state. Only registered users in a local internal database have write access. " assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "Initially used by the AnaEE France community. To be extended to EU level." assertion.
- declaration considerations "Not yet implemented. The objective is to add PROVenance elements to the semantic characterisation already in use in AnaEE for the description of data and their contexts, and to implement it using the developped pipelines." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "GeoNetwork, in use in the AnaEE France community. CKAN portal under development at the AnaEE EU level (https://data.anaee.eu/)." assertion.
- declaration considerations "Preliminary state for an institutional repository. 1) Open access for published data on Dataverse repository. 2) Restricted access for contributors." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "Initially used in the AnaEE France community." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "No additional elements to report." 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 DOI DataCite schemas" 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 ontology uses PROV-O to record provenance information. This information can be queried from Argo SPARQL endpoint : https://sparql.ifremer.fr/argo/query. Argo SPARQL endpoint : http://purl.org/np/RA1IPRCYWlzzoT4z11Fj8q3_thw4xtC_jYyMirHTKVCHc" 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 "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 Argo DOI representation language is compliant with DataCite RDF schema and RDF Schema.org. " assertion.
- declaration considerations "We use NetCDF CF metadata." assertion.
- declaration considerations "Google dataset search is efficient for cross domain 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 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 "The Argo DOI representation language is compliant with DataCite RDF schema and RDF Schema.org " 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.
- declaration considerations "The Argo NetCDF implementation contains detailed provenance information : data state, processing state, history of adjustements" assertion.
- declaration considerations "Work in progress." assertion.
- declaration considerations "Work in progress." assertion.
- declaration considerations "According to DANUBIUS-PP" assertion.
- declaration considerations "Currently in use by the community of users." assertion.
- declaration considerations "Under consideration." assertion.
- declaration considerations "Several options are considered. No final decision yet." assertion.
- declaration considerations "Harmonized EMSO ERIC data services also use other mechanisms for identification of data and products." assertion.
- declaration considerations "EMSO ERIC uses a harmonized metadata schema based on OceanSites specifications, CF and other conventions. The final document is not publicly available yet. The schema is used through different mechanisms such as NetCDF (below) and ERDDAP." assertion.
- declaration considerations "DataCite is the most used" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "Harmonization of the vocabulary is still required. Under development." assertion.