Features/Classroom management: Difference between revisions

m update link
 
(7 intermediate revisions by one other user not shown)
Line 3: Line 3:
[[Category:Feature|Classroom management]]
[[Category:Feature|Classroom management]]
</noinclude>
</noinclude>
[[Image:AnalyzeJournal.png|300px]] [[File:ScreenshotJournalShareActivity_client.png|300px]]


== Summary ==
== Summary ==
Line 33: 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?
 
;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 ==
Line 69: Line 76:


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


== Dependencies ==
== Dependencies ==