Page History

...

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

Notes

Status:
Both the Strategic Planning Group and Technical Planning Group are finalizing their reports to the DSpace Steering Group.
Reports are expected to be submitted by the end of October or early November.
Next Steps:
- Steering and Leadership will review the reports to decide on:
  - Moving forward with the proposed merger.
  - Providing feedback or requesting clarifications from working groups.
- Decision may come within the next month, depending on review progress.
Action:
Tim will continue to provide updates in upcoming meetings.

...

Scheduled for next week’s meeting.
Will focus on:
- Testing conducted by Art Lowel.
- Related development work from Giuseppe and the 4Science team.
Other ongoing topics:
- Angular Dynamic Decorators: now resolved and can be removed from the agenda since Alex confirmed compatibility with both possible solutions.
- Aggressive bot protection: no current updates.

...

Topic: Enhancing provenance metadata for better auditing of item and bitstream changes.
Milan proposed using provenance metadata to track edits and deletions.
Key Points:
- Tim noted challenges with using provenance alone for auditing deletions, since deleted objects also remove their provenance records.
- Milan clarified that DataQuest’s enhanced provenance tracks deletions as metadata before removal.
- Tim and others agreed this approach could complement the separate audit trail.
Consensus:
- Provenance and audit trail serve distinct but related purposes:
  - Provenance: chain of custody.
  - Audit trail: operational log within DSpace.
- Both may coexist or be configurable.
- Stefano (4Science) emphasized keeping the Solr-based audit trail.
- Tim recommended creating a GitHub ticket describing DataQuest’s approach with screenshots and examples for future review.
Action:
Milan will create a ticket documenting the enhanced provenance approach.

...

Two PRs (backendand frontend) address HTML escaping in search and MyDSpace results.
Goal: Prevent HTML tags from rendering improperly or causing security issues.
Status:
- Backend changes focus on Solr configurations and escaping logic.
- Frontend implements consistent escaping through metadata handling.
Reviewers:
- Giuseppe (4Science) volunteered to review.
- Tim added himself for oversight.
Priority: High.

Adds lang attributes to elements for accessibility compliance.
Issue:
Metadata language codes use the POSIX format (e.g., en_US) while web standards require en-US.
Discussion:
- Debate over whether to convert format in frontend or backend.
- Art suggested backend conversion for consistency.
- Tim agreed it warrants deeper analysis.
Decision:
- Implement a temporary conversion on the frontend.
- Create a separate ticket to evaluate proper long-term language format for the backend.

Proposal: More flexible pagination component allowing:
- Skipping large page ranges.
- Jumping directly to a specific page via input or ellipsis pop-up.
Feedback:
- Art and Tim supported simpler, flexible pagination, with mobile-friendly variations.
- Avoid embedding a “search box” within pagination, as it may confuse users.
- Consider reviewing designs from other systems (e.g., Google, admin tools).
Outcome:
- Andrea to refine the PR for simplicity.
- Possible multi-mode pagination (basic/advanced).

Adds a new "mail.server.fixedRecipient" setting to allow all email to be sent to a single recipient email
When this setting is enabled, it overrides the "mail.server.disabled=true".
Feedback:
New setting makes a lot of sense
Several Committers however are concerned about how it overrides "mail.server.disabled=true". That may be confusing behavior, and (at the very least) would require detailed documentation
Next Steps:
Mark W, Paulo G and Tim will all be assigned as reviewers

...

Team Code Review Session:
Meeting concluded with collaborative review of the HTML escaping PR.