Minnesota/Closures/Main: Difference between revisions Discussion View history

(*/Closures/Main*/)
m (*/Closures/Main*/)
Line 3: Line 3:
A topic about closures will be here soon!
A topic about closures will be here soon!


=== Update Requests ===
== Update Requests ==


An Update Request (UR) is a Map Issue reported by a user from the Waze client app. It is also a layer in the Map Editor. See [[Update_Requests_in_Waze_Map_Editor|update requests]] for more information.  
An Update Request (UR) is a Map Issue reported by a user from the Waze client app. It is also a layer in the Map Editor. See [[Update_Requests_in_Waze_Map_Editor|update requests]] for more information.  
Line 9: Line 9:
In {{RootPage2}}, we have adopted a 1/6/10 system for response to Update Requests.  
In {{RootPage2}}, we have adopted a 1/6/10 system for response to Update Requests.  


==== Day 1 ====
=== Day 1 ===
This is the first day the editor responds.  We typically want to answer a report within 24 hours, but this should be at least attempted within the first 3 days.   
This is the first day the editor responds.  We typically want to answer a report within 24 hours, but this should be at least attempted within the first 3 days.   


Line 16: Line 16:
"''"Thank you for reporting a [general error] through the Waze app. The report was not clear on what exactly happened at [this location]. Could you please explain the issue that occurred further?"''"
"''"Thank you for reporting a [general error] through the Waze app. The report was not clear on what exactly happened at [this location]. Could you please explain the issue that occurred further?"''"


==== Day 6 ====
=== Day 6 ===
If the reporter has not commented after 6 days of this initial comment a message should be sent reminding the reporter that we need more information about the problem they encountered to fix the issue.
If the reporter has not commented after 6 days of this initial comment a message should be sent reminding the reporter that we need more information about the problem they encountered to fix the issue.


Line 23: Line 23:
"''We apologize that we have not heard back from you to explain the issue further. We will need a response to fix the issue further. This ticket will be closed in 4 days if no response occurs.''"
"''We apologize that we have not heard back from you to explain the issue further. We will need a response to fix the issue further. This ticket will be closed in 4 days if no response occurs.''"


==== Day 10 ====
=== Day 10 ===
If the reporter still has not commented after 4 more days (10 days since initial comment) a message should be sent telling the reported that we were unable to fix the problem and this report is being closed.  The Update Request then needs to be closed as Not Identified.
If the reporter still has not commented after 4 more days (10 days since initial comment) a message should be sent telling the reported that we were unable to fix the problem and this report is being closed.  The Update Request then needs to be closed as Not Identified.


Line 30: Line 30:
"''We apologize that we still have not heard back from you about the issue. We have not found the issue and it could be that your map is giving you incorrect information. Please go to the Waze App, then go to Settings / Advanced Settings / Data Transfer and then Refresh Area of My Map to see if that improves anything. Due to no response, we are closing this ticket. You can submit another report if the issue is still present''"
"''We apologize that we still have not heard back from you about the issue. We have not found the issue and it could be that your map is giving you incorrect information. Please go to the Waze App, then go to Settings / Advanced Settings / Data Transfer and then Refresh Area of My Map to see if that improves anything. Due to no response, we are closing this ticket. You can submit another report if the issue is still present''"


==== Rural Areas ====
=== Rural Areas ===
While we would like to have every inch of {{RootPage2}} covered with a network of editors, we are not currently at that level of community involvement.  The 1/6/10 rule has been set as the standard for areas with [[#Area_Managers|Area Managers]] and active editors; However, in many areas, there is very little editor coverage. That being said, use good judgment in these areas as there may be Update Requests that are greater than 30 or even 60 days old. There is no penalty or negative perception to answering these, quite the opposite.  Please, still take the time to send the reporter a message to see if they can remember the issue and allow them additional time to provide more information.  In these areas, we will follow a 1/15/30 rule.  Day 1 is the first day an editor responds.  Day 15 is the warning message stating the issue will be closing in 15 days.  Day 30 to close out the ticket.   
While we would like to have every inch of {{RootPage2}} covered with a network of editors, we are not currently at that level of community involvement.  The 1/6/10 rule has been set as the standard for areas with [[#Area_Managers|Area Managers]] and active editors; However, in many areas, there is very little editor coverage. That being said, use good judgment in these areas as there may be Update Requests that are greater than 30 or even 60 days old. There is no penalty or negative perception to answering these, quite the opposite.  Please, still take the time to send the reporter a message to see if they can remember the issue and allow them additional time to provide more information.  In these areas, we will follow a 1/15/30 rule.  Day 1 is the first day an editor responds.  Day 15 is the warning message stating the issue will be closing in 15 days.  Day 30 to close out the ticket.   


Line 37: Line 37:
"''Thank you for your report! I apologize for the late response, we are volunteer editors and in some areas there are not many of us.  You reported a General Error near [this location] in [City], {{RootPage2}} way back on 9 Dec 14. Do you remember what issue you encountered?''"
"''Thank you for your report! I apologize for the late response, we are volunteer editors and in some areas there are not many of us.  You reported a General Error near [this location] in [City], {{RootPage2}} way back on 9 Dec 14. Do you remember what issue you encountered?''"


=== Unlock Requests ===
== Unlock Requests ==


Sometimes, you will come to an issue with a road, but you do not have a sufficient lock level to fix the situation. [http://www.waze.com/forum/viewforum.php?f=622 Click here] if you need to setup an unlock request.  Please pay attention to the top of this forum where it will give clear instructions on how to create an unlock request.
Sometimes, you will come to an issue with a road, but you do not have a sufficient lock level to fix the situation. [http://www.waze.com/forum/viewforum.php?f=622 Click here] if you need to setup an unlock request.  Please pay attention to the top of this forum where it will give clear instructions on how to create an unlock request.

Revision as of 12:26, 26 February 2015

Update Requests

An Update Request (UR) is a Map Issue reported by a user from the Waze client app. It is also a layer in the Map Editor. See update requests for more information.

In Minnesota, we have adopted a 1/6/10 system for response to Update Requests.

Day 1

This is the first day the editor responds. We typically want to answer a report within 24 hours, but this should be at least attempted within the first 3 days.

Example

""Thank you for reporting a [general error] through the Waze app. The report was not clear on what exactly happened at [this location]. Could you please explain the issue that occurred further?""

Day 6

If the reporter has not commented after 6 days of this initial comment a message should be sent reminding the reporter that we need more information about the problem they encountered to fix the issue.

Example

"We apologize that we have not heard back from you to explain the issue further. We will need a response to fix the issue further. This ticket will be closed in 4 days if no response occurs."

Day 10

If the reporter still has not commented after 4 more days (10 days since initial comment) a message should be sent telling the reported that we were unable to fix the problem and this report is being closed. The Update Request then needs to be closed as Not Identified.

Example

"We apologize that we still have not heard back from you about the issue. We have not found the issue and it could be that your map is giving you incorrect information. Please go to the Waze App, then go to Settings / Advanced Settings / Data Transfer and then Refresh Area of My Map to see if that improves anything. Due to no response, we are closing this ticket. You can submit another report if the issue is still present"

Rural Areas

While we would like to have every inch of Minnesota covered with a network of editors, we are not currently at that level of community involvement. The 1/6/10 rule has been set as the standard for areas with Area Managers and active editors; However, in many areas, there is very little editor coverage. That being said, use good judgment in these areas as there may be Update Requests that are greater than 30 or even 60 days old. There is no penalty or negative perception to answering these, quite the opposite. Please, still take the time to send the reporter a message to see if they can remember the issue and allow them additional time to provide more information. In these areas, we will follow a 1/15/30 rule. Day 1 is the first day an editor responds. Day 15 is the warning message stating the issue will be closing in 15 days. Day 30 to close out the ticket.

Example:

"Thank you for your report! I apologize for the late response, we are volunteer editors and in some areas there are not many of us. You reported a General Error near [this location] in [City], Minnesota way back on 9 Dec 14. Do you remember what issue you encountered?"

Unlock Requests

Sometimes, you will come to an issue with a road, but you do not have a sufficient lock level to fix the situation. Click here if you need to setup an unlock request. Please pay attention to the top of this forum where it will give clear instructions on how to create an unlock request. If you want to check to see if there are any Unlock Requests that you can handle, Click Here to check all open reports for Minnesota. Anything showing the green check mark means it has been completed.