Difference between revisions of "Features/Statistics gathering"
m (sort in category) |
|||
| Line 1: | Line 1: | ||
<noinclude> | <noinclude> | ||
[[Category:Feature Page Incomplete]] | [[Category:Feature Page Incomplete]] | ||
| − | [[Category:Feature| | + | [[Category:Feature|Statistics gathering]] |
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example | <!-- You can add categories to tie features back to real deployments/schools requesting them, for example | ||
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). --> | [[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). --> | ||
Latest revision as of 22:26, 21 November 2011
Summary
To gather usage statistics in separate logs from error logs (up to a storage limit). The software improvement process requires usage statistics data to learn from our users.
Owner
- Name: Sebastian Silva
- Email: sebastian at sugarlabs.org
Current status
- Targeted release: 0.96
- Last updated: 2011.11.21
- Percentage of completion: 0%
Detailed Description
There have been efforts to gather statistics from the Journal as well as from Sugar error logs. However this is not sufficient. We would like there to be an optional logging of user interaction events that would make statistical analysis of usage viable.
Benefit to Sugar
Sugar will benefit from being easier to work with for researchers trying to study computer in education implementations. Also deployments can engage in user experience tracking and help provide helpful (hard data) feedback to developers who can improve the platform.
The Local Lab in Peru sees this feature as strategic for Local Labs sustainability.
Scope
Not sure.
UI Design
No UI changes necessary.
How To Test
Features/Statistics gathering/Testing
User Experience
N/A.
Dependencies
Determining relevant metrics.
Contingency Plan
Push for next release.
Documentation
To come.
Release Notes
To come.