Custom Query (2152 matches)
Results (280 - 282 of 2152)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1664 | fixed | Smarter group activity streams | seanh | seanh |
| Description |
We already have simple activity streams for groups that have new group or group updated events (see #1631). Smarter/more useful group activity streams would also contain the events for things related to the group: users, datasets, other groups, etc. This should just mean using a more complex SQL query in the group_activity_list() logic function. 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. |
|||
| #1665 | fixed | Begin doing research into eurovoc | seanh | seanh |
| Description |
How big is it? How are we going to store it? etc. |
|||
| #1666 | fixed | Add activity stream events for tags | seanh | seanh |
| Description |
...and show them on the tag pages. This means adding tag_activity_list() and tag_activity_list_html() logic functions, adding the templating to render tags as HTML, and adding the tag HTML into the tag pages. What exactly should go into a tag's activity stream? As with datasets we may want a more complex SQL query, where events from objects related to the tag (datasets, users, etc.) appear in the tag's stream. |
|||
