Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- 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 "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.
- declaration considerations "The Argo DOI representation language is compliant with DataCite RDF schema and RDF Schema.org " assertion.
- declaration considerations "The Argo DOI representation language is compliant with DataCite RDF schema and RDF Schema.org " assertion.
- declaration considerations "The Argo community decided 20 years ago to distribute data and metadata in NetCDF files. The Argo NetCDF format is regularly improved." assertion.
- declaration considerations "Argo metadata such as sensor type, history records are recorded in Argo NetCDF self descriptive variables. The controlled vocabularies are published on NVS vocab server." assertion.
- declaration considerations "The Argo vocabularies used in NetCDF files are published on NVS vocab server" assertion.
- 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 "DCAT-AP is intended to be the unifying profile in the ENVRI context." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "GeoNetwork, in use in the AnaEE France community." assertion.
- declaration considerations "GeoNetwork, in use in the AnaEE France community." 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 by the AnaEE France community. To be extended to 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." 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 "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 "5 years min. as defined in the ACTRIS DMP" 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 "ACTRIS vocabulary has been published" assertion.
- declaration considerations "Ongoing submission of missing names" 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 "ACTRIS recommendation" assertion.
- declaration considerations "ACTRIS recommendation" assertion.
- declaration considerations "Will follow ENVRI-FAIR recommendations" assertion.
- declaration considerations "Will follow ENVRI-FAIR recommendations" 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 (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 "We have an agreement with DataCite." assertion.
- declaration considerations "Being the LifeWatch ERIC Metadata Catalogue published online, Google automatically indexes its main pages. " assertion.
- declaration considerations "It represents the search engine of DataCite (https://search.datacite.org), hence it allows to find, access and reuse all Life" assertion.
- declaration considerations "Being the LifeWatch ERIC Metadata Catalogue published online, Google automatically indexes its main pages. " 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 "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, based on GeoNetwork, hence no login is required. The authentication and authorization are needed to add and manage 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). It will adopt the SAML 2.0 protocol, with a multifactor authentication and is going to analyse the OAUTH infrastructure (analysis of providers, costs, issues, etc.)." assertion.
- declaration considerations "The authentication & authorisation technique for datasets depends from the LifeWatch ERIC national node. For example, in some cases the access through ORCID is currently used, in other cases the traditional login mechanism that identifies and authenticates users through the couple of credentials (username and password) is used." assertion.
- declaration considerations "The authentication & authorisation technique for datasets depends from the LifeWatch ERIC national node. For example, in some cases the access through ORCID is currently used, in other cases the traditional login mechanism that identifies and authenticates users through the couple of credentials (username and password) is used." 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." 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 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.