click here for details... Sakai Executive Director Position Search now open
Issue Details (XML | Word | Printable)

Key: SAK-12648
Type: Bug Bug
Status: Open Open
Priority: Minor Minor
Assignee: Zhen Qian
Reporter: Steve Lonn
Votes: 0
Watchers: 5
Operations

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

Extraneous Log Events Recorded When New Site is Created

Created: 08-Jan-2008 12:45   Updated: 08-Mar-2010 01:00
Component/s: Worksite Setup
Affects Version/s: 2.5.0, 2.5.2, 2.5.3, 2.6.0
Fix Version/s: 2.7.0-b05

Time Tracking:
Issue & Sub-Tasks
Issue Only
Not Specified

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

Sub-Tasks  All   Open   

 Description  « Hide
Some (not all) tools log a "new" event when they are initially turned on.

These events are pretty confusing, especially when trying to determine what tools are actually being used. For example, the Email Archive tool generates a "mail.new" event when the channel is created, but new messages sent to the Email Archive also generate "mail.new" events, so it can become difficult to differentiate between the different events, particularly if the interest is identifying user activity within the system.

Possible solution:
Rename initial log events that occur when the tool is first turned on for a site.
(e.g. when resources tool creates the root folder: content.setup instead of content.new)





 All   Comments   Work Log   Change History   Subversion Commits   git Commits      Sort Order: Ascending order - Click to sort in descending order
Peter A. Knoop added a comment - 04-Oct-2008 08:27
Can folks commit to fixing the remaining sub-tasks for this bug for 2.6 to help improve tracking and statistics?

Beth Kirschner added a comment - 13-Nov-2008 13:58
I've changed the sub-tasks to suggest using ".create" rather than ".setup", since this is what the emailArchive uses and what I will use in Calendar for consistency.

Peter A. Knoop added a comment - 02-Mar-2009 09:34
[Bulk Comment] This is issue is currently scheduled to be resolved for inclusion in the Sakai 2.6.0 release, however, it is still unresolved. If you still planning on resolving it, please reply with a comment indicating when you expect to have it resolved. If you don't think you will be able to address this issue in time for the release, please reply with a comment indicating such; particularly if this issue is Blocker or Critical priority. If the resolution of this issue is to be delayed until a future release (i.e., 2.7), then please update the Fix Version accordingly.