Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- 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.
- 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.
- 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.
- 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.
- 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.
- declaration considerations "Used in GloBI" assertion.
- declaration considerations "Used in GloBI" 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.