History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: SAK-6212
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Stephen Marquard
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Sakai

Log events for meaningful user actions

Created: 06-Sep-2006 00:48   Updated: 23-Oct-2008 11:10
Component/s: News (RSS)
Affects Version/s: 2.2.1, 2.3.0, 2.2.2
Fix Version/s: 2.4.0

Time Tracking:
Not Specified

2.4.x Status: None
2.5.x Status: None
2.6.x Status: None


 Description  « Hide
News does not currently log anything in the Sakai event log. The event log is useful both for site statistics (user activity within site, e.g. as reported by the UFP SiteStats tool), and for research purposes when investigating how users have used Sakai, which in turn is important for informing further development.

News should post events to the Sakai log (news.*) for each meaningful user action, e.g. read news (visit the tool) and update (change the RSS feed).

The REF field should preferably include both the site id (context) and a reference to the RSS feed, as there can be more than one instance of the tool per site.


 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Joshua Ryan - 30-Nov-2006 01:06
Would the placementId be good enough context for the REF field?

Joshua Ryan - 30-Nov-2006 01:23
Should un successful updates be logged? or just successful actions?

Nuno Fernandes - 30-Nov-2006 02:05
I do not know of any implementation details of the News Tool but, in my opinion, the REF field should have a syntax similar to the following (to match other tools REFs):

/news/site/[SITE_ID]/feed/[FEED_ID]

You can view what others are logging in SAKAI_EVENT table. Example of a resource file REF:
/content/group/b0f42760-cc3a-4938-00ea-dbf4208bccbd/NCRMResearchMethodsTypology.pdf

Probably unsuccessful updates shouldn't be logged (I think other tools don't do it).

nuno.

Joshua Ryan - 30-Nov-2006 09:31
A news tool only has a title, a url and a placementId. The url and title can be changed during any update. Is it more important for the REF to be consistent or descriptive?

/news/site/[SITE_ID]/feed/[placementId]

Using the plancementId would stay the same for the life of the tool instance, the url could be used instead and would be more descriptive as to what content the user actually saw, but it would get ugly when/if the news adds support for aggregation of multiple feeds in one tool (possibly 2.4).

Nuno Fernandes - 30-Nov-2006 09:49
Hi Joshua,

I now understand your problem. Data is kept on the tool registry (feed URL stored under 'channel-url:'). Also, feed url is not associated with any kind of identifier and the url is not appropriate for the REF field.
I do not have better ideas! Perhaps just change your proposed REF to have 'placement' instead of 'feed' as it could lead to confusion?? Like:

/news/site/[SITE_ID]/placement/[placementId]

(just a suggestion)

Thanks, nuno

Joshua Ryan - 30-Nov-2006 09:59
Sold! I'll get started tonight.

Megan May - 08-Feb-2007 08:43
Updating fix version from nightly2/trunk to 2.4.0.001 in prep for first QA tag (Prelim testing pre-code freeze)

Megan May - 12-Apr-2007 13:45
Tasks for 2.4 have been completed. If you find a problem related to a task, please create a bug report and use the Link feature to create a connection between the two issues.