Difference between revisions of "Features/Classroom management"
(→Owner) |
|||
| Line 24: | Line 24: | ||
== Detailed Description == | == Detailed Description == | ||
| − | + | As described in the summary, the goal of this feature is to encapsulate three aspects of classroom management into one harmonious set of tools and interactions. The goal is to provide tools for visualization and exchange of Journal activity. We'd like to accomplish this within the context of the existing Sugar infrastructure (for reasons of maintainability) and do it in a way such that the teacher and child have maximum control of the flow of information and content. | |
| + | |||
| + | There are four components to the work: | ||
| + | # capturing activity usage (this is already largely accomplished by the accumulation of launch times [https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/src/sugar3/activity/activity.py#L332 1]). We may want to consider adding metadata which captures the accumulated time an activity is the top window in Sugar. | ||
| + | # visualizing activity usage (again, this is largely accomplished by Analyze Journal [http://activities.sugarlabs.org/en-US/sugar/addon/4545 2]). We may want to enhance the stats and also to maintain a current data object with these stats. | ||
| + | # exchange between the teacher and the student (largely accomplished by Journal Share [http://activities.sugarlabs.org/en-US/sugar/addon/4656 3]). We plan to expand upon Journal Share to enable automatic uploading of statistics from the student laptop. We also plan to add the ability to push a favorite view from the teacher's Sugar to the student's Sugar. | ||
| + | # exchange between the teacher and a webservice (this can leverage the webservices mechanism [[WebServices|4]] but needs to be informed by more clarity around what needs to be uploaded/downloaded | ||
| + | |||
| + | Above and beyond these components, we need to define a workflow by which they are used: | ||
| + | ... | ||
== Benefit to Sugar == | == Benefit to Sugar == | ||
Revision as of 11:02, 11 July 2013
Summary
This feature provides an infrastructure that addresses three aspects of classroom management:
- sharing content between students and teachers
- visualizing activity usage by students and teachers
- managing the Sugar home page by the teacher for lesson planning
It also provides the framework for the controlled uploading classroom statics by the classroom teacher.
Owner
- Name: Walter Bender
- Name: Gonzalo Odiard
- Email: <walter AT sugarlabs DOT org> <gonzalo AT sugarlabs DOT org>
Current status
- Targeted release: 1.2
- Last updated: 10 July 2013
- Percentage of completion: 25% (Analyze Journal and Journal Share are the basis of this feature)
Detailed Description
As described in the summary, the goal of this feature is to encapsulate three aspects of classroom management into one harmonious set of tools and interactions. The goal is to provide tools for visualization and exchange of Journal activity. We'd like to accomplish this within the context of the existing Sugar infrastructure (for reasons of maintainability) and do it in a way such that the teacher and child have maximum control of the flow of information and content.
There are four components to the work:
- capturing activity usage (this is already largely accomplished by the accumulation of launch times 1). We may want to consider adding metadata which captures the accumulated time an activity is the top window in Sugar.
- visualizing activity usage (again, this is largely accomplished by Analyze Journal 2). We may want to enhance the stats and also to maintain a current data object with these stats.
- exchange between the teacher and the student (largely accomplished by Journal Share 3). We plan to expand upon Journal Share to enable automatic uploading of statistics from the student laptop. We also plan to add the ability to push a favorite view from the teacher's Sugar to the student's Sugar.
- exchange between the teacher and a webservice (this can leverage the webservices mechanism 4 but needs to be informed by more clarity around what needs to be uploaded/downloaded
Above and beyond these components, we need to define a workflow by which they are used: ...
Benefit to Sugar
Scope
The feature requires:
UI Design
How To Test
Features/Classroom management/Testing
User Experience
Dependencies
Contingency Plan
No impact as this is a new feature.
Documentation
Some discussions with the design team regarding the placement of the buttons on the palettes.