Ticket #1494 (closed enhancement: wontfix)
API call for getting a user's public activity stream as rendered rtext
Reported by: | seanh | Owned by: | seanh |
---|---|---|---|
Priority: | awaiting triage | Milestone: | ckan-sprint-2012-01-09 |
Component: | ckan | Keywords: | 5d |
Cc: | Repository: | ckan | |
Theme: | none |
Description (last modified by seanh) (diff)
This could be implemented as a separate API call, or the rendered text versions of the activities could be added into the JSON returned by the existing API call.
This requires setting up templates for rendering activity streams items and detail items as nice, human-readable text.
There are some open questions, e.g.: Do we want the entire activity stream rendered as a block of plain text? As HTML? Or do we want a list of JSON objects, where each object contains its textual and/or HTML representations as fields?
Activity stream items and their related detail items are separate objects that each have their own textual representations.
For a mockup of the kind of text messages we want, see:
but note that this ticket is just for creating the text snippets themselves, not rendering then in an HTML page or RSS feed. Also the mockup only show activity items and not their detail items.
Change History
comment:2 Changed 2 years ago by seanh
- Milestone changed from ckan-sprint-2011-12-05 to current-ckan-sprint-2011-12-19
comment:3 Changed 2 years ago by seanh
- Milestone changed from current-ckan-sprint-2011-12-19 to ckan-sprint-2012-01-09
comment:4 Changed 2 years ago by seanh
- Summary changed from Setup templates for activity streams to API call for getting a user's public activity stream as rendered rtext
- Description modified (diff)
- Milestone changed from current-ckan-sprint-2012-01-09 to ckan-v1.6
comment:6 Changed 2 years ago by seanh
- Keywords 5d added
- Milestone changed from ckan-v1.6 to current-ckan-sprint-2012-01-09
comment:7 Changed 2 years ago by seanh
I've added a controller function for getting a user's activity stream as rendered html to ckan/logic/action/get.py in this commit: https://github.com/okfn/ckan/commit/30264997c7fe34324381123d6741d404baa67c1e
I'm proposing to leave it at that for now and not actually hook this controller function up to an API call, as I'm not sure how useful an API call for getting rendered HTML will be (we already have an API call for getting the user's activity stream a JSON).