Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Sakai DG: 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.

Task 1: Review and expand on initial use cases

The diagram below is an attempt to define the problem space we're talking about. There are many actors who need usage data, but the data in many cases is the same. I'd like to start by reviewing these diagrams and discussing any additional actors or use cases that aren't represented here. On the page for each use case, I've put in what I know about how we do or don't do this right now at University of Michigan. Please add what you know about how this use case is supported at your institution.

  • No labels