This was resolved by improving on the possible ways in which a hub can be connected with an edoovillage. The implementation now includes two possible relations:
+ The hub is managing the edoovillage
+ The hub has contributed a dootronic which was deployed at the edoovillage
This provides a more fair way to capture the edoovillages that a hub is really contributing to. For instance, at the time of this ticket, prior to this modification, the Hub in California/Pomona had no edoovillages, even though it had contributed laptops that were deployed in an edoovillage (but not managed by it). With this change, the 'Edoovillages' table of this hub it now also shows one edoovillage it's (indirectly) contributing laptops to: https://www.labdoo.org/hub?h=37237
Commenti
Also hub has contributed to
Also hub has contributed to edoovillages but does not show in the edoovillage tab: https://www.labdoo.org/hub?h=17517
To fix, ensure indirect relations are also included in the dashboards (same as dootronics above)
This was resolved by
This was resolved by improving on the possible ways in which a hub can be connected with an edoovillage. The implementation now includes two possible relations:
+ The hub is managing the edoovillage
+ The hub has contributed a dootronic which was deployed at the edoovillage
This provides a more fair way to capture the edoovillages that a hub is really contributing to. For instance, at the time of this ticket, prior to this modification, the Hub in California/Pomona had no edoovillages, even though it had contributed laptops that were deployed in an edoovillage (but not managed by it). With this change, the 'Edoovillages' table of this hub it now also shows one edoovillage it's (indirectly) contributing laptops to: https://www.labdoo.org/hub?h=37237
Commit: https://github.com/Labdoo/Labdoo/commit/3842817df7aa2b57ee7a3fe8046d6b7c...