Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- 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 "We use DataCite and Schema.org for Argo data and metadata DOI" assertion.
- declaration considerations "Argo data and metadata are distributed with a CC-By license" 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 "The provenance information is recorded in Argo NetCDF implementation documented on http://dx.doi.org/10.13155/29825" 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." assertion.
- declaration considerations "No specific constraints related to UUID use. Limitation is about the incomplete production of metadata records" assertion.
- declaration considerations "Non-systematic and heterogeneous practice between platforms. Need for implementation support" assertion.
- declaration considerations "Non-systematic and heterogeneous practice between platforms. Need for implementation support" assertion.
- declaration considerations "Non-systematic usage among platforms IS." assertion.
- declaration considerations "Non-systematic usage among platforms IS." assertion.
- declaration considerations "Non-systematic usage among platforms IS." assertion.
- declaration considerations "DCAT-AP is intended to be the unifying profile in the ENVRI context. Starting state" 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 "no additional elements to report" assertion.
- declaration considerations "no additional elements to report" 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 "Preliminary state for an institutional repository 1) Open access for published data on Dataverse repository 2) Restricted access for contributors" assertion.
- declaration considerations "DMP not yet completed" assertion.
- declaration considerations "no additional elements to report" assertion.
- declaration considerations "Use in the AnaEE France community. Netcdf files are generated from the AnaEE semantic pipelines. Will be extended to other AnaEE european platforms" assertion.
- declaration considerations "Initially used in the AnaEE France community. To be extended to EU level" assertion.
- declaration considerations "Initially used in the AnaEE France community. Extended to the EU level" assertion.
- declaration considerations "INSPIRE compliance and metadata catalogue interoperability" assertion.
- declaration considerations "no additional elements to report" assertion.
- declaration considerations "no additional elements to report" assertion.
- declaration considerations "no additional elements to report" assertion.
- declaration considerations "Not yet implemented. Preliminary work in 2021" 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 "" assertion.
- declaration considerations "" 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 "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 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.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "We use the ISO 19139:2007 profile for several kinds of resources (e.g., services, workflows, virtual research environments, etc.)" assertion.
- declaration considerations "We use the EML 2.2.0 standard for datasets metadata records." assertion.
- declaration considerations "The LifeWatch ERIC UPper Ontology (LUPO) defines the core set of LifeWatch ERIC elements." 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 models, schemas used for datasets depend on the LifeWatch ERIC national node. Some examples are DwC-A, NetCDF, etc." assertion.
- declaration considerations "The models, schemas used for datasets depend on the LifeWatch ERIC national node. Some examples are DwC-A, NetCDF, etc." assertion.
- declaration considerations "Metadata records can be accessed and downloaded with a CC0 license both on LifeWatch ERIC Metadata Catalogue and on EcoPortal." assertion.
- declaration considerations "A mixture between mostly CC-BY, CC-0 and CC-BY-NC is used, it depends on the LifeWatch ERIC national node." assertion.
- declaration considerations "A mixture between mostly CC-BY, CC-0 and CC-BY-NC is used, it depends on the LifeWatch ERIC national node." assertion.
- declaration considerations "A mixture between mostly CC-BY, CC-0 and CC-BY-NC is used, it depends on the LifeWatch ERIC national node." assertion.
- declaration considerations "A Handle PID is going to be assigned to all data products and instruments" assertion.
- declaration considerations "DataCite DOI is going to be assigned to data collections" assertion.
- declaration considerations "It will be used to identify people " assertion.
- declaration considerations "A Handle PID is going to be assigned to all data products and instruments" assertion.
- declaration considerations "DataCite DOI is going to be assigned to data collections" assertion.
- declaration considerations "DataCite metadata schema is going to be used for data collections" assertion.
- declaration considerations "All our (meta)data are NetCDF 1.7 compliant. The definition of new CF variable names has been approved by the CF community" assertion.
- declaration considerations "Under discussion" assertion.
- declaration considerations "Collections of data" assertion.
- declaration considerations "Data products and instruments" assertion.