Features/Classroom management: Difference between revisions
No edit summary |
|||
| Line 50: | Line 50: | ||
;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. | ;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? Is an accumulation of launch-times per activity adequate? | :* 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? | ||
:* or could launching it while the teacher is running Journal Share (or some equivalent) be used as an opportunity for a background upload? | :* or could launching it while the teacher is running Journal Share (or some equivalent) be used as an opportunity for a background upload? | ||