http://localhost/ticket/1664 <p> We already have simple activity streams for groups that have new group or group updated events (see <a class="closed ticket" href="http://localhost/ticket/1631" title="enhancement: Add activity stream events for new/changed groups (closed: fixed)">#1631</a>). Smarter/more useful group activity streams would also contain the events for things related to the group: users, datasets, other groups, etc. </p> <p> This should just mean using a more complex SQL query in the group_activity_list() logic function. </p> <p> Things might get tricky when a user or dataset joins a group, this may show up as two events (the user or dataset was modified, and the group was modified). We may want to have two separate events for this (one to go in the user or dataset activity stream and one for the group), or maybe we just want one 'user/dataset joined group' event. </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/1664 Trac 0.12.3 seanh Tue, 17 Jan 2012 10:22:57 GMT http://localhost/ticket/1664#comment:1 http://localhost/ticket/1664#comment:1 <ul> <li><strong>keywords</strong> <em>2d</em> added; <em>1d</em> removed </li> <li><strong>description</strong> modified (<a href="/ticket/1664?action=diff&amp;version=1">diff</a>) </li> </ul> Ticket seanh Mon, 28 May 2012 11:24:36 GMT http://localhost/ticket/1664#comment:2 http://localhost/ticket/1664#comment:2 <ul> <li><strong>milestone</strong> changed from <em>ckan-v1.7</em> to <em>ckan-future</em> </li> </ul> Ticket seanh Fri, 02 Nov 2012 13:37:17 GMT http://localhost/ticket/1664#comment:3 http://localhost/ticket/1664#comment:3 <ul> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>fixed</em> </li> </ul> Ticket