Page History
...
See Trading reviews on Pull Requests for how to get immediate attention to that PR!
Notes
DSpace–DSpace-CRIS merger:
No major updates; both groups are still working toward a decision point.
Q&A webinar planned for late September.
Webinars:
Next week: First session in the new DSpace Deep Dive series
Topic: DSpace 9.x Overview + Q&A (repeat of Open Repositories presentation).
Will be recorded and posted for later viewing.
October: Planned webinar on migrating from bepress to DSpace.
Call for presenters: Anyone interested in sharing DSpace work is encouraged to contact Holger and volunteer for upcoming webinars, or just fill out the form on the website
Main Topic: NX Migration Discussion
Background:
Last week, Giuseppe presented why NX might be useful for DSpace.
Discussion continued due to limited time previously.
Tim Donohue’s findings:
Looked into NX GitHub activity: appears healthy and active.
NX supports multiple Angular versions (last 3), offering flexibility.
Kristoph feedback:
Suggested considering Angular CLI workspaces instead of NX.
Concern: NX migration may involve heavy restructuring, similar to previous Angular version transitions.
Believes Angular alone supports modularization and libraries without needing NX.
Giuseppe:
NX provides useful additional features: incremental caching, dependency graph, tooling.
Angular CLI lacks some of these.
Prefers NX but open to discussion.
Art:
Sees CLI workspaces as a possible intermediate step before NX.
Suggested experimenting with both approaches before deciding.
Proposed creating a simple prototype (e.g., adding a tab or menu) in both NX and CLI workspaces for comparison.
Francesco:
Has ~2 years of production experience with NX.
Initial learning curve and rigid structure, but ultimately useful for modularization and shared components.
Other concerns raised:
Pierre: Asked whether modularization will simplify or add complexity for new developers.
Tim: It may add slight complexity for contributors to DSpace core, but could make local customizations easier.
Mark:
Emphasized the need for clear documentation if new structures are adopted.
- Documenting can assist with improving one's understanding and clarify questions.
Next Steps
Preparation Pull Request (PR):
Current PR reorganizing imports and code paths is seen as a good first step, regardless of NX vs. CLI decision. https://github.com/DSpace/dspace-angular/pull/4629
General agreement to move it forward with small adjustments.
Future work:
Consider prototyping add-ons or overlays in both NX and Angular CLI workspaces for comparison.
Document structural decisions carefully to support contributors and institutions.
Action Items:
Tim to summarize discussion and ensure feedback on current PR.
Giuseppe to clarify pathing decisions in PR (before his holiday or after return).
Art may explore a prototype comparison (depending on availability).
Community to continue discussion, aiming for clarity on benefits/complexity balance.
Summary
- No final decision yet on NX vs. Angular CLI. The group will continue testing and discussing, with preparation work proceeding in the meantime.
...