Possibly exclude some components from SSR? E.g. DSpace-CRIS excludes the Search component from SSR as these are not necessary for SEO. (Need to verify this has no negative impacts on accessibility or similar.)
May have a negative impact on download/view statistics (in Solr Statistics) as hits to the Apache cache would not generate view events. We'd need a different way to send these view events to REST API.
To quickly find PRs assigned to you for review, visit https://github.com/pulls/review-requested (This is also available in the GitHub header under "Pull Requests → Review Requests")
Goals for 8.0
This were decided by Steering in their meeting on June 28, 2023.
Duplicate Detection in Submission ported from DSpace-CRIS (The Library Code)
Include new features which empower users in the admin UI. Make things easier for Admins.
Accepting community contributions of any 6.x features which missed 7.x
Improve documentation, training to allow for greater community contributions. (Ease setup/install/customization, etc.)
Per DSpace 7 WG meeting on June 29, 2023, this may include dependency upgrades/maintenance (Angular, Spring, Solr, Tomcat, etc). May also include necessary code updates/refactors to ease in ongoing maintenance.
Release Goal: May 20, 2024
In parallel to 8.0, proof of concepts / planning regarding modularization:
Bug/security fixes only. Release will occur when sufficient fixes have been made to warrant a release.
New "themeable components" (for dspace-angular) are allowed in bug fix releases, provided that they don't significantly modify component behavior or similar.
Bug fixes should have one Pull Request
A PR against either the "dspace-7_x" maintenance branch OR the "main" branch.
(In the case of complex bug fixes, it is possible this automatic port action will fail. In that situation a manual port PR may need to be created.)
Try "Pull Request Trading" for a quicker review
Do you have a PR stuck in "under review" that you really want to see move forward? Or maybe it's someone else's PR but you want to get it more attention?
Presentation by Michał Dykas on how to optimize SSR performance
Michał Dykas and PCG team shared challenges and solutions on reducing lag times when dealing with large repositories in DSpace.
PCG team ran into some scalability/performance issues with a large repository. Currently documented Performance Tuning DSpace instructions were not helpful enough for a large site
Developed a way to use Redis for caching (instead of built-in DSpace caching which uses an in-memory lru-cache). This Redis solution worked well for a large site
PCG will donate Redis integration code & also make suggestions on improving documentation. (This Redis approach would be optional, only for sites that need it. However for larger sites it can help alleviate the need for a large cluster of node instances)
Add configuration to disable inlined CSS in SSR: https://github.com/DSpace/dspace-angular/pull/2067