Features/Classroom management: Difference between revisions

Line 47:

== 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.

:* what additional data should be captured?

:* 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.

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

;visualizing classroom statistics: A few different ways in which this could happen. A new activity [NEEDS TO BE WRITTEN], similar to Analyze Journal, could be written to aggregate the stats uploaded by the students into one unified visualization. Or the classroom data could be sent out to a webservice [NEEDS TO BE WRITTEN] that provides cumulative statistics.

:* 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

== Dependencies ==

@@ Line 47: / Line 47: @@
 == 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.
+:* what additional data should be captured?
+:* 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.
+:* is this something that is better done as a background task? If so, when and how often?
+;visualizing classroom statistics: A few different ways in which this could happen. A new activity [NEEDS TO BE WRITTEN], similar to Analyze Journal, could be written to aggregate the stats uploaded by the students into one unified visualization. Or the classroom data could be sent out to a webservice [NEEDS TO BE WRITTEN] that provides cumulative statistics.
+:* 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
 == Dependencies ==