Reason for rejecting the PUR
I receive many complaints from new editors who find it frustrating that their Place Update Requests (PURs) are rejected by other editors without even receiving a notification, and especially without any explanation of why the request was denied.
"How are we supposed to know what we did wrong if we're never told the reason?" is by far the complaint I hear most often.
Because of this, I believe this is both a very valid and necessary improvement. I also believe Waze itself would agree, since the newer Suggest an Edit feature—such as adding house numbers or creating a new road—already includes the option to provide a reason for rejecting an edit. However, in practice, this still doesn't work as intended, because the editor who submitted the suggestion does not receive the rejection reason provided by the reviewing editor.
-
Ana Paula Helena commented
Muito importante esse feedback pra quem está começando até pra refinar as futuras edições.
-
Renato Parussolo commented
Acredito que será muito importante essa comunicação
-
RAZZOR - Software Cracking commented
Acho crucial, sou um editor iniciante e algumas das minhas sugestões foram recusadas sem nenhuma contato após, como eu tinha feito várias, sequer sei em qual local e porque motivos a recusa, ficando impossível aprender com meus erros e também, aperfeiçoar minhas sugestões.
-
Daniel Di Tommaso commented
Será muito útil, apesar de que tive que aprender na marra com as negativas do Tinder do AG.