Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- 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 "DataCite is the most used" assertion.
- declaration considerations "DataCite is the most used" assertion.
- declaration considerations "Metadata are registered in NetCDF files and text, available through https from portal and ERDDAP." assertion.
- declaration considerations "Metadata are registered in NetCDF files and text, available through https from portal and ERDDAP." assertion.
- declaration considerations "Datasets are provided in NetCDF files and text (CSV), available through https from portal and ERDDAP." assertion.
- declaration considerations "Datasets are provided in NetCDF files and text (CSV), available through https from portal and ERDDAP." assertion.
- declaration considerations "Metadata records are publicly available." assertion.
- declaration considerations "Most of datasets are made publicly available; however, some functionalities requires authentication and authorization." assertion.
- declaration considerations "Metadata records using DOIs are compliant with RDF. " assertion.
- declaration considerations "Datasets using DOIs are compliant with RDF. " assertion.
- declaration considerations "Harmonized metadata uses NERC Vocabulary Server (NVS)." assertion.
- declaration considerations "Harmonized datasets use NERC Vocabulary Server (NVS) " 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." 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." assertion.
- declaration considerations "Use license is currently being harmonized across EMSO ERIC regional facilities; however, the most common is provided above." assertion.
- declaration considerations "Use license is currently being harmonized across EMSO ERIC regional facilities; however, the most common is provided above." assertion.
- declaration considerations "Provenance is currently being harmonized across EMSO ERIC regional facilities; however, the most common mechanism is currently via NetCDF." assertion.
- declaration considerations "Provenance is currently being harmonized across EMSO ERIC regional facilities; however, the most common mechanism is currently via NetCDF." 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 "Metadata are registered in NetCDF files and text, available through https from portal and ERDDAP." assertion.
- declaration considerations "Most of datasets are made publicly available; however, some functionalities requires authentication and authorization." assertion.
- declaration considerations "Harmonized metadata uses NERC Vocabulary Server (NVS)." 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." assertion.
- declaration considerations "The most common PID mechanism is indicated above. " assertion.
- declaration considerations "The most common PID mechanism is indicated above. " assertion.
- declaration considerations "DataCite is the most used" assertion.
- declaration considerations "DataCite is the most used" assertion.
- declaration considerations "DataCite is the most used" assertion.
- declaration considerations "DataCite is the most used" assertion.
- declaration considerations "DataCite is the most used" assertion.
- declaration considerations "Metadata are registered in NetCDF files and text, available through https from portal and ERDDAP." assertion.
- declaration considerations "Datasets are provided in NetCDF files and text (CSV), available through https from portal and ERDDAP." assertion.
- declaration considerations "Datasets are provided in NetCDF files and text (CSV), available through https from portal and ERDDAP." assertion.
- declaration considerations "Metadata records are publicly available." assertion.
- declaration considerations "Most of datasets are made publicly available; however, some functionalities requires authentication and authorization." assertion.
- declaration considerations "Metadata records using DOIs are compliant with RDF. " assertion.
- declaration considerations "Datasets using DOIs are compliant with RDF. " assertion.
- declaration considerations "Harmonized datasets use NERC Vocabulary Server (NVS) " 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." assertion.
- declaration considerations "Use license is currently being harmonized across EMSO ERIC regional facilities; however, the most common is provided above." assertion.
- declaration considerations "Use license is currently being harmonized across EMSO ERIC regional facilities; however, the most common is provided above." assertion.
- declaration considerations "Provenance is currently being harmonized across EMSO ERIC regional facilities; however, the most common mechanism is currently via NetCDF." assertion.
- declaration considerations "Provenance is currently being harmonized across EMSO ERIC regional facilities; however, the most common mechanism is currently via NetCDF." assertion.
- declaration considerations "The most common PID mechanism is indicated above. " 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 "DataCite is the most used" assertion.
- declaration considerations "Datasets are indexed in different engines such as google data search, SEANOE, PANGAEA, and aggregators. " assertion.
- declaration considerations "Datasets are indexed in different engines such as google data search, SEANOE, PANGAEA, and aggregators. " assertion.
- declaration considerations "Datasets are indexed in different engines such as google data search, SEANOE, PANGAEA, and aggregators. " assertion.
- declaration considerations "Metadata are registered in NetCDF files and text, available through https from portal and ERDDAP." assertion.
- declaration considerations "Metadata are registered in NetCDF files and text, available through https from portal and ERDDAP." assertion.
- declaration considerations "Datasets are provided in NetCDF files and text (CSV), available through https from portal and ERDDAP." assertion.
- declaration considerations "Datasets are provided in NetCDF files and text (CSV), available through https from portal and ERDDAP." assertion.
- declaration considerations "Metadata records are publicly available." assertion.
- declaration considerations "Most of datasets are made publicly available; however, some functionalities requires authentication and authorization." assertion.
- declaration considerations "Most of datasets are made publicly available; however, some functionalities requires authentication and authorization." assertion.
- declaration considerations "Metadata records using DOIs are compliant with RDF. " assertion.
- declaration considerations "Datasets using DOIs are compliant with RDF. " assertion.
- declaration considerations "Harmonized metadata uses NERC Vocabulary Server (NVS)." assertion.
- declaration considerations "Harmonized datasets use NERC Vocabulary Server (NVS) " 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." 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." assertion.
- declaration considerations "Use license is currently being harmonized across EMSO ERIC regional facilities; however, the most common is provided above." assertion.
- declaration considerations "Use license is currently being harmonized across EMSO ERIC regional facilities; however, the most common is provided above." assertion.
- declaration considerations "Provenance is currently being harmonized across EMSO ERIC regional facilities; however, the most common mechanism is currently via NetCDF." assertion.
- declaration considerations "Provenance is currently being harmonized across EMSO ERIC regional facilities; however, the most common mechanism is currently via NetCDF." assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "The current URI pattern for the IPCHEM metadata page is the following: https://ipchem.jrc.ec.europa.eu/#showmetadata/<DATASET> (e.g. https://ipchem.jrc.ec.europa.eu/#showmetadata/HBM4EUALIGNEDSTUDIES). And for the corresponding JSON version, the URI pattern is the following: https://ipchem.jrc.ec.europa.eu/public/<DATASET>/IPCheM_<DATASET>_metadata.json (e.g. https://ipchem.jrc.ec.europa.eu/public/HBM4EUALIGNEDSTUDIES/IPCheM_HBM4EUALIGNEDSTUDIES_metadata.json). With the transfer of the IPCHEM functionalities to the upcoming CPDC platform, new URIs could be implemented by using the Persistent URI service of the Publication Office (https://op.europa.eu/en/web/webguide/uris#persistive-uri)" assertion.
- declaration considerations "The current URI for the IPCHEM public dataset package summary is the following: https://ipchem.jrc.ec.europa.eu/public/IPCHEM_public_dataset_packages.csv. And for each dataset, the partial package summary URI pattern is the following: https://ipchem.jrc.ec.europa.eu/public/<DATASET>/IPCHEM_<DATASET>_package_summary.csv (e.g. https://ipchem.jrc.ec.europa.eu/public/HBM4EUALIGNEDSTUDIES/IPCHEM_HBM4EUALIGNEDSTUDIES_package_summary.csv). The package summaries contain the list of data packages available for each public dataset. Highest granularity data packages are split by chemical/media/period; cumulative data packages are available as well, split by period in the case of regular collections (e.g. yearly). The package name patterns are the following: a) https://ipchem.jrc.ec.europa.eu/public/<DATASET>/IPCHEM_<DATASET>_<UUID>.zip [datasets collected irregularly] (e.g. https://ipchem.jrc.ec.europa.eu/public/CNRPFAS/IPCHEM_CNRPFAS_3185f1f5-212c-4a2b-917a-4a8060115dd6.zip); b) https://ipchem.jrc.ec.europa.eu/public/<DATASET>/<PERIOD>/IPCHEM_<DATASET>_<UUID>.zip [datasets collected periodically] (e.g. https://ipchem.jrc.ec.europa.eu/public/WATERQUALITY/2014/IPCHEM_WATERQUALITY_519b7aba-2c74-40a3-a8a1-01b18eb55cd6.zip). With the transfer of the IPCHEM functionalities to the upcoming CPDC platform, new URIs could be implemented by using the Persistent URI service of the Publication Office (https://op.europa.eu/en/web/webguide/uris#persistive-uri)." assertion.
- declaration considerations "UUIDs are currently used in the package name patterns, as described in the previous FER (i.e. data URI). No versioning mechanism is implemented to persist the formerly created and subsequently amended packages, the previous UUIDs are simply lost. A possible enhancement could be to introduce versioning date as an additional field of the package summary, and to keep track of the former package UUIDs and corresponding files, for better traceability and replicability." assertion.
- declaration considerations "Dataset metadata fiches are currently compiled by filling three alternative templates: IPCHEM basic, HBM4EU and Indoor Air (xlsx). These are transformed automatically into JSON, and deployed to the public data package repository, as described in the previous FER (i.e. metadata URI). A possible evolution could be the JSON-LD enhancement, thus including the scheme within the same metadata JSON. With the transfer of the IPCHEM functionalities to the upcoming CPDC platform, the DCAT-AP scheme could be implemented through the dataset registration via the Data Provider Interface service of the data.europa.eu platform (https://dataeuropa.gitlab.io/data-provider-manual/data-provider-interface)." assertion.
- declaration considerations "Currently the link between metadata and data in IPCHEM is based on the unique identification codes of datasets in the platform, that can be used to identify harmonised data packages and specific records picked-up from the dataset console. Possible future implementation of DCAT in the context of CDPC." assertion.
- declaration considerations "Currently IPCHEM public dataset metadata are accessible through the public dataset package repository in the form of JSON files: ipchem.jrc.ec.europa.eu/public. Possible registry service implementation in the context of CDPC" assertion.
- declaration considerations "Currently IPCHEM public dataset packages are accessible through the public dataset package repository in the form of CSV (zip) files: ipchem.jrc.ec.europa.eu/public. Possible registry service implementation in the context of CDPC" assertion.