Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "Description was implemented as a prototype exercise in ENVRI." assertion.
- declaration considerations "The metadata is always connected to/or part of the respective datasets." assertion.
- declaration considerations "Analysed data inserted in Madrigal are also indexed by experiment in https://handle.eiscat.se:8000" assertion.
- declaration considerations "Decision on implementation depends on EISCAT_3D development. " assertion.
- declaration considerations "There's no metadata-data linking schema used. Metadata is usually part of the dataset (in case of Level 3 data in Madrigal the metadata is part of the HDF5 file, in the case of L1 and L2 data, metadata is part of the dataset download)." assertion.
- declaration considerations "Use has been evaluated in EUDAT prototype project. It is planned to come to use with EISCAT_3D data." assertion.
- declaration considerations "EISCAT is a PITHIA-NRF Node, metadata for EISCAT datasets will be registered and findable through the PITHIA-NRF e-science centre search engine." assertion.
- declaration considerations "This is a legacy system that will be merged with the EISCAT_3D data portal in the future. Implementation TBD." assertion.
- declaration considerations "Madrigal has served well for distributing analysed data from the legacy systems and will remain used for that purpose. However, it will not be used with EISCAT_3D data." assertion.
- declaration considerations "The EISCAT Schedule provides a human readable overview of experiments and their archived data. Madrigal also provides a machine actionable web service API." assertion.
- declaration considerations "Existing EISCAT datasets are downloadable through web services or commands such as wget and curl. Plain text http is being replaced by https." assertion.
- declaration considerations "For L1 and L2 data, metadata is openly accessible through EISCAT portal page https://portal.eiscat.se/ Detailed experiment description files are included with dataset download and can be downloaded separately as well. For L3 data in Madrigal database the metadata is publicly accessible and Madrigal database has also available interaction through an API." 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 "EISCAT Blue book describes the governing rules of the EISCAT Scientific Association and is agreed on by all EISCAT Associates." assertion.
- declaration considerations "Decision on implementation depends on EISCAT_3D development. " assertion.
- declaration considerations "Decision on implementation depends on EISCAT_3D development. " assertion.
- declaration considerations "EISCAT is a PITHIA-NRF node. Part of PITHIA-NRF project is the development of a common ontology for data from the upper atmosphere to the near-Earth space region, where EISCAT operates. " assertion.
- declaration considerations "EISCAT is a PITHIA-NRF node; this ontology is planned for use in the PITHIA-NRF e-science centre search engine." 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 "This scheme will be used in HDF5 files for L1 and L2 EISCAT data. The conversion implementation at present is pending and depends on EISCAT_3D development." 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 "Metadata is freely available for usage. No license is specifically stated." assertion.
- declaration considerations "EISCAT Bluebook describes the governing rules of the EISCAT Scientific Association and is agreed on by all EISCAT Associates. EISCAT Data Policy is part of these rules." assertion.
- declaration considerations "DataCite scheme is used for analysed (L3) data in the madrigal database. " assertion.
- declaration considerations "L1 and L2 data, available through the EISCAT portal webpage, are planned to be converted to HDF5 files with DataCite metadata scheme records once a unified form for EISCAT_3D purposes is decided." assertion.
- declaration considerations "Description was implemented as a prototype exercise in ENVRI." assertion.
- declaration considerations "DataCite scheme is used for analysed (L3) data in the madrigal database. L1 and L2 data, available through the EISCAT portal webpage, are planned to be converted to HDF5 files with DataCite metadata scheme records once a unified form for EISCAT_3D purposes is decided." assertion.
- declaration considerations "" assertion.
- declaration considerations "Availability (in contrast to DOIs), easy maintenance of local handle server, etc" assertion.
- declaration considerations "Standard, compatibility with B2FIND harvesting, etc" assertion.
- declaration considerations "Standard, compatibility with B2FIND harvesting, etc" 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 "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 "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 "EISCAT_3D is in the commission phase, and is expected to deliver first data late 2023" assertion.
- declaration considerations "EISCAT_3D is in the commission phase, and is expected to deliver first data late 2023" assertion.
- declaration considerations "Available identity providers of all EISCAT users, including those in China and Japan, must be federated." assertion.
- declaration considerations "Available identity providers of all EISCAT users, including those in China and Japan, must be federated." assertion.
- declaration considerations "Available identity providers of all EISCAT users, including those in China and Japan, must be federated." assertion.
- declaration considerations "Available identity providers of all EISCAT users, including those in China and Japan, must be federated." assertion.
- declaration considerations "Available identity providers of all EISCAT users, including those in China and Japan, must be federated." assertion.
- declaration considerations "Available identity providers of all EISCAT users, including those in China and Japan, must be federated." assertion.
- declaration considerations "An old de facto standard among incoherent scatter radars and other upper atmospheric instruments." assertion.
- declaration considerations "MADRIGAL data are archived in a legacy binary format. Transfer to a HDF5 based standard is going on." assertion.
- declaration considerations "MADRIGAL data are archived in a legacy binary format. Transfer to a HDF5 based standard is going on." assertion.
- declaration considerations "Agreed by EISCAT Associates." assertion.
- declaration considerations "Agreed by EISCAT Associates." assertion.
- declaration considerations "Description was implemented as a prototype exercise in ENVRI." assertion.
- declaration considerations "The DOIs are the best way to permanently identify a given digital object, in a format controlled by the International DOI Foundation. We have an agreement with DataCite and this will guarantee the cross-domain findability. When a DOI is not available, users can specify a persistent internal identifier." assertion.
- declaration considerations "The DOIs are the best way to permanently identify a given digital object, in a format controlled by the International DOI Foundation. We have an agreement with DataCite and this will guarantee the cross-domain findability. When a DOI is not available, users can specify a persistent internal identifier." assertion.
- declaration considerations "We use the ISO 19139:2007 profile for several kinds of metadata resources, that are: services, workflows, virtual research environments, and research sites." assertion.
- declaration considerations "We use the EML 2.2.0 standard for datasets metadata records." assertion.
- declaration considerations "We have an agreement with DataCite." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue is based on GeoNetwork 3.10, that has been customized according to our different needs and requirements. It allows to manage and publish metadata records of five types of digital resources, that are research sites, datasets, services, workflows, and Virtual Research Environments. LifeWatch ERIC is a direct member of DataCite and it can provide a Digital Object Identifier (DOI) for metadata records that do not have it, taking advantage of the GeoNetwork – DataCite connection." assertion.
- declaration considerations "EcoPortal is based on OntoPortal Virtual Appliance, version 3.1.1 that has been customized according to our different needs and requirements. It is a repository for semantic resources in the ecological domain, for different kinds of stakeholders (researchers, vocabularies managers, data managers, ontologists, etc.). EcoPortal supports the community in the creation, management, mapping and alignment of its semantic resources and subsequently also of its data. LifeWatch ERIC is a direct member of DataCite and it can provide a Digital Object Identifier (DOI) for semantic resources that do not have it, taking advantage of the EcoPortal – DataCite connection." assertion.
- declaration considerations "It represents the search engine of DataCite (https://search.datacite.org), hence it allows to find, access and reuse all LifeWatch ERIC research digital objects that have a DOI. " assertion.
- declaration considerations "Being the LifeWatch ERIC Metadata Catalogue published online, Google automatically indexes its main pages. " assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue is based on GeoNetwork 3.10, that has been customized according to our different needs and requirements. It allows to manage and publish dataset metadata records and to provide a Digital Object Identifier (DOI) when needed, taking advantage of the GeoNetwork – DataCite connection. The dataset metadata records are automatically harvested by the LifeWatch ERIC national nodes data repositories (e.g., LifeWatch Italy: https://dataportal.lifewatchitaly.eu/data; LifeWatch Belgium: https://www.lifewatch.be/en/data; LifeWatch Portugal and Greece: http://ipt.gbif.pt/ipt/; etc.)." assertion.
- declaration considerations "It represents the search engine of DataCite (https://search.datacite.org), hence it allows to find, access and reuse all LifeWatch ERIC research digital objects that have a DOI. " assertion.
- declaration considerations "Being the LifeWatch ERIC Metadata Catalogue published online, Google automatically indexes its main pages. " assertion.
- declaration considerations "It represents the standard de facto as secure communication protocol." assertion.
- declaration considerations "It represents the standard de facto as secure communication protocol." assertion.
- declaration considerations "Metadata records are freely accessible in the LifeWatch ERIC Metadata Catalogue and in EcoPortal, hence no login is required. The authentication and authorization are needed to add and manage metadata records and resources and currently are performed by using a traditional login mechanism that identifies and authenticates users through the couple of credentials (username and password). We are developing the Keycloak Single-Sign On that will allow to login with different identity providers (e.g., Google, ORCID, etc.). " assertion.
- declaration considerations "Dataset metadata records are freely accessible in the LifeWatch ERIC Metadata Catalogue, hence no login is required. The authentication and authorization are needed to add and manage dataset metadata records and currently are performed by using a traditional login mechanism that identifies and authenticates users through the couple of credentials (username and password). We are developing the Keycloak Single-Sign On that will allow to login with different identity providers (e.g., Google, ORCID, etc.). To access datasets, the authentication & authorisation service depends on the LifeWatch ERIC national node." assertion.
- declaration considerations "A metadata longevity plan is still under definition." assertion.
- declaration considerations "RDF schema is actually in improvement status in the LifeWatch ERIC Metadata Catalogue to describe the metadata of all LifeWatch ERIC resources (e.g., datasets, services, Virtual Research Environments, workflows, research sites)." assertion.
- declaration considerations "The XML allows us to exchange metadata records among distributed sources. This format is used to download metadata records both in the LifeWatch ERIC Metadata Catalogue and EcoPortal." assertion.
- declaration considerations "EcoPortal API returns JSON as the default content type." assertion.
- declaration considerations "The knowledge representation languages used for datasets depend on the LifeWatch ERIC national node. Some examples are XMLS, CSV, DwC-A, NetCDF, etc." assertion.
- declaration considerations "The knowledge representation languages used for datasets depend from the LifeWatch ERIC national node. Some examples are XMLS, CSV, DwC-A, NetCDF, etc." assertion.
- declaration considerations "The knowledge representation languages used for datasets depend from the LifeWatch ERIC national node. Some examples are XMLS, CSV, DwC-A, NetCDF, etc." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node." assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node." assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.