Contribute to the DSpace Development Fund
The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.
Version 9.0
Table of Contents:
Under Discussion for 9.0
The following is a (incomplete) list of features / priorities that are currently under discussion for the 9.0 release. Features/ideas listed on this list are NOT guaranteed for 9.0 until approved/prioritized by the DSpace Steering Group.
- Improving performance / scalability in general
- High CPU usage for server-side rendering, https://github.com/DSpace/dspace-angular/issues/3110
- Serve backend configuration more efficiently: https://github.com/DSpace/DSpace/issues/9056
- User permissions should be obtained in fewer REST requests: https://github.com/DSpace/dspace-angular/issues/3161
- Submission Form should be loaded using fewer REST requests: https://github.com/DSpace/dspace-angular/issues/3162
- Configurable Entities (by default)
- What do we need to achieve to enable Entities by default?
- How can entities be made more usable?
- Improving scalability/performance/functionality of Relationships
- Nested/hierarchical metadata (e.g. dates on a Person's affiliation with an OrgUnit)
- If entities are enabled by default how could a migration look like? Shall we offer a script to add a field dspace.entity.type="Publication" to all items without an entity type?
- Easier Installation and Upgrades - Can we simplify the installation/upgrade process of DSpace, especially now that there's a frontend & backend to manage?
- Modularization
- Angular : library-based architecture proposal - As of 8.0, we've already migrated to "standalone components". We can now consider whether to potentially migrate to using Nx.
- Bitstream persistence URLs - As of DSpace 7, there are no persistent URLs for bitstreams. The URL is based on UUID, and if you replace or version a bitstream the URL will change: https://github.com/DSpace/DSpace/issues/9083
- Replace Submission Form library (as the one we use is unmaintained): https://github.com/DSpace/dspace-angular/issues/2216
- Permissions
- Possibility of granting granular permission to individuals and groups to edit / see only some metadata
- Shall we automatically change metadata in flyway migrations?
- DOIs
- Changing the field a DOI is using (dc.identifier.uri vs. dc.identifier.doi)
- Changing the resolver (https://doi.org vs. http://dx.doi.org)
- DOIs
Priorities for 9.0
To be decided. 9.0 is still in very early planning phase. Priorities have not yet been established.
Tickets & Pull Requests to review for possible inclusion
All potential tickets & pull requests may be found on our 9.0 Project Board.
- 9.0 Project Board: https://github.com/orgs/DSpace/projects/31
If there is a feature you wish to work on which is not on that 9.0 Project Board, please create a GitHub issue ticket to describe it (or find one if it exists) and contact Tim Donohue (via email or Slack) about possible inclusion in 9.0.
Keep in mind, even if a ticket/PR exists on the 9.0 Project Board, that does not guarantee it will be completed in time for 9.0. All development & testing/reviewing is volunteer based. You can help ensure a PR's inclusion by volunteering to help test or review the code! Any work that cannot be achieved in time for 9.0 will be rescheduled for a future release.
Organizational Details
Release Coordination
The 9.0 Release will be coordinated by Tim Donohue and the DSpace Committers.
Updates and discussions will take place in weekly Developer Meetings.
Release Timeline
Please note that the dates below are estimates of when particular activities may occur. As there are many factors involved in a major release, these are subject to change.
Date | Milestone | What it means |
---|---|---|
April 2025 (tentative) | DSpace 9.0 is publicly released | DSpace 9.0 is released for download and general use. |
Release Process needs to proceed according to the following Maven release process: Release Procedure