Frequently Asked Questions

It depends on what exactly you need. You can find a detailed explanation of mechanisms that can be used to achieve linked or hierarchical records that Invenio has or could have in the near future here .

No. While metadata models designed in DataSpecer  and represented in OWL or RDF provide useful semantic documentation, they must still be manually translated into the YAML model representation used by CESNET Invenio . For a detailed explanation on how to do so, see .

ORCID identifiers are not automatically validated (e.g. by a user signing in with their ORCID account or by a data curator). Similarly, DataCite does not validate whether submitted ORCID identifiers are correct. Given how the deposition workflow in Invenio works it does not make sense for ORCIDs in record metadata to be validated.

For legacy reasons Invenio displays a full green icon since the feature was implemented before ORCID changed it’s ORCID iD display guidlines  to using an icon with a green outline for unvalidated ORCID. The change in policy also states that the API should indicate that the ORCID iD is unverified which is a more involved change than just changing an icon. The change in policy has been acknowledged by the InvenioRDM team but not yet implemented and has a low priority.

Not yet. Support for additional persistent identifier types (such as Handles, ARK or ePIC) is possible and requested by multiple communities building upon CESNET Invenio. For more details see the Alternative PIDs section in CESNET Invenio Support for Linked and Hierarchical Records > Related Topics . For the latest roadmap and implementation status, see the Planned features  page.

Clearing your browser’s cookies and cache for the specific site often resolves sign-in issues. Below are instructions for the most commonly used browsers.

Google Chrome

1. Click the three-dot menu button in the top-right corner
2. Select Settings
3. Click Privacy and security in the left sidebar
4. Click Third-party cookies and other site data
5. Click See all site data and permissions
6. Search for or find the repository URL in the list
7. Click the trash icon next to it to delete its data

Mozilla Firefox

1. Click the menu button (three lines) in the top-right corner
2. Select Settings
3. Click Privacy & Security in the left sidebar
4. Scroll down to the Cookies and Site Data section
5. Click Manage Data
6. Search for the repository URL in the list
7. Select it and click Remove Selected

Microsoft Edge

1. Click the three-dot menu button in the top-right corner
2. Select Settings
3. Click Cookies and site permissions in the left sidebar
4. Click Manage cookies and site data
5. Search for or find the repository URL in the list
6. Click the trash icon next to it to delete its cookies

Safari (macOS)

1. Open Safari and click Safari in the menu bar
2. Select Settings (or Preferences on older versions)
3. Click the Privacy tab
4. Click Manage Website Data
5. Search for the repository URL in the list
6. Select it and click Remove
7. Click Done when finished

Safari (iOS/iPadOS)

1. Open Safari and tap the AA icon in the address bar
2. Tap Privacy Report, then Manage Website Data
3. Tap Edit in the top-right corner
4. Tap the red minus icon next to the repository URL
5. Tap Delete
6. Tap Done

Note: After clearing the site’s cookies, you may need to sign in again to your account.

Invenio primarily assigns roles to users relative to a community. The default community roles are defined by InvenioRDM as Owner, Manager, Curator and Reader. For more details, see the documentation . These roles are generally sufficient for most use cases but additional roles can also be defined.

CESNET Invenio offers more advanced role management as part of workflows, see the documentation .

There are also global repository roles that can be mapped to certain permissions, such as to access the repository administration panel, for example see Create administration group .

Partially. CESNET Invenio can consume external groups from Perun , which external systems can connect to — provided the service is set up to do so and the user consents to sharing their group membership with the service.

However, since CESNET Invenio 14, groups are no longer synchronized back to Perun. This means that changes made inside CESNET Invenio — e.g. adding or removing group members, or changing roles — will not be reflected in Perun, and therefore cannot be used for authorization in external systems.

The reason is technical: we cannot guarantee consistency between Invenio and Perun in all cases.

Yes. Starting with InvenioRDM 13, each community can have its own visual appearance (see Themed communities ). If stronger separation is required, repository teams can discuss the technical feasibility with the CESNET Invenio developers.

Yes. Records can be shared by link, or with specific users, even while still in draft, so reviewers can access data before it is published. For more details, see https://help.zenodo.org/docs/share/link-sharing/ .

Yes. Bulk ingestion through command-line tools or APIs is supported and is recommended for repositories that import large numbers of records or records with many and/or large files. For more detailed information, see the user guide. 

Uploading data directly to external data storage (such as NRP S3) is not supported. Instead, files should be uploaded through the repository API. The API uploads the files directly to S3 without storing them temporarily in local storage, so it should not significantly affect the upload speed.

Bulk imported records can subsequently be edited through the graphical user interface.