Sakai WG - Usage Data
Easily accessible information about usage is critical to the work of Sakai-related staff including support staff, designers, researchers, developers, testers, and system administrators. Current capabilities to gather the required data and tools to present and interpret it are limited and vary across Sakai implementations. The Sakai Usage Data group intends to fully describe the types of usage data needed by all stakeholders, compare current strategies for gathering and interpreting usage data, and specify new strategies for gathering and interpreting data. Development of these strategies may be undertaken as a Sakai project.
Focusing on the use cases allows us to see that while there are many stakeholders who need usage data, the data in many cases is the same. This site has been structured around the initial use cases shown below. My hope is that the use case focus will allow us to design/deliver meaningful and complete chunks of usage data as we progress. In addition, we can compare ways that we access particular types of data across institutions, helping us understand the complexities of global and local configurations.
- Use Case 1 - Find out who did a particular action in a site
- Use Case 2 - Find out when a particular action in a site happened
- Use Case 3 - Find trends in usage over time
- Use Case 4 - Find out how often a particular widget is used
Questions for the Usage Data WG
- Do the use cases and actors below reflect your local stakeholders and needs?
- Does your current CMS or Sakai implementation support any of these use cases? Do they support others not listed here that should be added?
- If no Sakai implementations support these use cases, how should they?
Diagram has been updated to reflect important use cases identified in the Austin Usage Data BOF