Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- 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 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 "We don't use a metadata schema for describing the provenance of our metadata records at the moment." assertion.
- declaration considerations "We don't use a metadata schema for describing the provenance of our datasets at the moment." assertion.
- declaration considerations "The community often uses DOI for the reference of research outputs. " assertion.
- declaration considerations "The community is using the Handle system. " assertion.
- declaration considerations "ORCID has been widely adapted by members of the community. " assertion.
- declaration considerations "Considering that DOI is not very well used in the community yet, we assert that DOI wil be used in the future. " assertion.
- declaration considerations "The Handle sytem is being used by researchers in the community. " assertion.
- declaration considerations "DDI is used by researchers in the community. " assertion.
- declaration considerations "MARC21 is used by the community. It was newly added to the FIP Wizard as a FER. " assertion.
- declaration considerations "EAD 3 was used researchers in the community. It was newly added to the FIP Wizard as a FER. " assertion.
- declaration considerations "EAD 3 was used researchers in the community. It was newly added to the FIP Wizard as a FER. " assertion.
- declaration considerations "DOI is used to link metadata with data." assertion.
- declaration considerations "The Handle is used to link metadata with data." assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "Dataverse is being used in the project. " assertion.
- declaration considerations "The community is going to use it in the future. " assertion.
- declaration considerations "OAI-PMH is used in the community." assertion.
- declaration considerations "HTTPS is well used in the community. " assertion.
- declaration considerations "REST API is being used in the community. " assertion.
- declaration considerations "REST API is being used. " assertion.
- declaration considerations "HTTPS is being used in the community. " assertion.
- declaration considerations "OAI-PMH is being used. " assertion.
- declaration considerations "HTTPS is being used by the community. " assertion.
- declaration considerations "SWORD is being used in the community." assertion.
- declaration considerations "SWORD is being used in the community." assertion.
- declaration considerations "It's used in the community. " assertion.
- declaration considerations "RDF is well used. " assertion.
- declaration considerations "OWL is well used." assertion.
- declaration considerations "RDFS is well used in the community." assertion.
- declaration considerations "Use by the community." assertion.
- declaration considerations "OWL is well used. " assertion.
- declaration considerations "RDF is well used. " assertion.
- declaration considerations "RDFS is well used. " assertion.
- declaration considerations "XML Schema is being used in the community. " assertion.
- declaration considerations "HTML is widely used in the community. " assertion.
- declaration considerations "DCAT2." assertion.
- declaration considerations "DCAT2." assertion.
- declaration considerations "DCAT2." assertion.
- declaration considerations "HISCO is being maintained at IISG and being used. " assertion.
- declaration considerations "AMCO is being used. " assertion.
- declaration considerations "AMCO is being used in the community." assertion.
- declaration considerations "" assertion.
- declaration considerations "IDS is being used by the community." assertion.
- declaration considerations "IDS is being used by the community" assertion.
- declaration considerations "There are plans to use it in the future. " assertion.
- declaration considerations "This has not been specified in the interview. " assertion.
- declaration considerations "Used in the community. " assertion.
- declaration considerations "Not as well used in the community. " assertion.
- declaration considerations "DCAT2 is not of this type in the system. Chose DCAT3 for now. " assertion.