Idea #2056
Updated by Tom Clegg about 10 years ago
This is a view of the Logs table.
* "Group activity" is a report for a single group. Includes all Log entries whose object has @owner_uuid = {this_group_uuid}@.
* "User activity" is a report for a user. Includes Log entries whose object has @owner_uuid in ({all groups owned by this user})@.
* Probably OK if the selection of objects is slightly fuzzy at this stage: e.g., if you show logs for any object whose @modified_by_user_uuid@ is this user, an object which is undergoing edit wars could disappear and reappear on activity logs, and that's OK. We can revisit the edge cases after getting some input/experience (and possibly a new metadata database that makes different queries easier).
* Theoretically Log entries will have a "summary" attribute which is human-readable.
* Presumably, Workbench's LogsHelper gets a method that renders nice html for a given Log entry.
Things that should appear on the activity list include:
* Sharing settings changed for this group (So-and-so added/removed)
* Item added/removed from group
* Login by user that this group can_read