Changes

[[Category:Feature|Classroom management]]

[[Category:Feature|Classroom management]]

</noinclude>

</noinclude>

== Summary ==

== Summary ==

This feature provides an infrastructure that addresses three aspects of classroom management:

This feature provides an infrastructure that addresses three aspects of classroom visualization and management:

# sharing content between students and teachers

# sharing content between students and teachers

# visualizing activity usage by students and teachers

# visualizing activity usage by students and teachers

Above and beyond these components, we need to define a workflow by which they are used:

Above and beyond these components, we need to define a workflow by which they are used:

...

 

;teacher server?:Journal Share makes use of a local webserver. Should that server be repurposed for background processing? Or should we utilize a school server?

 

;TBD: Is this an integrated Sugar feature or one that is managed at the Sugar activity level? (Easier to customize as the latter.)

 

;teacher buddy: [[Features/Teacher Buddy]] is a mechanism for identifying a teacher in the network neighborhood.

== Benefit to Sugar ==

== Benefit to Sugar ==

== User Experience ==

== User Experience ==

;student visualizing Journal use: Simply by launching the Analyze Journal activity, a student can see a display of their activity usage, both based on instances and [NEEDS TO BE ADDED] on the number of times each instance has been launched. By default [NEEDS TO BE ADDED], Analyze Journal will save a datastore object associated with the activity that contains a json-encoded summary.

;student visualizing Journal use: Simply by launching the Analyze Journal activity, a student can see a display of their activity usage, both based on instances and on the number of times each instance has been launched. Analyze Journal saves a datastore object associated with the activity that contains a json-encoded summary.

:* what additional data should be captured?

:* what additional data should be captured? Is an accumulation of launch-times per activity adequate? Do we need to worry about change over time or just the current stats?

:* is it important that this be available as a background task as well? If so, when and how often?

:* is it important that this be available as a background task as well? If so, when and how often?

;uploading student Journal use to the teacher's laptop: Once the aforementioned modifications to Analyze Journal are made, the Journal Share mechanism could be used directly to upload a student's activity usage to the teacher.

;uploading student Journal use to the teacher's laptop: Once the aforementioned modifications to Analyze Journal are made, the Journal Share mechanism could be used directly to upload a student's activity usage to the teacher.

:* is this something that is better done as a background task? If so, when and how often?

:* is this something that is better done as a background task? If so, when and how often?

;setting the favorites view on a classroom full of laptops: TBD

;setting the favorites view on a classroom full of laptops: Might be worthwhile doing from Journal Share [NEEDS TO BE WRITTEN]. Or do we want it to be background? Best if used with multi-homeview patch [https://github.com/walterbender/sugar/commit/2ffa1cf6742bdb6b70c470d21969b4f45568038e 5].

 

 

;TBD: How do we identify the teacher laptop? Using the 'age' field?

 

 

== Dependencies ==

== Dependencies ==