Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- 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.
- 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, the SPARQL communication protocol 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 "See F1 Data (i.e. URI FER)" assertion.
- declaration considerations "See F1 Data (i.e. URI FER)" assertion.
- declaration considerations "See F1 Data (i.e. URI FER)" assertion.
- declaration considerations "See F1 Data (i.e. URI FER)" assertion.
- declaration considerations "See F1 Data (i.e. URI FER)" assertion.
- declaration considerations "To be addressed in the context of CDPC" assertion.
- declaration considerations "Possible implementation in the context of CDPC" assertion.
- declaration considerations "Possible implementation in the context of CDPC" assertion.
- declaration considerations "Possible implementation in the context of CDPC" assertion.
- declaration considerations "Possible implementation in the context of CDPC" assertion.
- declaration considerations "Possible implementation in the context of CDPC" assertion.
- declaration considerations "Possible implementation in the context of CDPC" assertion.
- declaration considerations "Possible implementation in the context of CDPC" assertion.
- declaration considerations "Possible implementation in the context of CDPC" assertion.
- declaration considerations "Possible implementation in the context of CDPC" assertion.
- declaration considerations "Possible implementation in the context of CDPC" assertion.
- declaration considerations "Possible implementation in the context of CDPC" assertion.
- declaration considerations "Possible implementation in the context of CDPC" assertion.
- declaration considerations "Not explicitly stated in IPCHEM; However, in the JRC Data Catalogue the 'Use conditions' for AIRMEX are 'European Commission Reuse and Copyright Notice' (https://data.jrc.ec.europa.eu/licence/com_reuse). Maybe EUPL_1_2 is applicable as alternative (http://publications.europa.eu/resource/authority/licence/EUPL_1_2, https://opensource.org/license/eupl-1-2/)" assertion.
- declaration considerations "the usage license for datasets in IPCHEM is stated by the data provider in the participation form and in the metadata fiche" assertion.
- declaration considerations "The IPCHEM metadata fiche, in addition to the general description of the dataset, includes the following specific fields which aim to support its possible reuse: Monitoring reason(s), Sampling method(s), Analytical method(s), Responsible organization (name and PoC), Other Contributors, General Links, Linked resources about the data collection. Future DCAT-AP compliance is to be considered in the context of the CDPC." assertion.
- declaration considerations "Possible implementation in the context of CDPC" assertion.
- declaration considerations "The IPCHEM metadata fiche, in addition to the general description of the dataset, includes the following specific fields which aim to support its possible reuse: Monitoring reason(s), Sampling method(s), Analytical method(s), Responsible organization (name and PoC), Other Contributors, General Links, Linked resources about the data collection. Future DCAT-AP compliance is to be considered in the context of the CDPC" assertion.
- declaration considerations "Possible implementation in the context of CDPC" assertion.
- declaration considerations "Cost effective solution, our data portal requires lots of PIDs due to large number of digital objects." assertion.
- declaration considerations "Will be used to identify people." 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 "Widely used format in the community." 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 "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 "Most convenient protocol." 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 "Need internal one. Not yet implemented." assertion.
- declaration considerations "Standard." assertion.
- declaration considerations "Standard." assertion.
- declaration considerations "Best option." assertion.
- declaration considerations "Requirement." assertion.
- declaration considerations "Requirement." 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 "DOI are minted using the AERIS prefix" assertion.
- declaration considerations "Handle server hosted by AERIS with a prefix obtained from ePIC" assertion.
- declaration considerations "Automatic conversion from internal metadata format to Datacite" 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 "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 "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 "" 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 "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.