Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "Analysed data inserted in Madrigal are also indexed by experiment in https://handle.eiscat.se" assertion.
- declaration considerations "DataCite metadata records are added when analysed results are converted from Matlab to HDF5 files." 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 "MADRIGAL has served well for distributing analysed data from the legacy systems and will remain in use for that purpose. It will not scale well to EISCAT_3D data however." assertion.
- declaration considerations "EISCAT is a member o the PITHIA Network of Research Facilities and PITHIA builds upon developments during the ESPAS FP7 project." assertion.
- declaration considerations "Compatibility with B2FIND" assertion.
- declaration considerations "Considered by ENVRI-FAIR" assertion.
- declaration considerations "Existing EISCAT datasets should be downloadable through a web browser. For future EISCAT_3D data it is planned to use DIRAC to stage data for analysis on grid or cloud resources." assertion.
- declaration considerations "Existing EISCAT datasets should be downloadable through a web browser. For future EISCAT 3D data it is planned to use DIRAC to stage data for analysis on grid or cloud resources." 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 "An old de facto standard among incoherent scatter radars and other upper atmospheric instruments." assertion.
- declaration considerations "Used in EISCAT HDF5 archive format for Level 3 data (analysed physical parameters)" 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 "Analysed data from EISCAT radars (Level 3 data) are now archived in a dedicated HDF5 format and indexed in a SQL database with DataCite metadata records." assertion.
- declaration considerations "Agreed by EISCAT Associates." assertion.
- declaration considerations "Description was implemented as a prototype exercise in ENVRI." assertion.
- declaration considerations "Analysed data inserted in Madrigal are also indexed by experiment in https://handle.eiscat.se" assertion.
- declaration considerations "DataCite metadata records are added when analysed results are converted from Matlab to HDF5 files." 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 "MADRIGAL has served well for distributing analysed data from the legacy systems and will remain in use for that purpose. It will not scale well to EISCAT_3D data however." assertion.
- declaration considerations "EISCAT is a member o the PITHIA Network of Research Facilities and PITHIA builds upon developments during the ESPAS FP7 project." assertion.
- declaration considerations "Compatibility with B2FIND" assertion.
- declaration considerations "Considered by ENVRI-FAIR" assertion.
- declaration considerations "Existing EISCAT datasets should be downloadable through a web browser. For future EISCAT_3D data it is planned to use DIRAC to stage data for analysis on grid or cloud resources." assertion.
- declaration considerations "Existing EISCAT datasets should be downloadable through a web browser. For future EISCAT 3D data it is planned to use DIRAC to stage data for analysis on grid or cloud resources." 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 "An old de facto standard among incoherent scatter radars and other upper atmospheric instruments." assertion.
- declaration considerations "Used in EISCAT HDF5 archive format for Level 3 data (analysed physical parameters)" 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 "Analysed data from EISCAT radars (Level 3 data) are now archived in a dedicated HDF5 format and indexed in a SQL database with DataCite metadata records." assertion.
- declaration considerations "Agreed by EISCAT Associates." assertion.
- declaration considerations "Description was implemented as a prototype exercise in ENVRI." 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 (obtained via the French member of Datacite: INIST-CNRS)" assertion.
- declaration considerations "DOI are minted using the AERIS prefix (obtained via the French member of Datacite: INIST-CNRS)" assertion.
- declaration considerations "Automatic conversion from internal metadata format to Datacite schema" assertion.
- declaration considerations "Internal format compliant with ISO standard" assertion.
- declaration considerations "widely used in community" 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 "REST api" assertion.
- declaration considerations "-" assertion.
- declaration considerations "Using Thredds data server. We would need to convert all data to the NetCDF format" assertion.
- declaration considerations "Metadata are openly available" assertion.
- declaration considerations "Data are open" assertion.
- declaration considerations "Home made JSON format, compliant with standards" assertion.
- declaration considerations "Conversion of all data to NetCDF planned. " assertion.
- declaration considerations "Community relevant" assertion.
- declaration considerations "Community relevant" assertion.
- declaration considerations "Home-made metadata format compliant with standards" assertion.
- declaration considerations "Conversion from EDF files to be done. Both format will be distributed" assertion.
- declaration considerations "-" assertion.
- declaration considerations "Community standard" 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 "All ICOS data is available open and free." 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 "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 "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 "CF-1.7 compliant netcdf metadata included in the netcdf data objects" assertion.
- declaration considerations "CF-1.7 compliant netcdf metadata included in the netcdf data objects" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" 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 "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" 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 specialiszed to our Argo community." 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 "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)." 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 "Argo data is hosted in Ifremer Sismer service. Sismer is a RDA Core-Trust Seal certified data centre. Our long-term data and metadata longevity plan is a commitment of our RDA-CTS certification. " 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.