Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "The community would like to establish a mechanism to cite data(sets) in scientific publication to better show the value of data and increase the incentive to make it publicly available. DOIs, often in addition to data warehouse specific unique identifiers, will help with that since they put the datasets on the same level as other citations. " assertion.
- declaration considerations "Database specific identifiers" assertion.
- declaration considerations "Used to get the DOIs" assertion.
- declaration considerations "Currently mainly used to annotate websites with training contents. Schema.org and bioschemas.org is proposed to be used more wildly. " assertion.
- declaration considerations "Implementation was tested in the prototype combining institutional repositories and nano-specific warehouses." assertion.
- declaration considerations "Implementation was tested in the prototype combining institutional repositories and nano-specific warehouses." assertion.
- declaration considerations "Use for physics-based models and in combination with QMRF and CHADA to cover integrated approaches (characterisation and data-driven / physics-based modelling)." assertion.
- declaration considerations "Use for physicochemical characterisation data and in combination with QMRF and MODA to cover integrated approaches (characterisation and data-driven / physics-based modelling)." assertion.
- declaration considerations "Use for data-driven models and in combination with CHADA and MODA to cover integrated approaches (characterisation and data-driven / physics-based modelling)." assertion.
- declaration considerations "Besides the InChI itself, the InChI for nano (NInChI) is currently under development in the nanosafety community." assertion.
- declaration considerations "Besides the InChI itself, the InChI for nano (NInChI) is currently under development in the nanosafety community." assertion.
- declaration considerations "Possibility to get DOI for (meta)data" assertion.
- declaration considerations "Indexing of data from the NanoCommons data warehouse and other nano-specific databases implemented as part of the NanoCommons project." assertion.
- declaration considerations "Promoted as one way to make data better findable. However, this leads to data duplication which should be avoided by the generally agreed nano-specific solution integrated into the European data ecosystem." assertion.
- declaration considerations "Similar to institutional repositories, this listing needs to be integrated into (or even replaced by) a more general solution. Even if this might be helpful for getting datasets provided e.g. as supporting material of scientific publications into this general solution, the need to curate the metadata manually limits the available entries. " assertion.
- declaration considerations "Promoted as one way to make data better findable. However, this leads to data duplication which should be avoided by the generally agreed nano-specific solution integrated into the European data ecosystem." assertion.
- declaration considerations "Database provided by the NanoCommons project to host data from many different EU funded projects." assertion.
- declaration considerations "Database provided by the eNanoMapper project to host data from many different EU funded projects." assertion.
- declaration considerations "Database specifically designed to provide data for model development and nanoinfomatics applications" assertion.
- declaration considerations "Work on harmonisation of REST APIs provided by data warehouses and modelling tools was done in eNanoMapper, OpenRiskNet and NanoCommons / some SOAP APIs are also available / data access from many databases as HTML" assertion.
- declaration considerations "Mainly used for omics and MS data to upload and access data from standards (not-nano-specific) databases." assertion.
- declaration considerations "Work on harmonisation of REST APIs provided by data warehouses and modelling tools was done in eNanoMapper, OpenRiskNet and NanoCommons / some SOAP APIs are also available / data access from many databases as HTML" assertion.
- declaration considerations "To my knowledge is this the underlying mechanism of the EOSC and ELIXIR A&A" assertion.
- declaration considerations "Used in the OpenRiskNet project, which was partly based on Red Hat sponsored services." assertion.
- declaration considerations "Data and metadata are accessed using the same A&A mechanisms." assertion.
- declaration considerations "Data and metadata are accessed using the same A&A mechanisms." assertion.
- declaration considerations "Data and metadata are accessed using the same A&A mechanisms." assertion.
- declaration considerations "Use to represent the eNanoMapper ontology." assertion.
- declaration considerations "Different RDF data source exist." assertion.
- declaration considerations "JSON-LD is used to annotate API results in different modelling tools (started in OpenRiskNet)" assertion.
- declaration considerations "See Declaration I1a." assertion.
- declaration considerations "See Declaration I1a." assertion.
- declaration considerations "See Declaration I1a." assertion.
- declaration considerations "Major activity of the nanosafety community to cover all data for risk assessment." assertion.
- declaration considerations "Better alignment with the material modelling and characterisation communities is needed, which might be supported by the adoption of the EMMO. However, clearer concepts how to annotate the MODA/CHADA reporting standards, potentially as part of the iMODA/iCHADA developments, need to be developed. " assertion.
- declaration considerations "See Declaration I2a." assertion.
- declaration considerations "See Declaration I2a." assertion.
- declaration considerations "See Declaration I2a." assertion.
- declaration considerations "See Declaration I2a." assertion.
- declaration considerations "This is the recommended license. However, journals and some databases might allow or require other licenses. Additionally, embargo periods are often enforced." assertion.
- declaration considerations "This is the recommended license. However, journals and some databases might allow or require other licenses. Additionally, embargo periods are often enforced." assertion.
- declaration considerations "This is the recommended license. However, journals and some databases might allow or require other licenses. Additionally, embargo periods are often enforced." assertion.
- declaration considerations "This is the recommended license. However, journals and some databases might allow or require other licenses. Additionally, embargo periods are often enforced." assertion.
- declaration considerations "" assertion.
- declaration considerations "The implementation was made on the data-related needs of the nanosafety and nanomaterials community for high-quality datasets in a ready-for-modelling format for direct import into computational workflows. " assertion.
- declaration considerations "Datasets are linked to their metadata via their respective peer-reviewed publications." assertion.
- declaration considerations "As of now, no specific implementation has been made due to the different requirements of the computational scientists / modellers." assertion.
- declaration considerations "Datasets are linked to their metadata via their respective peer-reviewed publications." assertion.
- declaration considerations "The NanoPharos database provides access to ready-for-modelling datasets for direct import into computational workflows, which are directly linked to their respective peer-reviewed publications for metadata retrieval." assertion.
- declaration considerations "The NanoPharos database provides public access to ready-for-modelling datasets for direct import into computational workflows, which are directly linked to their respective peer-reviewed publications for metadata retrieval." assertion.
- declaration considerations "The NanoPharos database is publicly accessible via it's dedicated URL." assertion.
- declaration considerations "A REST API will be implemented for retrieving and submitting data to the database." assertion.
- declaration considerations "Datasets are publicly available for access and download via a dedicated link." assertion.
- declaration considerations "No specific authentication & authorisation services are currently used as the datasets are publicly available and linked to the respective publications. Direct links to the peer-reviewed publications are provided for metadata retrieval, but these are handled by the journals." assertion.
- declaration considerations "No specific authentication & authorisation services are currently used as the datasets are publicly available and linked to the respective publications. Direct links to the peer-reviewed publications are provided for metadata retrieval, but these are handled by the journals." assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "Metadata are linked to their respective peer-reviewed publicatios, thus the licensing is handled by these. Any metadata available in NanoPharos are available by a CC-BY 4.0 license." assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "ORCIDs may be provided as a link that resolves to a researcher's ORCID page, but it must be typed into the metadata by the depositor. Metadata is not pushed to the researcher's ORCID page by the Repository, though we may provide this in the future." assertion.
- declaration considerations "ORCIDs may be provided as a link that resolves to a researcher's ORCID page, but it must be typed into the metadata by the depositor. Metadata is not pushed to the researcher's ORCID page by the Repository, though we may provide this in the future." assertion.
- declaration considerations "ORCIDs may be provided as a link that resolves to a researcher's ORCID page, but it must be typed into the metadata by the depositor. Metadata is not pushed to the researcher's ORCID page by the Repository, though we may provide this in the future." assertion.
- declaration considerations "DOIs resolve to a metadata landing page as per recommended practice. Content is accessible from the landing page either in-browser or as downloadable content." assertion.
- declaration considerations "DOIs resolve to a metadata landing page as per recommended practice. Content is accessible from the landing page either in-browser or as downloadable content." assertion.
- declaration considerations "MODS records cannot be entered manually as part of the Repository deposit process, but batch uploads of MODS records are possible. In those circumstances, MODS is both mapped to Dublin Core for display and available to download as XML. These records are included in the Repository search function." assertion.
- declaration considerations "Both simple and qualified Dublin Core are used." assertion.
- declaration considerations "This metadata schema is used for the purposes of aggregating metadata from DRI to Europeana, not for ingest into the Repository. Much of the Repository's content is discoverable through the Europeana platform." assertion.
- declaration considerations "EAD records cannot be entered manually as part of the Repository deposit process, but batch uploads of EAD records are possible. In those circumstances, EAD is both mapped to Dublin Core for display and available to download as XML. These records are included in the Repository search function." assertion.
- declaration considerations "MARCXML records cannot be entered manually as part of the Repository deposit process, but batch uploads of MARCXML records are possible. In those circumstances, MARCXML is both mapped to Dublin Core for display and available to download as XML. These records are included in the Repository search function." assertion.
- declaration considerations "MODS records cannot be entered manually as part of the Repository deposit process, but batch uploads of MODS records are possible. In those circumstances, MODS is both mapped to Dublin Core for display and available to download as XML. These records are included in the Repository search function." assertion.
- declaration considerations "MODS records cannot be entered manually as part of the Repository deposit process, but batch uploads of MODS records are possible. In those circumstances, MODS is both mapped to Dublin Core for display and available to download as XML. These records are included in the Repository search function." assertion.
- declaration considerations "DRI is the Irish national metadata aggregator for Europeana." assertion.
- declaration considerations "DRI is the Irish national metadata aggregator for Europeana." assertion.
- declaration considerations "DRI is the Irish national metadata aggregator for Europeana." assertion.
- declaration considerations "OAI-PMH is used for harvesting." assertion.
- declaration considerations "OAI-PMH is used for harvesting." assertion.
- declaration considerations "OAI-PMH is used for harvesting." assertion.
- declaration considerations "OAI-PMH is used for harvesting." assertion.
- declaration considerations "The DRI allows the depositor to set access restrictions on their data. Data can be available publicly, to logged-in users only, or restricted to named individuals (see the Restricted Data Policy). DRI also enables restriction of access to those with Edugate usernames and passwords. These access restrictions are implemented via a custom user and groups code library developed by DRI which stores the permissions as technical metadata alongside each object or collection (this technical metadata can be accessed only by the developer team). Users may request access to data via the web interface." assertion.
- declaration considerations "The DRI allows the depositor to set access restrictions on their data. Data can be available publicly, to logged-in users only, or restricted to named individuals (see the Restricted Data Policy). DRI also enables restriction of access to those with Edugate usernames and passwords. These access restrictions are implemented via a custom user and groups code library developed by DRI which stores the permissions as technical metadata alongside each object or collection (this technical metadata can be accessed only by the developer team). Users may request access to data via the web interface." assertion.
- declaration considerations "The DRI allows the depositor to set access restrictions on their data. Data can be available publicly, to logged-in users only, or restricted to named individuals (see the Restricted Data Policy). DRI also enables restriction of access to those with Edugate usernames and passwords. These access restrictions are implemented via a custom user and groups code library developed by DRI which stores the permissions as technical metadata alongside each object or collection (this technical metadata can be accessed only by the developer team). Users may request access to data via the web interface." assertion.
- declaration considerations "The DRI allows the depositor to set access restrictions on their data. Data can be available publicly, to logged-in users only, or restricted to named individuals (see the Restricted Data Policy). DRI also enables restriction of access to those with Edugate usernames and passwords. These access restrictions are implemented via a custom user and groups code library developed by DRI which stores the permissions as technical metadata alongside each object or collection (this technical metadata can be accessed only by the developer team). Users may request access to data via the web interface." assertion.
- declaration considerations "The DRI allows the depositor to set access restrictions on their data. Data can be available publicly, to logged-in users only, or restricted to named individuals (see the Restricted Data Policy). DRI also enables restriction of access to those with Edugate usernames and passwords. These access restrictions are implemented via a custom user and groups code library developed by DRI which stores the permissions as technical metadata alongside each object or collection (this technical metadata can be accessed only by the developer team). Users may request access to data via the web interface." assertion.
- declaration considerations "The DRI allows the depositor to set access restrictions on their data. Data can be available publicly, to logged-in users only, or restricted to named individuals (see the Restricted Data Policy). DRI also enables restriction of access to those with Edugate usernames and passwords. These access restrictions are implemented via a custom user and groups code library developed by DRI which stores the permissions as technical metadata alongside each object or collection (this technical metadata can be accessed only by the developer team). Users may request access to data via the web interface." assertion.
- declaration considerations "The DRI allows the depositor to set access restrictions on their data. Data can be available publicly, to logged-in users only, or restricted to named individuals (see the Restricted Data Policy). DRI also enables restriction of access to those with Edugate usernames and passwords. These access restrictions are implemented via a custom user and groups code library developed by DRI which stores the permissions as technical metadata alongside each object or collection (this technical metadata can be accessed only by the developer team). Users may request access to data via the web interface." assertion.
- declaration considerations "The DRI allows the depositor to set access restrictions on their data. Data can be available publicly, to logged-in users only, or restricted to named individuals (see the Restricted Data Policy). DRI also enables restriction of access to those with Edugate usernames and passwords. These access restrictions are implemented via a custom user and groups code library developed by DRI which stores the permissions as technical metadata alongside each object or collection (this technical metadata can be accessed only by the developer team). Users may request access to data via the web interface." assertion.
- declaration considerations "The DRI allows the depositor to set access restrictions on their data. Data can be available publicly, to logged-in users only, or restricted to named individuals (see the Restricted Data Policy). DRI also enables restriction of access to those with Edugate usernames and passwords. These access restrictions are implemented via a custom user and groups code library developed by DRI which stores the permissions as technical metadata alongside each object or collection (this technical metadata can be accessed only by the developer team). Users may request access to data via the web interface." assertion.
- declaration considerations "The DRI allows the depositor to set access restrictions on their data. Data can be available publicly, to logged-in users only, or restricted to named individuals (see the Restricted Data Policy). DRI also enables restriction of access to those with Edugate usernames and passwords. These access restrictions are implemented via a custom user and groups code library developed by DRI which stores the permissions as technical metadata alongside each object or collection (this technical metadata can be accessed only by the developer team). Users may request access to data via the web interface." assertion.
- declaration considerations "The DRI allows the depositor to set access restrictions on their data. Data can be available publicly, to logged-in users only, or restricted to named individuals (see the Restricted Data Policy). DRI also enables restriction of access to those with Edugate usernames and passwords. These access restrictions are implemented via a custom user and groups code library developed by DRI which stores the permissions as technical metadata alongside each object or collection (this technical metadata can be accessed only by the developer team). Users may request access to data via the web interface." assertion.
- declaration considerations "The DRI allows the depositor to set access restrictions on their data. Data can be available publicly, to logged-in users only, or restricted to named individuals (see the Restricted Data Policy). DRI also enables restriction of access to those with Edugate usernames and passwords. These access restrictions are implemented via a custom user and groups code library developed by DRI which stores the permissions as technical metadata alongside each object or collection (this technical metadata can be accessed only by the developer team). Users may request access to data via the web interface." assertion.