Hello! I am helping several districts roll out Kolibri as an offline solution for students with zero internet access in rural Arkansas. Here are my thoughts and I would love some feedback/input as we look to roll this out.
- A “primary” or “main” server would be housed on the school campus.
- This one server would be the sole “Facility” in Kolibri
- School teachers would have Coach accounts on the main server
- School teachers would create “classes” - one class for each period or subject or however they see fit to organize their coursework. Most likely, teachers would have several classes they oversee.
- ALL Coursework would be located on one server, in one facility
- All students (roughly 200 initially, but up to 1100 possible) would be entered into the single facility.
- Students would be assign to classes according to their schedules
- Content would be propagated out to Raspberry Pi Zero Ws for each household (NOT each student).
- Each student has a Chromebook or Tablet
- Each student connects to their local/home-based Raspberry Pi device over the Kolibri wi-fi hotspot.
- Students complete their work on their devices/local copy of Kolibri
- Students return to campus at selected intervals to “sync” their data back to the main server on campus. (Hopefully implemented in 0.14, but can be done via command lines in 0.13 manually).
That is my plan at this point. One of the biggest issues I am told is the use of one single facility to handle all of this because of the potential for a vast amount of content being stored on all the memory cards for each Pi-ZeroW. Instead, it has been suggested that multiple Facilities be set up and associate students with a specific facility.
If we were to try to associate specific students with specific facilities, how much extra work is that in terms of making sure the right content goes to the right facility? I do not want to overload our teachers more than they are already being asked, if at all possible.