Recent Changes (Content Activity Reporting)

Intended Audience

This feature will be geared for all users of MindTouch; the feature will be available as an add-on module for commercial (TBD). The first iteration of this will be available in Olympic.

Additional information

This work will be a precursor for enabling a richer "activity stream" experience inside MindTouch for applications.

Related

• Change monitor (watched pages)

Use Cases

Non-goals

UI requirements

The current table-based layout for recent changes makes no sense, as the tabular data doesn't yield any additional data. The scannability of the feed is currently atrocious (especially with move operations). The recent changes should do its best to reflect a single action as a single event and group changes as close together as possible).

Changes to note:

• Filtering in namespaces should effectively be boiled down to two namespaces: "Main" (NS_MAIN + NS_TALK) and "User" (NS_USER + NS_USERTALK) - thus promoting "Talk" as being tied more closely to the "Main" namespace.
• A table-based layout isn't useful if you're not doing calculations, making data points scannable, or you're allowing sorting by data points.
  • This new design allows for quick scanning by titles, and a drilling into the changes in each title
• Removed the per-date categorization (there's no benefit to breaking this down by day)
• Each page which has a richer history has a "view more changes to this page link..." which will inline append five more events to that particular page's history - this is to provide additional context of changes
• Metadata (files, comments, tags) should have actionable follow-up events within the recent changes feed
• Events that occur as a byproduct of other events (for example, moving or deleting) should be collapsable - it should be clear from this view that each activity was a single human event, and which events were the byproduct of human events. \
• The "Next" will inline load the next 50 (but still maintain permalinks) - in this progressive enhancement, the "previous" link becomes hidden.
• Advanced filters:
  • Search by username & group
  • Search by page path (this could theoretically be limited down to a single page to show the page's history)
  • Do NOT allow free-form search queries here

API requirements