Translations:Update request/1/en Geschiedenis weergeven

(Importing a new version from external source)
Geen bewerkingssamenvatting
 
(5 tussenliggende versies door 2 gebruikers niet weergegeven)
Regel 1: Regel 1:
==Update Requests==
==Update Requests==
The global [https://wazeopedia.waze.com/wiki/Global/Update_Requests_in_Waze_Map_Editor Wiki page on Update Requests] contains an extensive description of all aspects of the User Request. This page describes the BeNeLux approach.
The global [https://wazeopedia.waze.com/wiki/Global/Update_Requests_in_Waze_Map_Editor Wiki page on Update Requests] contains an extensive description of all aspects of the Update Request. This page describes the BeNeLux approach.
<br />
<br />
[[File:UR-request-pop-up.png|right]] Update requests (UR) are submitted by [[Waze app|app]] users to report issues with the routing or the map. An icon with the small Waze icon [[File:Request_pin_open-low.png|20px]] is added to the editing map in the Update Requests [[Waze_Map_Editor#Layers_menu|layer]]. The reporters name is not displayed. Clicking on the UR icon a panel with the UR details is displayed. The UR is of a certain type, has a date time displayed. Sometimes the ''Waze provided route'' and/or the ''User drive'' are available plus some words from the reporter.<br />
[[File:UR-request-pop-up.png|right]] Update requests (UR) are submitted by [[Waze app|app]] users to report issues with the routing or the map. An icon with the small Waze icon [[File:Request_pin_open-low.png|20px]] is added to the editing map in the Update Requests [[Waze_Map_Editor#Layers_menu|layer]]. The reporters name is not displayed. Clicking on the UR icon a panel with the UR details is displayed. The UR is of a certain type, has a date time displayed. Sometimes the ''Waze provided route'' and/or the ''User drive'' are available plus some words from the reporter.<br />
Regel 7: Regel 7:
The conversation start with your first response, often asking for information. When the reporter doesn't react a friendly reminder should be send. After two reminders the UR can be closed with '''Mark as not identified'''. In case the reporter replies on your response the problem might be solved. Perhaps an explanation is sufficient, sometimes the map should be corrected. If the problem is fixed the UR can be closed with '''Mark as closed'''.<br />
The conversation start with your first response, often asking for information. When the reporter doesn't react a friendly reminder should be send. After two reminders the UR can be closed with '''Mark as not identified'''. In case the reporter replies on your response the problem might be solved. Perhaps an explanation is sufficient, sometimes the map should be corrected. If the problem is fixed the UR can be closed with '''Mark as closed'''.<br />
<br />
<br />
The e-mail that is send to the reporter already contains: <i>You can reply via the Waze app or [link] in the Waze Map Editor. It is not possible to respond to this e-mail, this is a no-reply address. If you have any other questions about Waze or would like to discuss this issue further, please join our Slack channel.</i><br>
<br>
'''First reply:'''
'''First reply:'''
* Thank user for reporting the issue.
* Thank user for reporting the issue.
Regel 12: Regel 14:
* If your reply is not on the date of the UR itself give an indication of the day and time.
* If your reply is not on the date of the UR itself give an indication of the day and time.
* Ask for more information necessary to solve this UR.
* Ask for more information necessary to solve this UR.
* Indicate that they cannot answer directly by email because of the no-reply@waze.com address used. You could include an email address of your own allowing the reporter to answer by email replacing the no-reply@waze.com address with yours.
* Sign off with your name and optionally an e-mail address.
* Sign off with your name.
<br />
<br />
'''Procedure'''
'''Procedure'''
* First reply '''>''' First reminder after 5 days '''>''' Optional second reminder 4 days later '''>''' Mark as Not identified  [[File:UR-mark-as-not-identified.png|85px]] 2 days later.
* First reply '''>''' First reminder after 3 days '''>''' Optional second reminder 3 days later '''>''' Mark as Not identified  [[File:UR-mark-as-not-identified.png|85px]] 3 days later.
* React on reporter's answers untill a conclusion is reached '''>''' Mark as Solved [[File:UR-mark-as-solved.png|85px]] 2 days later to give the reporter the opportunity to give a last reaction.  
* React on reporter's answers until a conclusion is reached '''>''' Mark as Solved [[File:UR-mark-as-solved.png|85px]] 3 days later to give the reporter the opportunity to give a last reaction.  
<br />
<br />
'''Etiquette'''<br />
'''Etiquette'''<br />
When you respond to user reports, you are interacting with the original reporter, and you may also be interacting with other Waze editors who respond to the same request. The first responding editor has no ownership of the problem resolution. Other editors should not step in, other than to send a next reminder to the reporter, or unless they think the owner needs help (whether the owner realizes it or not), or the first reporting editor has abandoned/lost track of the report over time.<br />
When you respond to user reports, you are interacting with the original reporter, and you may also be interacting with other Waze editors who respond to the same request. The first responding editor has no absolute ownership of the problem solution. Other editors should not step in, other than to send a next reminder to the reporter, or unless they think the owner needs help (whether the owner realizes it or not), or the first reporting editor has abandoned/lost track of the report over time.<br />
* Always react friendly, helpful.
* Always react friendly, helpful.
* Don't use jargon
* Don't use jargon
* Keep your reactions short and to the point.
* Keep your reactions short and to the point.

Huidige versie van 25 feb 2022 om 15:59

Informatie over bericht (bijdragen)
Dit bericht heeft geen documentatie. Als u weet waar of hoe dit bericht wordt gebruikt, dan kunt u andere gebruikers helpen door documentatie voor dit bericht toe te voegen.
Berichtdefinitie (Update request)
==Update Requests==
De globale <i>[https://wazeopedia.waze.com/wiki/Global/Update_Requests_in_Waze_Map_Editor Wiki page on Update Requests]</i> bevat een uitgebreide beschrijving van alle aspecten van het Update Request. De pagina hier beschrijft de Nederlandse aanpak.
<br />
[[File:UR-request-pop-up.png|right]] Updateverzoeken (UR) worden ingediend door [[Waze app|app]]-gebruikers om problemen met de route of de kaart te melden. Een pictogram met het kleine Waze-pictogram [[File:Request_pin_open-low.png|20px]] is toegevoegd aan de bewerkingskaart in de Update Requests [[Waze_Map_Editor#Layers_menu|layer]]. De naam van de melder wordt niet weergegeven. Als u op het UR-pictogram klikt, wordt een paneel met de UR-details getoond. De UR is van een bepaald type en heeft een datum en tijd. Soms zijn de ''door Waze verstrekte route'' en/of de ''Gebruikersrit'' beschikbaar plus enkele woorden van de melder.<br />
<br />
'''Conversatie'''<br />
De conversatie begint met jouw eerste reactie: doorgaans vragen om informatie. Als de melder niet reageert, moet er een vriendelijke herinnering worden gestuurd. Na twee herinneringen kan de UR worden afgesloten met '''Markeer als niet geïdentificeerd'''. Als de melder op uw antwoord reageert, kan het probleem mogelijk opgelost worden. Misschien is een uitleg voldoende, soms moet de kaart worden gecorrigeerd. Als het probleem is opgelost, kan de UR worden afgesloten met '''Markeer als opgelost'''.<br />
<br />
In de e-mail die naar de melder gaat staat al standaard: <i>Je kan antwoorden via de Waze-app of [link] in de Waze Map Editor. Reageren op deze e-mail is niet mogelijk, dit is een no-reply adres. Heb je nog andere vragen over Waze of wil je dit probleem verder bespreken, meld je dan even aan op ons Slack-kanaal.</i><br>
<br>
'''Eerste antwoord:'''
* Bedank de gebruiker voor het melden van het probleem.
* Geef de straatnaam/wijk aan zodat de melder weet waar hij/zij de melding gemaakt heeft. (Dit kan verschil maken bij meerdere meldingen op die dag door deze melder.)
* Vermeld de dag en tijd wanneer uw reactie niet op de dag van de UR is.
* Vraag om meer informatie die nodig is om deze UR op te lossen.
* Onderteken met uw naam en een optioneel e-mailadres.
<br />
'''Procedure'''
* Eerste antwoord '''>''' Eerste herinnering na 3 dagen '''>''' Optionele tweede herinnering 3 dagen later '''>''' Markeer als Niet geïdentificeerd [[File:UR-mark-as-not-identified.png|85px]] 3 dagen later.
* Reageer op de melder zijn antwoorden totdat een conclusie is bereikt '''>''' Markeer als opgelost [[File:UR-mark-as-solved.png|85px]] 3 dagen later om de melder de gelegenheid te geven tot een laatste reactie. 
<br />
'''Etiquette'''<br />
Wanneer je reageert op gebruikersmeldingen, heb je een interactie met de oorspronkelijke melder en mogelijk ook met andere Waze-editors die op hetzelfde verzoek reageren. De eerste reagerende editor is niet de absolute eigenaar van de melding. Andere editors moeten niet tussenbeide komen, behalve om een ​​volgende herinnering naar de melder te sturen, of tenzij ze denken dat de eigenaar van de UR hulp nodig heeft (of de eigenaar het zich realiseert of niet), of wanneer de eerste editor het rapport heeft verlaten/uit het oog is verloren.<br />
* Reageer altijd vriendelijk, behulpzaam.
* Gebruik geen jargon
* Houd uw reacties kort en to the point.

Update Requests

The global Wiki page on Update Requests contains an extensive description of all aspects of the Update Request. This page describes the BeNeLux approach.

Update requests (UR) are submitted by app users to report issues with the routing or the map. An icon with the small Waze icon is added to the editing map in the Update Requests layer. The reporters name is not displayed. Clicking on the UR icon a panel with the UR details is displayed. The UR is of a certain type, has a date time displayed. Sometimes the Waze provided route and/or the User drive are available plus some words from the reporter.


Conversation
The conversation start with your first response, often asking for information. When the reporter doesn't react a friendly reminder should be send. After two reminders the UR can be closed with Mark as not identified. In case the reporter replies on your response the problem might be solved. Perhaps an explanation is sufficient, sometimes the map should be corrected. If the problem is fixed the UR can be closed with Mark as closed.

The e-mail that is send to the reporter already contains: You can reply via the Waze app or [link] in the Waze Map Editor. It is not possible to respond to this e-mail, this is a no-reply address. If you have any other questions about Waze or would like to discuss this issue further, please join our Slack channel.

First reply:

  • Thank user for reporting the issue.
  • Give streetname/area so the reporter knows about the location (could make a difference in case of multiple reports on that day by this reporter).
  • If your reply is not on the date of the UR itself give an indication of the day and time.
  • Ask for more information necessary to solve this UR.
  • Sign off with your name and optionally an e-mail address.


Procedure

  • First reply > First reminder after 3 days > Optional second reminder 3 days later > Mark as Not identified 3 days later.
  • React on reporter's answers until a conclusion is reached > Mark as Solved 3 days later to give the reporter the opportunity to give a last reaction.


Etiquette
When you respond to user reports, you are interacting with the original reporter, and you may also be interacting with other Waze editors who respond to the same request. The first responding editor has no absolute ownership of the problem solution. Other editors should not step in, other than to send a next reminder to the reporter, or unless they think the owner needs help (whether the owner realizes it or not), or the first reporting editor has abandoned/lost track of the report over time.

  • Always react friendly, helpful.
  • Don't use jargon
  • Keep your reactions short and to the point.