Skip to content

Provide logging for Collection change events, add Activity Log views #3668

Description

@lsat12357

Descriptive summary

Collections do not have changes logged in Redis the way works do. This became more evident recently when uo-arch-photos mysteriously changed from open to restricted; in addition to recording who is working on a collection, logging may provide information useful in analyzing an unexpected change.
Events should be displayed on the collection show page; there are 2 possible pages for this, see below for example
Events to include the creation, updates (i.e. when the edit page is submitted), visibility changes; additional events can be added if required.
Because of the numbers involved, it is not suggested that the addition of members be logged.
Only changes that are made via the collection form will be logged, can consider tracking bulkrax importers.

  • Add logging for updates
  • Add logging for visibility changes
  • Add logging for create
  • Add to view

Expected behavior

Events related to the Collections will be logged in Redis. Events will be displayed on the collection show page.

Related work

Link to related tickets or prior related work here.

Accessibility Concerns

Add any information here to indicate any known or suspected accessibility issues for this ticket

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Content OpsIssues related to import, export, bulkrax, and content processing.MetadataIssues related to metadata configuration, application, and representationPriority - LowIssues that can be prioritized after High Priority - later in the project timeline

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions