Official feedback thread - v1.3 - Schedules & Conversation

The place to get information and ask questions about everything to do with properly and successfully editing the Waze Map.

Use this forum for all general editing questions, and the sub-forums for specific types of Waze Map Editor features.

Moderators: Unholy, bextein

Re: Official feedback thread - v1.3 - Schedules & Conversati

Postby elle-emme » Sun Nov 10, 2013 6:48 pm

jasonh300 wrote:When you make the initial comment on a UR, you become responsible for that UR. Nobody else is going to get a notification that the reporter has replied.


Unless you follow the conversation as well.

So now, the lower level user has to ask for an unlock, or ask for someone else to fix the problem, creating additional complication.


As long as the lower-ranked editor does that, is it really such an issue? How is it any different than a low-ranked editor running across the same problem during their normal editing of the map and posting an unlock request in the forum?

We've worked on and tested this feature for 6 months now to make it a DIRECT communication between the editor and the reporter. Obviously this isn't how it's going to work now that everyone has access to it. This is quickly going to turn into an unmanageable mess.


If you worked on and tested it for six months, then how did this issue never come up? Did no one ever bring up the possibility of rank-locking conversations according to the rank lock of the road the UR was reported on?

edit: also, if it's such a big deal that plebeian editors are forbidden from initiating conversations on roads that are rank-locked and only patrician editors should do so, why isn't it addressed in the Wiki article about URs and conversations?
-Elle Emme
Area Manager, Portland (OR)/SW Washington Metro area
Now these points of data make a beautiful line/we're out of beta, we're releasing on time...
elle-emme
 
Posts: 101
Joined: Wed Mar 06, 2013 8:48 am
Location: Wilsonville, Oregon, USA
Has thanked: 41 times
Been thanked: 21 times

Re: Official feedback thread - v1.3 - Schedules & Conversati

Postby elle-emme » Sun Nov 10, 2013 1:34 am

jasonh300 wrote:How do we handle users with driven area permissions that allow them to start conversations in URs but have no ability to edit anything on major roads in the area because their level is too low, and therefore no hope of being able to solve anything?


Perhaps it wasn't your intention, but what I got from that statement is "what good are these useless low-ranked editors? All they can do is ask questions and then not be able to fix anything!"

Which, as a low-ranked editor, is rather offensive :|
-Elle Emme
Area Manager, Portland (OR)/SW Washington Metro area
Now these points of data make a beautiful line/we're out of beta, we're releasing on time...
elle-emme
 
Posts: 101
Joined: Wed Mar 06, 2013 8:48 am
Location: Wilsonville, Oregon, USA
Has thanked: 41 times
Been thanked: 21 times

Re: Official feedback thread - v1.3 - Schedules & Conversati

Postby elle-emme » Fri Nov 08, 2013 6:52 am

Don't know if it's possible, but some sort of restriction on closing a UR that has a conversation you're not involved in may be useful.

As it stands now: an error is reported. Editor A initiates a conversation for more information. Editor B comes along X period of time later, [doesn't read the conversation, can't figure out what's wrong,] marks it as not identified, and that's it unless the original reporter takes the time to report it again.

With the restriction enacted, Editor B can't close the report until Y period of time later unless certain conditions are met (they're AM/CM/staff, the report has been open for more than Z days, etc). Even if Editor B adds something to the conversation, there would still be a period of time before they can close it.

Just a rough idea that came to mind after having more than a couple URs closed out as not identified within a few hours of starting a conversation by some overly-enthusiastic and rambunctious editors :evil:
-Elle Emme
Area Manager, Portland (OR)/SW Washington Metro area
Now these points of data make a beautiful line/we're out of beta, we're releasing on time...
elle-emme
 
Posts: 101
Joined: Wed Mar 06, 2013 8:48 am
Location: Wilsonville, Oregon, USA
Has thanked: 41 times
Been thanked: 21 times

Re: Official feedback thread - v1.3 - Schedules & Conversati

Postby edsonajj » Sun Nov 24, 2013 9:03 pm

New Official feedback thread - v1.4 available, locking this one.
Image Edson Jiménez

Image
edsonajj
EmeritusChamps
EmeritusChamps
 
Posts: 2625
Joined: Wed Feb 01, 2012 6:32 pm
Location: México
Has thanked: 154 times
Been thanked: 1034 times

Official feedback thread - v1.3 - Schedules & Conversation

Postby edsonajj » Fri Nov 15, 2013 10:28 pm

ArtVictorP wrote:
edsonajj wrote:
ArtVictorP wrote:Before this feature, we didn't have to "keep an eye" on an UR, we just closed it as solved or unidentified at the moment. That's why it is said: "Ignorance is a bliss".

That depends more on your community than the comments feature, in México we already had a rule about not closing as "Not Identified" any reports for which the icon wow still yellow.


Good policy! May I know how good were its results?
It would be a good idea to apply it in Ecuador too.

In the cities where I'm most active it works well since I try and train the local editors an the correct practices... The biggest problem are the users who don't read the wiki (same as every tool and rule) but I try and get in contact with the newbies I notice to point them in the right direction.
Image Edson Jiménez

Image
edsonajj
EmeritusChamps
EmeritusChamps
 
Posts: 2625
Joined: Wed Feb 01, 2012 6:32 pm
Location: México
Has thanked: 154 times
Been thanked: 1034 times

Re: Official feedback thread - v1.3 - Schedules & Conversati

Postby edsonajj » Fri Nov 15, 2013 6:12 pm

ArtVictorP wrote:Before this feature, we didn't have to "keep an eye" on an UR, we just closed it as solved or unidentified at the moment. That's why it is said: "Ignorance is a bliss".

That depends more on your community than the comments feature, in México we already had a rule about not closing as "Not Identified" any reports for which the icon wow still yellow.
Image Edson Jiménez

Image
edsonajj
EmeritusChamps
EmeritusChamps
 
Posts: 2625
Joined: Wed Feb 01, 2012 6:32 pm
Location: México
Has thanked: 154 times
Been thanked: 1034 times

Re: Official feedback thread - v1.3 - Schedules & Conversati

Postby edsonajj » Thu Nov 07, 2013 7:21 pm

The three warning system seems like too much. I would opt to send the initial request for info, a friendly reminder a couple of days later (warning it could be marked as not identified) and if no response is obtained simply closing the report.
Image Edson Jiménez

Image
edsonajj
EmeritusChamps
EmeritusChamps
 
Posts: 2625
Joined: Wed Feb 01, 2012 6:32 pm
Location: México
Has thanked: 154 times
Been thanked: 1034 times

Re: Official feedback thread - v1.3 - Schedules & Conversati

Postby edsonajj » Thu Nov 07, 2013 4:51 am

trooster10 wrote:1. "env=usa" is required at the end of the editor URL in order to access the restrictions and conversations panels.

Maybe for users in the US and Canada, not true for the rest of the world.
Image Edson Jiménez

Image
edsonajj
EmeritusChamps
EmeritusChamps
 
Posts: 2625
Joined: Wed Feb 01, 2012 6:32 pm
Location: México
Has thanked: 154 times
Been thanked: 1034 times

Re: Official feedback thread - v1.3 - Schedules & Conversati

Postby CBenson » Sun Nov 24, 2013 3:20 am

I'm not sure I understand the question. Don't you just put them individually on the two segments?
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
EmeritusChamps
EmeritusChamps
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

Re: Official feedback thread - v1.3 - Schedules & Conversati

Postby CBenson » Tue Nov 12, 2013 12:04 pm

Oh, no they don't affect routing after they expire (at least the ones I've added that have expired don't affect routing).
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
EmeritusChamps
EmeritusChamps
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

PreviousNext

Return to Waze Map Editor

Who is online

Users browsing this forum: Baidu [Spider]