Time/Location
from 14:00-15:00 UTC
Location: https://lyrasis.zoom.us/my/dspace?pwd=RTk4QUhISnhPRi9YenVrTFJKbDllQT09 (Meeting ID: 502 527 3040). Passcode: dspace
|
There will be no meeting next week on Thursday, September 18 because Tim and Holger will be at the Lyrasis All-Staff Retreat. Next meeting is Thursday, September 25. |
Agenda
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")
To be decided by DSpace Steering Group with feedback from Leadership Group.
Priorities listed at DSpace Release 10.0 Status.
Deadline is TBD for 9.2, 8.3 and7.6.5. Bug fix releases do not have fixed/scheduled deadlines. Instead, the developer team will determine when to create a release based on the significance of the issues to solve. (e.g. If major issues are fixed, then a bug fix release will occur more rapidly. If minor issues are found, then a bug fix release may be delayed until sufficient fixes have been made to warrant a release)
dspace-7_x are becoming more difficult to port forward.)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?
See Trading reviews on Pull Requests for how to get immediate attention to that PR!
Opening and Updates
Merger Discussions:
Upcoming webinar next Tuesday at 14:00 UTC to provide updates on the potential DSpace / DSpace-CRIS merger.
Webinar will include live Q&A; registration link available in the agenda.
Technology Planning Group continues to draft a roadmap for possible product integration.
More updates expected during the webinar.
Main Agenda Items
Demo Overview:
Feature tracks changes to items, bundles, bitstreams, and related repository objects.
Provides both a global overview and item-level audit log.
Tracks metadata additions, modifications, deletions, and file checksum changes.
Technical Implementation:
Audit data stored in Solr (audit core).
No current persistence layer beyond Solr. Export to CSV possible.
Similar approach to statistics storage, raising concerns about upgrade/migration complexity.
Discussion Points:
Persistence concerns: risks of only storing in Solr; discussion about possible database storage or file persistence (JSON lines).
Performance: confirmed feature handles bulk imports/updates without slowdown.
Deleted items: logs remain in global overview, but not visible in item-level audit once deleted.
UI considerations:
Item-level audit log accessible via dropdown.
Request to add links from community/collection pages.
Need for search/filter functionality in audit overview for scalability.
Scalability: appears stable, but will generate large volumes of logs.
Next Steps:
Summarize feedback into existing PRs (REST + Angular).
Community members encouraged to test and review PRs.
Consider adding persistence/export tooling and UI improvements.
Spring Shell Proposal (Paulo Graça, FCCN|FCT)
Motivation:
Requested by community; also informed by work with La Referencia project.
Provides structured way to implement CLI commands in DSpace.
Key Features:
Annotation-based commands.
Interactive and non-interactive modes.
Built-in features: help, history, autocomplete (tab), validation, default values.
Can auto-generate documentation pages directly from commands.
Potential to replace/modernize current CLI.
Demo Highlights:
Showed example commands (database test, database info).
Demonstrated auto-complete, help system, and auto-doc generation.
Draft PR exists, tests in progress: https://github.com/DSpace/DSpace/pull/11320
Future Opportunities:
Migrate existing commands to Spring Shell.
Provide Docker image / standalone executable.
Bridge with current “dispatcher” runnable scripts.
Potential installer command for DSpace setup.
Improve CLI documentation by automating updates.
Discussion Points:
Positive reception: autocomplete, history, auto-doc seen as major improvements.
Extensibility: possible to add new commands in modular packages.
Technical approach: currently implemented in DSpace API module (not yet separate Maven module).
Closing
General agreement:
Audit trail is a much-needed feature, now ready for community review.
Spring Shell proposal seen as a positive direction for modernizing CLI tools and documentation.
Community members to register for merger webinar and bring questions.
Developers to test/review Audit Trail PRs (REST + Angular).
Tim Donohue to summarize feedback into PR comments (esp. persistence, UI, search).
Explore persistence/export options for audit trail beyond Solr.
Consider adding item/community/collection-level links to audit UI.
Continue development of Spring Shell PR and address test failures.
Evaluate migration plan for existing CLI commands to Spring Shell.