Requerimientos Para XO: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(redir) |
||
| (13 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
#redirect [[Blog educativo#Requerimientos para XO]] |
|||
[[Educational blogger project]] |
|||
The goal of this project is developing a whole system that helps teachers and children to write new contents, share them and use them with educational purposes. <br> |
|||
Uruguayan pilot-school of Villa Cardal has achieved very exciting results with the blogs usage, using Google Blogger for sharing the contents they produced and working on curricular stuff. <br> |
|||
However, the starting of these activities wasn't easy, requiring many hours of technical teaching and support. The main reason is that Blogger is not conceived with educational purposes - nor is any of the other popular blogging systems. <br> |
|||
Some drawbacks those systems have are:<br> |
|||
• To start working, you must have good connectivity <br> |
|||
• The drafts system is weak for collaborative work. It is not easy for children to compose posts together, and for the teacher to work with them. Most times, the approach gets to be just publishing draft materials and refining them afterwards. <br> |
|||
• They provide no easy way for working "indoors", for instance sharing a material within a whole school, but just publishing some selected articles. <br> |
|||
Those are common needs for educators.<br> |
|||
• We propose 5 local areas of work for making and deploying a blogging system tailored to educational puropses with XO laptops:<br> |
|||
• WordPress customization for granting different access levels<br> |
|||
• Daemons system for exchanging information within "Partner Servers"<br> |
|||
• WordPress customization for optimizing XO and children access<br> |
|||
• Web application for creating and managing users and blogs<br> |
|||
• System deployment <br> |
|||
WordPress customization for granting different access levels <br> |
|||
Users should be able to set to each post one of the following 4 access permission levels:<br> |
|||
1. Public access <br> |
|||
2. Registered-user access <br> |
|||
3. Selected Access: only can be accessed by a set of users defined by the writer <br> |
|||
4. Publisher-only access <br> |
|||
For the Selected Access level, a grouping system must be programmed, so it can be easy to set up a post for being accessible from within a form's group, for instance. <br> |
|||
Daemons system for exchanging information within "Partner Servers" <br> |
|||
This teamwork has the objective of changing the classical architecture of blogging systems, letting individual posts to be accessed from different servers, and letting users have different access grants. We'll call "Partner Servers" (PS) to servers which have our blogging applications running, and will be able to exchange feeds according to some set of policies. <br> |
|||
For instance, we may have a school server, which will store the posts published by their children and teachers. Posts that don't have permissions to be accessed from outside the school don't need to get replicated outside the school server. Other posts can be sent to a PS, for instance to a server which will store all the country's educational blogs. Finally, a lot of this information will be of international interest, and may get replicated in worldwide PSs. <br> |
|||
Why replicating? The two main advantages are: |
|||
• Optimizing schools bandwidth. As a lot of work is made locally, it doesn't get necessary to use the school's bandwidth in many cases. In other cases, replication can be made at scheduled moments, distributing in a more clever way the school's bandwidth usage. <br> |
|||
• Optimizing countries international bandwidth. International access to the Internet is an expensive issue for third-world countries. It's cheaper and faster storing local contents locally.<br> |
|||
The development work consists on programming daemons which will exchange posts within PSs according to configuration parameters that can be managed centrally.<br> |
|||
WordPress customization for optimizing XO and children access <br> |
|||
WordPress was conceived to be versatile for being used with many different purposes. However, when working with educational goals and XO machines, some special cares should be taken: <br> |
|||
• Children usability: The system has to be easy to be used, even for 6-year-old children. It includes taking away unnecessary stuff.<br> |
|||
• Clean and lightweight pages tested in XO's browser: Take care of the bandwidth usage and certify all pages run properly in XO laptops.<br> |
|||
Web application for creating and managing users and blogs<br> |
|||
This blogging system has to be managed somehow. Teachers may want to create blogs for special activities, school principals may want to create new blogs every year for their groups, and a support team must be able to help remotely. <br> |
|||
A web application for managing the whole system has to be programmed. |
|||
System deployment <br> |
|||
The system has to be installed in school servers and also in a datacenter. Hardware, connectivity and technical support is needed for this purpose. Additionally, a local community has to get involved, to administer and keep the system active. <br> |
|||
Latest revision as of 00:53, 19 May 2008
Redirect to: