Changes

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

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