<html><head></head><body><div class="ydpa5f00e5ayahoo-style-wrap" style="font-family: verdana, helvetica, sans-serif; font-size: 13px;"><div>Quality is important to respond to Emergencies such as the OSM Ebola Response for DRC. This morning, I did monitor the Job 5705 for Yumbi, DRC. <br><div><a href="https://tasks.hotosm.org/project/5705" rel="nofollow" target="_blank" class="">https://tasks.hotosm.org/project/5705</a></div><div><br></div><div>Thanks to the validators who support OSM DRC and this response and revised geometry for almost all the buildings traced for this project. This is one more example that we should not accept beginners for these tasks and continue to propose to use JOSM until a better workflow can be established with beginners.<br></div><div><br></div><div><div><div><span><div>JOSM is a major editor for quality mapping and validating in OSM. But by default, every time I reconnect to the TM, iD is proposed by default (the first in the list) and the TM do not remember my choices. For tasks where we restrict access to intermediate contributors and to JOSM, this is not the best solution for Project coordinators to assure quality of data.<br></div></span><div><span><div><br></div><div>An other problem surged recently. What a surprise to me when selecting from the <span><span>Production HOT Tasking Manager 3</span></span> to use the JOSM editor to see the TM opening <span>a window with an Ambiguous message</span> </div></span></div></div><div><span></span><br></div><div><br></div><div><span>Contact with JOSM Failed<br>JOSM remote control did not respond. Do you have JOSM <br>running and configured to be controlled remotely? </span><br></div><div><span><div><br></div></span><div><div><span><div>+--------------------------------------------------------</div></span></div><div><span></span> +--------+ +--------------------+<br></div><div> | Dismiss | | Stop Using JOSM |<br></div><div><span> +--------+ +--------------------+<br></span><span><div><span><div>+--------------------------------------------------------</div></span></div><span></span></span><br></div><div><div><div><span><div>I see two problems with this.</div><div><br></div></span></div><div><span></span>1. Connection problems to fix with JOSM. My editor was running and often I did already have received data with success before this window open. <span><span>I often have to click many times to succeed to send data to JOSM. And less often offen this morning but often with this window opening.</span></span><br></div><div><br></div><div>2. Ambiguous message on the quality of JOSM<br></div><div><span><div>I understand that this terminology is similar to buttons proposing to stop mapping. But it remains quite ambiguous. Clicking on the X button on the top right panel, there was no problem. But selecting Dimiss did lock the task. <br></div></span><div><span><div><div><span><div><br></div></span><div><span><div>This morning, I did a test trying to select more then one task and I was successfull to select / lock successsively 10 tasks. <br></div></span><div><span><div><span>See <a href="https://twitter.com/pierzen/status/1090626920620929026" rel="nofollow" target="_blank">https://twitter.com/pierzen/status/1090626920620929026</a></span><br></div></span><div><span><div><br></div><div>Claire Halleux from OSM RDC tested on her side if she could select one of these tasks. As expected, the task was locked.</div></span></div></div></div></div></div></span></div></div><div><span>See <a href="https://twitter.com/pierzen/status/1090673406561996800" rel="nofollow" target="_blank">https://twitter.com/pierzen/status/109067340656199680</a></span></div><span><div><br></div></span><br></div><div>I hope this help to enhance the TM.</div></div></div></div></div></div><div class="ydpa5f00e5asignature"><span style="font-style:italic;color:rgb(0, 0, 191);font-weight:bold;"> <br><font face="garamond, new york, times, serif">Pierre </font><br></span></div></div></div></body></html>