Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

  1. Technical (developers, dbas)
    • to predict growth, evaluate long-term resource needs; to quantify performancecurrent demands and identify pressure points on the system as a whole
  2. Communications/Marketing
    • to track adoption and articulate quantify user interest in the various components
  3. Management
    • to determine strategy based on current usage groups; to target specific groups for adoption

...

  1. Real time event monitoring
  2. Data-mining of existing usage information in the database

Most likely, we will encounter some constraints when it comes to mining the database on account of the sheer quantity of data involved. Tables that contain event data are frequently truncated, so any long-term monitoring would require some aggregation and archiving of data. Also, depending on the complexity, it may be necessary to batch some of the queries and/or denormalize some of the assessment data.

What's already out there?

...

– Confluence Docs: http://issues.sakaiproject.org/confluence/x/Gz0
– SVN for v2.1.x: https://source.sakaiproject.org/contrib/ufp/sakai_2-1-x/sitestats/

Indiana has a tool-by-tool break down of their usage by semester including percentage change in usage since the previous year. Not clear on whether this is a one-time data mining action or a tool they have implemented.

UCD Functionality Wish List:

At this point in time, the following is just a wish list because we don't know yet if it's possible to determine all these statistical data points from the currently collected data in Sakai.

  • How many unique users have access sakai
  • How many course sites
  • How many project sites
  • Hourly concurrent users peaks
  • Most accessed course sites (top 10)
  • Most accessed project sites (top 10)
  • Most used tools in course sites (either by tool presents in sites or usage frequency)
  • Most used tools in project sites (either by tool presents in sites or usage frequency)
  • etc.

Once we have a complete UCD functionality wish list, we need to determine/research, which functionalities can actually be implemented. Feel free to add any comments below.