Page History
...
| Info | ||
|---|---|---|
| ||
On October 21November 24, 20242025, the the DSpace Steering Group announced the approval of the merger of DSpace-CRIS into DSpace. This merger is planned to take place over two major release: 10.0 and 11.0. In the 10.0 release we will begin the merger process by porting a subset of DSpace-CRIS features into DSpace. The merger will complete in 11.0 with the porting of all remaining features. Because of these ongoing merger activities, any donated features which conflict with the DSpace-CRIS merger or make merger that DSpace and DSpace-CRIS are investigating a possible merger. While this merger would not occur in the 9.0 release, the 9.0 priorities are taking into account a possible future merger (in 10.0 or later). Any donated features which make a potential merger more difficult would not be included in 10.0. |
...
Anyone is welcome to donate features / development work which aligns with these priorities. If there are alignment questions, get in touch with Tim Donohue or ask in a Developer Meeting.
- Begin the merger of DSpace-CRIS into DSpace via a series of pull request to "port" specific DSpace-CRIS features into the core DSpace code.
- These PRs are all identified via the "DSpace-CRIS merger" label:
- Improving performance / scalability in general. Some examples include...
- Serve REST 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
- Search Results should be loaded using fewer REST requests: https://github.com/DSpace/dspace-angular/issues/3163
- Easier Installation and Upgrades. Some examples include...
- Discussions around simplifying installation process: https://github.com/DSpace/dspace-angular/issues/3184
- Can we simplify the installation/upgrade process of DSpace, especially now that there's a frontend & backend to manage?
- Code Cleanup / Maintenance. Some examples include...
- Dependency upgrades: Upgrade to Angular 19 and latest Spring / Spring Boot
- Replace Submission Form library (as the one we use is unmaintained): https://github.com/DSpace/dspace-angular/issues/2216
- All collections should have a workflow – a default noninteractive workflow would facilitate applying curation tasks (such as virus scanning) to all submissions: https://github.com/DSpace/DSpace/issues/8820
- 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)
- 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.
- Do we need a UI/UX guide to enable module developer to achieve a common "DSpace" look and feel? https://github.com/DSpace/dspace-angular/issues/3211
- Bitstream persistence URLs (if it does not interfere with a potential the DSpace-CRIS merger) - 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
- Accessibility fixes and other major bug fixes.
- Features or fixes that make a potential the DSpace-CRIS merger easier. (For more information on the potential merger, see the announcement from DSpace Steering.)
Features likely tabled until a decision is made regarding a potential merger
The following features may conflict with a potential the DSpace-CRIS merger merger (see above) because they are (primarily) features already available in DSpace-CRIS. Therefore, they have been temporarily tabled until a decision on the possible merger has been made. If you have questions, get in touch with Tim Donohue or join a Developer Meeting.
...
Overview
Content Tools