| 1 | | This is a fairly big feature to add. |
| 2 | | |
| 3 | | We need to add to the User object/table a list of subscriptions, perhaps each row just needs to contain an object ID for an object whose activity stream the user subscribes to (or perhaps it will be more complicated when complex activity streams for things like groups and tags are considered). Or perhaps the subscriptions should be kept in a separate database table. |
| 4 | | |
| 5 | | We need to add the logic functions for getting the user's private activity stream as JSON and as rendered HTML. This is different from the user's public activity stream (which lists events performed by the user), it is the activity stream of events from all the activity streams that the user subscribes to. |
| 6 | | |
| 7 | | If this activity stream is meant to be private then their needs to be authorization when it is requested via the API for example. |
| 8 | | |
| 9 | | We then need to add the HTML rendering of this activity stream to the user's page when they are logged in. |
| 10 | | |
| 11 | | We need to add buttons for subscribing to activity streams. If the user is logged in and they are viewing a page with an activity stream (e.g. the page of another user, a dataset, a group, a tag) there should be a "subscribe" button. The user should not see a subscribe button on their own page. |
| 12 | | |
| 13 | | We need to add buttons for unsubscribing. The user needs to be able to see a list of the activity streams that she has subscribed to with an unsubscribe button next to each. |
| | 1 | This is a fairly big feature to add. Analysis: http://ckan.okfnpad.org/27 |
