Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- 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 "The architecture of the dataset schema fits with the metadata that we wish to create for our resource. " assertion.
- declaration considerations "The architecture of the data base matching the data schema." assertion.
- declaration considerations "The architecture of the data base matching the data schema." assertion.
- declaration considerations "The architecture of the data base matching the data schema." assertion.
- declaration considerations "The architecture of the data base matching the data schema." assertion.
- declaration considerations "The architecture of the data base matching the data schema." assertion.
- declaration considerations "The architecture of the data base matching the data schema." assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "We want to provide an unrestricted access to the data" assertion.
- declaration considerations "We want to provide an unrestricted access to the data" assertion.
- declaration considerations "We want to provide an unrestricted access to the data" assertion.
- declaration considerations "We want to provide an unrestricted access to the data" assertion.
- declaration considerations "We want to provide an unrestricted access to the data" assertion.
- declaration considerations "We want to provide an unrestricted access to the data" assertion.
- declaration considerations "We want to provide an unrestricted access to the data" assertion.
- declaration considerations "We want to provide an unrestricted access to the data" assertion.
- declaration considerations "We want to provide an unrestricted access to the data" assertion.
- declaration considerations "We want to provide an unrestricted access to the data" assertion.
- declaration considerations "We want to provide an unrestricted access to the data" assertion.
- declaration considerations "We want to provide an unrestricted access to the data" assertion.
- declaration considerations "We want to provide an unrestricted access to the data" assertion.
- declaration considerations "Unique identifiers for datasets" assertion.
- declaration considerations "Unique identification of data providers." assertion.
- declaration considerations "Unique identification of provider's institution." assertion.
- declaration considerations "eNanoMapper DB and project-specific DBs based on eNanoMapper (NANoREG, Nanoreg2,...)" assertion.
- declaration considerations "OpenTox API " assertion.
- declaration considerations "Unique identification of provider's institution promoted by RDA." assertion.
- declaration considerations "Besides the InChI itself, the InChI for nano (NInChI) is currently under development in the nanosafety community." assertion.
- 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 "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 "under development" assertion.
- declaration considerations "under development" assertion.