Request for information
Some interest has been expressed in the development of an administrative tool to draw together and present usage statistics for UC Davis Sakai/SmartSite. Before moving forward, we would like to establish what the scope of the need for such a tool might be.
Primary interest groups/views/consumers of Sakai usage statistics
There are several different groups that may have both overlapping and non-overlapping requirements for assessing the actual usage of Sakai on a campus-wide basis.
- Technical (developers, dbas)
- to predict growth, evaluate long-term resource needs; to quantify performance
- Communications/Marketing
- to track adoption and articulate user interest
- Management
- to determine strategy based on current usage groups; to target specific groups for adoption
Types of data analysis
We can talk about potential solutions as falling into one or the other of these two forms of data analysis:
- Real time event monitoring
- Data-mining of existing usage information in the database
What's already out there? Leveraging the existing SiteStats Tool:
The existing SiteStats tool, which is currently marked as a Sakai Contrib, provides what is effectively an instructor-level view of usage on a site-by-site basis. Some of the logic of this code, however, may be useful in developing more of a global analysis of the data already available.
– 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/
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.