[HOT] Level of user experience to focus on
pierzenh at yahoo.fr
Thu May 28 14:27:45 UTC 2015
The Task Manager is for both new and experienced contributors. We should not focus on new contributors by accompany them appropriately,assuring at each level that they can intituively find more infos. For example,Buttons links, sliding panels for more infos or help can be used. Communication / suppor is also important. A Button for IRC communication, or even a IRC Panel directly into the Task Manager woud be an other way to adapt to the new contriutors, support and monitor them. This same approach should be part of the OSM editors.
We also started discussions about showing different infos based on the experience of the contributors (something to define). The Nepal response with now close to 7,000 contributors in one month is forcing us to revise how we manage crowdsourcing through the task manager. Many mapathons with one day contributors, have created various problems. There is the quality of data to manage and the validation workflow.
The Task manager by itself cannot address all these problems. We will need to talk on the Technical WG, Learning WG, Activation WG about some strategies to better manage the crowdsourcing, the Mapathons in context of emergencies like Nepal and tasks with various levels of difficulty.
Good documentation, easy access to the documentation, integration of the documentation in the tools (a side panel that shows how to trace a building, etc) Documentation and workflows specific to the Mapathons, tools to support and monitor the mapathons, these are various ways to approach this problem.
The design of the Task Manager should be part of a Global workflow for crowdsourcing.
De : Daniel O'Connor <daniel.oconnor at gmail.com>
À : Bryan Housel <bryan at 7thposition.com>
Cc : "hot at openstreetmap.org" <hot at openstreetmap.org>
Envoyé le : Jeudi 28 mai 2015 9h56
Objet : Re: [HOT] Level of user experience to focus on
I think https://github.com/openstreetmap/iD/issues/1657 sort of started in the right direction - the JOSM style, super complicated hard to understand validation messages aren't what you want, but the more the editor can suggest to me small improvements I want to make the better. If its real time or on new contributions, well; fantastic - discourages bad data getting in. That might not be feasible though.
You've previously said things like: "I think I might like it a little better if iD did very little validation and had an API integration with a dedicated validator like keepright." - that's probably a really feasible incremental step.
Imagine the workflow:
- New-ish user opens a tile in the tasking manager. - A flag to ID in the URL asks it to render the osmose error feed for that bounding box - New-ish user sees a few buildings, roads, etc. One of them has a red marker or outline on it. - User clicks on it, not having see it before - a message suggests that this is tagged with landuse and is a building. - Oops thinks the user, I thought about tagging like this, I guess that's not right. If we're lucky; I wonder if I can fix it. Outcomes: user learns from the 'mistakes' of others, but it's still very much suggestion based - more about gentle encouragement than having someone down the track invalidate your work with a terse message you don't understand.
That's... possibly a bit specific and maybe should be shifted into github somewhere to be kicked around further; but yeah...
On Thu, May 28, 2015 at 11:01 PM, Bryan Housel <bryan at 7thposition.com> wrote:
To your second point: Are there specific things that I can prioritize in iD to make it more suitable for new users performing HOT tasks? For example, I’ve made some progress on implementing a 2-click building drawing mode and hope to have that in the next iD release. And presets are something that are very easy for us change too.
Would be happy to start a conversation about this..
> On May 28, 2015, at 9:15 AM, Dan S <danstowell+osm at gmail.com> wrote:
> Hi Rekth,
> That's a great question. My perspective, as an occasional HOT facilitator:
> The learning curve for people getting into HOT has two "steep bits".
> The SECOND steep bit is advanced users learning how to use josm,
> learning how to validate etc. I've actually been surprised that this
> second steep bit doesn't seem too off-putting for people. The FIRST
> steep bit is when they're still quite new and learning how to use the
> TM, how to read aerial imagery, how to trace ways, etc. It's that
> first bit where the Tasking Manager could help facilitate their
> experience (especially since there are many complexities outside of
> the Tasking Manager), and where the TM could make sure that they have
> a positive, fluid experience that they feel good about repeating. So
> personally, I'd certainly say focus on the first-time or second-time
HOT mailing list
HOT at openstreetmap.org
HOT mailing list
HOT at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the HOT