Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

See Trading reviews on Pull Requests for how to get immediate attention to that PR!

Notes

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

  • Audit Trail Feature (Stefano Maffei, 4Science)
    • 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.

    • 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.

Action Items

  • 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.