Skip to content

Labdoo Objects

Jump to bottom
jrosgiralt edited this page Nov 17, 2013 · 6 revisions

The basic Labdoo objects are four: laptops, edoovillages, hubs and dootrips. They are implemented as content types and interconnected with each other using entity references. In addition, Labdoo users can be associated with each of these users taking a variety of roles (taggers, managers, editors, dootrippers, etc.)

The attached graph shows how these objects are interconnected with each other and with users. The interconnect follows a couple of rules that aim at reducing data redundancy while still ensuring all information and metrics can be computed (e.g., number of laptops assigned to an edoovillage, number of dootrips performed to a destination edoovillage, etc.)

Rules:

  • The graph should be acyclic. If it were not acyclic, there would be unnecessary redundancies.

  • There must exist a path between any two objects. This property ensures that the complete set of metrics derived from the Labdoo network can be computed. For instance, to calculate the number of dootrips performed towards reaching a destination edoovillage you can do as follows: compute first the complete set of laptops associated to that edoovillage; then, find the set of dootrips associated with these laptops.

[if you need write access to this drawing, please send an email to contact@labdoo.org] https://docs.google.com/drawings/d/1SPkDiNhb7HN3mjrW1XGnobdJ1Hvclex-tEs8dkMqcj0/edit?usp=sharing

Examples:

[dootrip] --n--> [laptop] : The node dootrip has a reference to the node laptop and such reference has a cardinality of n (a dootrip can carry n laptops in general)

[Edoovillage] --n--> [Hub] : Each edoovillage can be assigned to one or more hubs. This is a feature we don't support on Labdoo 1.0, but we got a solicitation for it from several hubs so we will support it in 2.0. In some occasions, multiple hubs collaborate together to bring laptops to a single school. For instance, currently we have projects in Nepal and Cameroon where hubs from Barcelona, California, Germany and Switzerland collaborate together to bring laptops.

[Dootrip] --n--> [User] : Most likely for this case we will often have n = 1 where a single user is responsible for the dootrip. But n > 1 should also be supported in the case where several Labdoo users make a dootrip together and they all want to be assigned to the dootrip. For instance, about 8 students from UCLA (from the group Eng. Without Borders) every year go to Guatemala to do water sanitation projects and they use that trip to bring laptops there. This feature would allow all of them to be associated with the dootrip. Currently Labdoo 1.0 only supports n = 1.

Clone this wiki locally