Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- 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.
- 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 "This license is required for metadata published to Europeana." assertion.
- declaration considerations "This license is required for metadata published to Europeana." assertion.
- declaration considerations "This license is required for metadata published to Europeana." assertion.
- declaration considerations "This license is required for metadata published to Europeana." assertion.
- declaration considerations "This license is required for metadata published to Europeana." assertion.
- declaration considerations "This license is required for metadata published to Europeana." assertion.
- declaration considerations "This license is required for metadata published to Europeana." assertion.
- declaration considerations "This license is required for metadata published to Europeana." assertion.
- declaration considerations "This license is required for metadata published to Europeana." assertion.
- declaration considerations "This license is required for metadata published to Europeana." assertion.
- declaration considerations "This license is required for metadata published to Europeana." assertion.
- declaration considerations "This captures and creates preservation metadata after content has entered the repository." assertion.
- declaration considerations "This captures and creates preservation metadata after content has entered the repository." assertion.
- declaration considerations "This captures and creates preservation metadata after content has entered the repository." assertion.
- declaration considerations "This captures and creates preservation metadata after content has entered the repository." assertion.
- declaration considerations "DOI comprises data and metadata as a package" 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 "" assertion.
- declaration considerations "" assertion.
- declaration considerations "Everyone is allowed to see and access metadata without restriction" assertion.
- declaration considerations "Everyone is allowed to see and access metadata without restriction" assertion.
- declaration considerations "Everyone is allowed to see and access metadata without restriction at GloBI" assertion.
- declaration considerations "Everyone is allowed to see and access metadata without restriction at GloBI" assertion.
- declaration considerations "Everyone is allowed to see and access metadata without restriction at GloBI" assertion.
- declaration considerations "Everyone is allowed to see and access metadata without restriction at GloBI" assertion.
- declaration considerations "Everyone is allowed to see and access metadata without restriction at GloBI" assertion.