Features/Classroom management - Revision history

FGrose: update link

2015-12-29T18:49:08Z

update link

← Older revision		Revision as of 14:49, 29 December 2015
Line 40:		Line 40:
	;TBD: Is this an integrated Sugar feature or one that is managed at the Sugar activity level? (Easier to customize as the latter.)		;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/~~TeacherBuddy~~]] is a mechanism for identifying a teacher in the network neighborhood.		;teacher buddy: [[Features/Teacher Buddy]] is a mechanism for identifying a teacher in the network neighborhood.

	== Benefit to Sugar ==		== Benefit to Sugar ==

2013-07-30T01:53:25Z

Detailed Description

← Older revision		Revision as of 21:53, 29 July 2013
Line 39:		Line 39:

	;TBD: Is this an integrated Sugar feature or one that is managed at the Sugar activity level? (Easier to customize as the latter.)		;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/TeacherBuddy]] is a mechanism for identifying a teacher in the network neighborhood.

	== Benefit to Sugar ==		== Benefit to Sugar ==

2013-07-11T23:38:32Z

Detailed Description

← Older revision		Revision as of 19:38, 11 July 2013
Line 37:		Line 37:

	;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?		;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.)

	== Benefit to Sugar ==		== Benefit to Sugar ==

2013-07-11T23:38:12Z

User Experience

← Older revision		Revision as of 19:38, 11 July 2013
Line 74:		Line 74:

	;TBD: Is this always running? Or only running when the teacher is running Journal Share?		;TBD: Is this always running? Or only running when the teacher is running Journal Share?

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

	== Dependencies ==		== Dependencies ==

2013-07-11T23:36:41Z

User Experience

← Older revision		Revision as of 19:36, 11 July 2013
Line 72:		Line 72:

	;TBD: What are the privacy concerns?		;TBD: What are the privacy concerns?

			;TBD: Is this always running? Or only running when the teacher is running Journal Share?

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

	== Dependencies ==		== Dependencies ==

2013-07-11T23:34:38Z

Detailed Description

← Older revision		Revision as of 19:34, 11 July 2013
Line 35:		Line 35:

	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?

	== Benefit to Sugar ==		== Benefit to Sugar ==

2013-07-11T23:26:09Z

← Older revision		Revision as of 19:26, 11 July 2013
Line 4:		Line 4:
	</noinclude>		</noinclude>

	[[Image:AnalyzeJournal.png\|300px]]		[[Image:AnalyzeJournal.png\|300px]] [[File:ScreenshotJournalShareActivity_client.png\|300px]]

	== Summary ==		== Summary ==

2013-07-11T22:55:18Z

← Older revision		Revision as of 18:55, 11 July 2013
Line 3:		Line 3:
	[[Category:Feature\|Classroom management]]		[[Category:Feature\|Classroom management]]
	</noinclude>		</noinclude>

			[[Image:AnalyzeJournal.png\|300px]]

	== Summary ==		== Summary ==

2013-07-11T22:52:56Z

User Experience

← Older revision		Revision as of 18:52, 11 July 2013
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?

2013-07-11T22:29:18Z

← Older revision		Revision as of 18:29, 11 July 2013
Line 5:		Line 5:

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