572
edits
Changes
Created page with "= Harvest Project = Harvest project aims to make learning visible to educators and decision makers. Within the context of the Sugar Learning Platform, this can be achieved by ..."
= Harvest Project =
Harvest project aims to make learning visible to educators and decision makers. Within the context of the Sugar Learning Platform, this can be achieved by collecting reliable metadata from the Journal. This project proposes a simple and continuous mechanism to obtain metadata from Journal entries, incrementally over time. Metadata can stored in a central repository for further statistical analysis.
== What it is collecting? ==
* Most of the available metadata from the Journal entries, except for the content itself, title and description.
* If available, it collects learners aproximate age, gender and laptop serial number.
== How does it work? ==
The project comprises two pieces of software: a harvest server that can be localed anywhere in the cloud, and a harvest client that runs in the learners machine. The harvest server exposes a service, accesible from the internet, for metadata storage. The harvest clients collect metadata from the Journal and send it to server.
== What are the advantages? ==
* Doesn't require OS customizations, it based on Sugar's web service framework.
* Doesn't depend on school server presence, either on backup files.
== What is implemented so far? ==
=== Harvest server ===
* Back-end service for storage.
* SSL data encryption.
* API Key authorization.
=== Harvest client ===
* Journal entries collection.
* Web service extension.
* Extension controls from the web service control panel.
== What is left to TODO? ==
* Server maintenance scripts.
* Server packaging.
* Client automation.
Harvest project aims to make learning visible to educators and decision makers. Within the context of the Sugar Learning Platform, this can be achieved by collecting reliable metadata from the Journal. This project proposes a simple and continuous mechanism to obtain metadata from Journal entries, incrementally over time. Metadata can stored in a central repository for further statistical analysis.
== What it is collecting? ==
* Most of the available metadata from the Journal entries, except for the content itself, title and description.
* If available, it collects learners aproximate age, gender and laptop serial number.
== How does it work? ==
The project comprises two pieces of software: a harvest server that can be localed anywhere in the cloud, and a harvest client that runs in the learners machine. The harvest server exposes a service, accesible from the internet, for metadata storage. The harvest clients collect metadata from the Journal and send it to server.
== What are the advantages? ==
* Doesn't require OS customizations, it based on Sugar's web service framework.
* Doesn't depend on school server presence, either on backup files.
== What is implemented so far? ==
=== Harvest server ===
* Back-end service for storage.
* SSL data encryption.
* API Key authorization.
=== Harvest client ===
* Journal entries collection.
* Web service extension.
* Extension controls from the web service control panel.
== What is left to TODO? ==
* Server maintenance scripts.
* Server packaging.
* Client automation.