How to track from droppoint to sanitizing hub?

Usually for this case (moving a laptop from one hub to another) we don't change the laptop status and we keep it as "S1". This is to avoid too much messaging and updates back and forth. The most important movement of a laptop is when it goes from a hub to an edoovillage, and in this case it is important to update the status (with a value "T1") because it does signal to the donor and participants that the laptop now is on its way to a school.

Upon moving a laptop from one hub to another, even though we do not change the laptop state, please *do* make sure to add the new hub in the laptop under the field "Source hub". This allows people to track in which hubs a laptop has been. So the laptop "Source hub" will now include the two or more hubs (as many as the number of hubs the laptop has been at). The protocol to move a laptop from one hub to another is explained in detail here: https://www.labdoo.org/content/dropping-point-hubs-tagging-protocol

Here is an example of a laptop that was moved from one hub to another (see the field "Source hub" which includes the two hubs): https://www.labdoo.org/content/000009157

By doing this, you can then check the history of this laptop and know when the laptop was moved from one hub to another. Here is the history of changes (under the 'Revision tab') for this example laptop: https://www.labdoo.org/node/35685/revisions

As you can see, on "Fri, 06/16/2017" this laptop was moved from Hub Escorxador to Hub Gestoria by user 'Laia': https://www.labdoo.org/node/35685/revisions/view/59076/60708

Hope this helps.

I see, this requires a bit of thinking then.

One simple solution is to change the address of the laptop to point to the address of the hub it is now currently located at. This would allow people to confirm if a laptop is indeed located in a hub or the other. But this will not change the list of laptops in both of the hubs' dashboard.

Right now each hub dashboard shows the laptops associated/related with that hub. That means it shows all the dootronics that somehow have interacted with that hub. This is done this way so that each hub can have a complete inventory of how many laptops it has helped to mobilize. But it does not mean that all those laptops are in that hub physically. So by looking at a hub's dashboard you won't be able to say with precision whether all those laptops are located in that hub, as those laptops could be related to the hub but currently located somewhere else.

On one hand, we need to keep the workflow simple. If we make it too complicated it will turn people off. On the other, i see your point.

Question: do we think there is a lot of laptops that move from one hub to another? if only 1% of the total laptops move from one hub to another, is it worth adding a new state and new flags to the workflow?

An alternative is to add a column "Located in this hub?" in the dashboard hub that says "yes" if the laptop is physically located in that hub. This way we don't need to add a new state/new rules. Would that help your use case?

Hello altogether

In Switzerland there is only hub with about 30 dropping points. So we do not face this challenge because we only track the hub location and not the dropping points. Otherwise we would end up in a nightmare of changing statuses for laptops on an ongoing basis.

Cheers, Frank