See our project board on GitHub
Done 🚀
What we have recently completed
Files
Support for multipart file-upload
Add support for multipart file upload in InvenioRDM.
@CESNET
Data citation support
Improve the data citation support in InvenioRDM according to Fenner et al. (2019) A data citation roadmap for scholarly data repositories.
@Front Matter
Export formats
Add support for metadata formats currently supported in Zenodo, including BibTeX, JSON-LD, GeoJSON. This includes adding support for custom and optional metadata fields currently supported by Zenodo, and ability to display badges on record landing pages.
@CERN, April 2023
Communities
Communities REST API: Records/Requests
Implement the REST API and workflows for communities and the requests features. This will enable the integration between communities and records as well as the general framework for communities submission handling.
@CERN, Northwestern University & TU Wien, May 2022
Communities
Communities UI: Members
Implements the user interface for managing members of a community as well as inviting members and allow user to request membership.
@CERN, June 2022
IIIF
IIIF image previewer
Enables the International Image Interoperability Framework (IIIF) support and integrates the Mirador v3 previewer for large images.
@Data Futures & Uni Hamburg, June 2022
Vocabularies
Creator/contributor auto-completion and improved ORCiD integration
Enable auto-completion of creators/contributors in the deposit from a local names vocabulary that can be filled from e.g. ORCiD or your institutional employee database.
@CERN, February 2022
Third-party integrations
GitHub integration
Migrate Zenodo's current GitHub integration to InvenioRDM.
@CERN, Q2 2023
Sharing
Access requests
Add support for requesting, granting and managing access to a restricted record.
@CERN, Q2 2023
Basic OAI-PMH server
@TU Graz, April 2022
Communities
Subcommunities
Add support for creating and managing fully featured subcommunities (i.e. support for records, members, settings etc) .
@@CERN, Q2 2024
Back office / Admin
Implement a basic an back office administration interface for InvenioRDM. The tasks focuses on setting up the main skeleton for the administration interface, and add the first couple of administration actions into the form.
@CERN, September 2023
Software Heritage
Document and launch the Software Heritage integration for use in InvenioRDM. The integration is currently launched on Zenodo.
@CERN
Vocabularies
Funders and grants
Enable the funder/grants field in the deposit form and import the required vocabularies in InvenioRDM.
@CERN, February 2022
Data migration
Implement the core features to enable and make data migration to a new InvenioRDM instance easy. The new tools will be tested and progressively enhanced while migrating the current Zenodo production instance to a new Zenodo instance based on InvenioRDM.
@CERN, December 2022
Statistics
Usage statistics
Migrate Zenodo's current usage statistics module providing record views and downloads according to COUNTER Code of Practice for Research Data Usage Metrics. The feature supports rolling up views over versions as well as sorting by most viewed records.
@CERN & TU Wien, April 2023
Development
Concept DOIs
Add support for registering concept DOIs.
@CERN, Q2 2023
OAI-PMH sets support
Supports the sets feature of the OAI-PMH harvesting protocol.
@TU Graz, June 2022
Communities
Communities: Record management
Enhance the communities feature with support for:
- Submit a record to multiple communities before/after the record is published.
- Remove a record from a community.
- Publish a record directly to a community without review (for users with appropriate permissions).
- Notifications for communities.
- About page with curation policies.
- Invite members by email.
@CERN, April 2023
Communities
Branded communities
Add support for styling communities with their own visual identity.
@CERN, Q1 2024
Communities
Communities UI: Records/requests
Implements the primary user interface for searching and browsing records associated with a community. Includes the workflow support for submission of new records to a community and the integration into the deposit form.
@CERN, May 2022
Authentication
EOSC AAI integration
Support logging in via the OpenAIRE Authentication and Authorization Infrastructure (AAI) as part of the European Open Science Cloud (EOSC).
@CERN, February 2022
Preservation
OCFL Backend Support
Basic demonstrator developed which dumps and InvenioRDM repository into a OCFL repository.
@Data Futures, June 2022
Metadata curation checks
Add support for automated basic curation checks of records per community.
@CERN
Development
Deposit form enhancements
Small enhancements to the deposit form to support features currently available on Zenodo. This includes adding optional support for:
- Disallowing fully restricted records.
- Require files for a record
@CERN, April 2023
Communities
Communities REST API: Members support
Adds support for having multiple community owners and members of communities with curation capabilities. This task only deals with the REST API and backend (i.e. the user interface is a separate task).
@CERN, Northwestern University & TU Wien, May 2022
Files
Linking to files on external storage systems
Support linking to files on an external storage system instead of requiring the files to be uploaded via InvenioRDM.
@CERN, November 2022
Third-party integrations
ownCloud integration
Added support for integrating ScieboRDS via server-side file downloading and RO-Crate metadata format.
@CERN, November 2022
Persistent Identifiers
DOI minting support
Support for registering DataCite DOIs as well as for developing your own plugins for registering other types of persistent identifiers (Crossref DOIs, ARKs, Handles, ...).
@CERN, May 2022
Custom fields
Allow instances to configure additional custom fields and make them available in the deposit form and on the landing page. The current task implements both the backend and frontend.
@CERN, September 2022
Collections: Backend + Browse page
See example on https://zenodo.org/communities/eu/browse
Third-party Integrations
OpenAIRE integration
Integrate InvenioRDM with the OpenAIRE infrastructure by supporting the required OAI-PMH sets, export formats as well as allowing direct indexing of new records to OpenAIRE.
@CERN, December 2022
Harvesting of ROR, ORCID.
Recurrent harvesting of ROR and ORCID into the names, affiliations and funders vocabulary.
I18N
Internationalization (I18N)
Finalise the I18N support and provide a german translation of InvenioRDM. Further languages to come later.
@TU Graz & Uni Bamberg, January 2023
Release dates
We aim to have a major release once a year. For more information, please read our maintenance policy.
FAQ
What does current, near-term and planned mean?
- Current means that a development team is currently working on the feature.
- Near-term means that a development team has planned to work on this feature as their next task.
- Planned means that a development team has allocated time on their schedule to start work on the feature.
Will "current" features be released before
"near-term" features?
No. It is not guaranteed that a feature currently under development will
be released before a feature in the near-term column. Each feature may vary
greatly in size and required effort, as can the team that implements the
feature.
When will feature X be released?
New features are released as soon as they are ready in the next
coming release. We on purpose do not communicate in which
release a given feature will be shipped.
Why do you not tie features to release dates?
We want to communicate clearly the inherent uncertainty in our planned
schedule coming from developing a product as a large open source
collaboration.
What is the inherent uncertainties in your development schedule?
As a large open source collaboration, most our resources comes as opportunistic
temporary resources. Partners may contribute developers on a short-term/long-term
basis, full-time or part-time. This means the development teams are rarely stable
for a longer period, and each team has different velocity and skillset. In addition,
a large part of the developers participate in running services for their institution
and services may from to time need immediate attention. We see all these challenges
as strengths for the InvenioRDM community, that overall helps build a stronger
and more resilient community, as well as building features that serve
real needs for our community.
Can I use your roadmap to make commitments?
Any commitment you make is your own commitment and made at your own risk and
you must evaluate the impact of not meeting your commitment. If you
need a specific feature, the best you can do is to help accelerate the roadmap.