You are not a member of this team. If you want to be part of this team, click on 'Subscribe to this team'.
Team(s):
Typ:
Feature request
Status:
Open
Priorität:
Low
Beschreibung:
Hi Jordi, we can discuss in Barcelona, just not to forget:
actually a dootrip can have the status pending or completed and mainly will be used for already assigned / agreed dootrips. But there is no difference to inform about needed dootrips. The dootrip data can be used as it is, but maybe we can add a new status "request" and "offer" or similar?
The idea is to add dootrips e.g. within Germany. There is a helper travelling every 2-4 weeks from Stuttgart <--> Duisburg. So I could add a dootrip as offer. Ideal would be 2 options (fixed date(s) as it is and a new option to show that is a frequent travel but without fixed date?)
Just an idea, will not be used often, so not so important...
Kommentare
Hi Ralf,
Hi Ralf,
It seems like you are asking for two separate features:
Feature 1. Currently all dootrips are "offers". This feature would require adding a new state or dootrip type for "requests", correct? so the workflow could be:
Step 1 - User creates a dootrip and marks it with state "request".
Step 2 - Traveler finds that dootrip and changes the state to "accepted/pending".
Step 3 - Traveler completes dootrip and marks it as "completed".
Step 1 is optional. Travelers can still create directly dootrips (offers) and mark them as "pending" as they do today.
Feature 2. Add an option to specify the time of a dootrip as a periodicity. Instead of fix days, users can now say "every two weeks", or "every month".
Is the above correct?
correct, but...
Yes, that is correct, both features would be great, but... I learned from Miguel that there are regional start-ups in Spain (and in Germany, too) offering a web based solution to bring helpers and goods together. Like similar solutions for transporting people (e.g. Uber) they focus on transporting goods, for free or a low fare. All these portals are in an early stage, e.g. not offering their service for a country, but only for a region, planning to spread.
The question I cannot answer today is, if Labdoo will get the traffic and visitors we need ? Or if it is better not to solve it be ourselves, but to use regional or national, external portals? They will take care of advertise, traffic etc. And we might have the chance to be noticed by No-Labdooers.
Actually I think, it might be better to wait for 6-12 months and see how the market will develop. What is also make me uncertain is that again most dootrips are registered by Frank and me. This shows me that dootrip matchings are not often used from other hubs. So I do not want to spend your resources. What do you think?
Thanks Ralf.
Thanks Ralf.
I agree that we can collaborate with other platforms that develop a similar concept as dootrip. The more CO2 neutral routes we can find, the more sustainable we will be.
I think that it's also important to register dootrips. Not only because of the logistic reasons, but also because of transparency and accounting reasons. Even if we use other platforms, we should still register the dootrips so that we can provide full transparency of which volunteers carried the laptops. This also allows us to compute CO2 savings and measure sustainability metrics etc.
In our local projects in Barcelona, we always ask volunteers to register their trip. Step by step, they are doing it more and more (i see now people registering dootrips from New York, New Zealand and many other remote places). It is a process. I don't know about all other hubs, but we should teach our volunteers to register their trips. When we have a traveler, we send them these two wiki links explaining how to register their dootrip:
How to register a dootrip: https://www.labdoo.org/content/how-register-dootrip
How to link dootrips and dootronics: https://www.labdoo.org/content/assigning-dootronic-dootrip
So even though we can use other platforms, we should still use the dootrip system to help transparency and accounting.
Implementing the two features you requested is fairly simple, i will get it done and let you know :). Thks.
Hi Ralf/Jordi, Thank you both
Hi Ralf/Jordi, Thank you both for the effort and dedication you put into the Labdoo process:)
Hi Jordi,
Hi Jordi,
Again thanks so much for the dootrip implementation! I love the feature and I can see it will be powerful as time goes by. In the meantime, I can also see Ralf's concern that commercial products most likely had spent tons of resources on market study before they implement certain features. We may waste your precious coding resources if we try to build something fits our own imagination, but not people's need.
Here's my humble opinion as my software company experience on dealing with users - even with a powerful implementation, we do selective tests before releasing it to "everyone". We don't do product announcement until we collect enough feedback and get final ok's with more than one major customers.
I cannot speak for everyone, but I got excited when receive the first notification on dootrip. Then I tend to filter out the "dootrip" notification due to the amount of emails I receive daily and "I made the assumption" that these are not related to me after receiving 20+ dootrip emails. I didn't go through the wiki page either. Because it's impossible to know which wiki got updated and "I assumed" there's nothing new to the dootrip feature. (that reminds me to submit a ticket for possible solution on this problem)
Again, I apologize that I "assume" everything and lots of time the assumptions may be wrong. But, I may be a good example as those many no patient users?
To conclude, my suggestion is temporary disable the email notification to "everyone" but only to the trip creator and the edoovillage mentioned in the form, until we feel it's mature enough to be released?
Thanks again for making Labdoo possible!
some ideas
Hi,
I am following your discussion and I agree that we should work on a permanent improvement, but our resources are limited. So just 2 spontaneous ideas, which might be easy to implement:
Most of the dootrips are caused by me and in most cases, when creating them, I am assigning the trips to an defined edoovillage at the same time. So those dootrips being assigned to a project should not be send to all other helpers and hubs not involved, even if they have projects in the same country. The laptops and the capacities are already assigned, so no use to involve others and produce the mails Wendy mentions. This will avoid many mails.
Another idea is to include only those other helpers in the mails living in the same country as the start of a dootrip? A German dootripper cannot carry laptops from the States :) I am not sure about this 2nd idea, as there maybe good reasons to include other countries as well. So please think about it, too.
But those 2 ideas could reduce the notifications mails. Any comments?
Thanks, Ralf
To accommodate for both
To accommodate for both requests (Wendy's and Ralf's), i have implemented a new "Announce this dootrip" checkbox. By default, this checkbox is disabled, which means that the dootrip will not be announced (so no unnecessary emails). But if the option is turned on, then edoovillage and hub managers (only, just like before) who have schools at the destination will be receiving an email about that dootrip.
I have updated the notifications wiki page, please read: https://www.labdoo.org/content/automatic-notifications-and-managing-your...
And check the new field at the bottom of the form: https://www.labdoo.org/node/add/dootrip
Let me know if you think this is not what you were looking for.
screenshot_from_2016-12-11_105425.png
Thank you for the
Thank you for the implementation!!
This new feature was just
This new feature was just triggered. Someone from Zurich who is going to Bangkok just created the following dootrip, and this user explicitly set the flag "Announce this dootrip" as ON.
https://www.labdoo.org/content/dootrip-000000291-z%C3%BCrich-switzerland...
Notice that this flag by default is OFF, so the user had to explicitly click on this check box. The assumption is that this user wants others to know about her trip because she still does not have any dootronics assigned (otherwise, she would not have select this option.) As a result, hub and edoovillage managers who manage a school in Thailand are receiving a notification:
Dootrip new feature
Hello - this was triggered by a new user. I will follow up with the user directly because she also sent me an e-mail about this. Frank
Sounds good Frank, we just
Sounds good Frank, we just wanted to demonstrate that the new feature to help reduce false alarms works. It seems it's working. The algorithm might need some refinements but at least now managers only get dootrip notifications when the user explicitly sets the flag "Announce this dootrip", as this user did. Thanks.