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 SuperDave1426 » Mon Nov 11, 2013 1:01 am

AlanOfTheBerg wrote:I didn't even think URs showed up outside a user's editable area, which means they could have rights to fix the issues within that area. If URs show up everywhere now, that's a WME issue which should be fixed.


I think his big issue is with URs and MPs that editors can get to, but can't "do anything about" because the road where the note appears is locked at a rank higher than the editor. (Which as far as I'm concerned is a NON issue for the reasons I gave in my reply earlier in this thread.)

Just as a FYI: I'm able to see URs and MPs outside of my editable area and even open them up to see what the reported issue is; however, I can't close them. Which is as it should be. :-)

I haven't looked to see if a UR outside of my editable area will let me start or add to a conversation, though. I think there's nothing wrong with being able to see a UR/MP outside of one's editable area, but I could see a possible issue if you can start or add to a conversation outside of your editable area, given the inability to actually close the UR as Solved or NI.
SuperDave1426
Country Manager
Country Manager
 
Posts: 865
Joined: Wed Oct 16, 2013 5:27 pm
Location: Nevada, USA
Has thanked: 79 times
Been thanked: 248 times

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

Postby AlanOfTheBerg » Sun Nov 10, 2013 11:22 pm

@jasonh300 I think you're being overly critical and restrictive. This is a collaborative environment and the handful of country managers can't fix everything. We've got to have newer editors looking at URs and looking to solve map issues too.

I didn't even think URs showed up outside a user's editable area, which means they could have rights to fix the issues within that area. If URs show up everywhere now, that's a WME issue which should be fixed.

elle-emme wrote:
jasonh300 wrote: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?

I agree. Just because there is a conversation going on, asking for an unlock is no different now than before. Hundreds of editors every month ask for unlocks because of a UR they can't resolve due to rank. This is a normal part of the editing workflow. This is not an additional complication. We've been doing this for years.

jasonh300 wrote: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.

I disagree. Now I don't have to worry about trying to solve ALL URs in my area using conversations. What I didn't think about in testing is a way to quickly, visually ID URs which I have participated in. Like the Participated list for the forum in Tapatalk.

elle-emme wrote: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?

But a good % of URs aren't about the road they are reported on anyway, so that's one reason it didn't come up. And I don't think it is worth the effort to pursue as a feature. The whole "issue" with multiple editors being involved in URs and the possible problems with it was partly due to not a lot of overlap between editors. But even before public release, we had issues with URs being closed improperly and having a conversation tool is not going to change it.

elle-emme wrote: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?

IMO, it isn't, and therefore, it isn't.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23598
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1124 times
Been thanked: 4781 times

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

Postby Machete808 » Sun Nov 10, 2013 10:55 pm

Just to add: So many URs have to do with external search engines delivering a bad location. A new editor can fix those as well as a ranking one by submitting the correction to the third-party site (still think the wiki could include a fuller tutorial on that aspect).


Sent from my iPhone using Tapatalk
Machete808
Waze Mentor
Waze Mentor
 
Posts: 1389
Joined: Mon May 28, 2012 12:36 am
Location: Kaneohe, HI
Has thanked: 220 times
Been thanked: 258 times

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

Postby russblau » Sun Nov 10, 2013 10:02 pm

jasonh300 wrote:This isn't about comments. It's about misrepresenting yourself as a person who can solve a problem when you can't. That will drive users away just as quickly as lying to them about having solved a UR when you haven't done anything.

I guess that is possible, depending on what the comment says, but just asking for additional information or directing the user to information in the Wiki (for example) would not be "misrepresentation" in any way.

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. So now, the lower level user has to ask for an unlock, or ask for someone else to fix the problem, creating additional complication.

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.


It sounds like you want Waze to design and implement a feature different from the one they actually implemented. You want a PRIVATE communication between one editor and one reporting user, but Waze has designed a communication tool that allows collaboration among multiple map editors. Perhaps you don't like collaboration. In my opinion, it's a good thing, but I understand that everyone has their own opinion.
russblau
State Manager
State Manager
 
Posts: 1192
Joined: Fri Oct 19, 2012 11:36 pm
Has thanked: 170 times
Been thanked: 493 times

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

Postby Bigbear3764 » Sun Nov 10, 2013 8:07 pm

I think it has been working well in my area. I get to see who the editors are in my area asking for info, watch what they saying back to them, and they get to see how I'm handling them. Been a good learning experience for all. Some have asked for help when they can't fix the problem. Some have been closed and I don't know what they did to fix it. But it's a learning experience for all.

You really don't know till you ask what the problem was and what rank is needed to fix it. Most of mine are complaints about being directed down alleys.


Sent from my iPhone using Tapatalk
Bigbear3764
Country Manager
Country Manager
 
Posts: 2583
Joined: Fri Feb 10, 2012 8:02 pm
Location: Island Lake, IL USA
Has thanked: 205 times
Been thanked: 939 times

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

Postby SuperDave1426 » Sun Nov 10, 2013 7:49 pm

elle-emme wrote:
jasonh300 wrote: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?


Absolutely +1.

When I'm editing whatever and need to have someone else apply the change because there's a junction node, etc., that's attached to something locked at a rank higher than me, I post the usual unlock/update request and it gets handled by someone. Nobody seems to complain about all that extra complication because I couldn't just handle it myself.

I completely fail to see how this is any different. If I'm browsing and come across something as incredibly "informative" as a UR containing "General error (user reported)" with no describing text and nothing showing up in the drive or waze-provided routing that gives me a clue as to the problem, I would have simply closed it as NI in the days before we had this feature - regardless of what rank the road was locked at because there's nothing to go on. NOBODY would be able to solve that, regardless of rank. Now we DO have the feature, so I see absolutely nothing wrong with making the comment to ask the reporter for more information. Then, simply follow the procedure as outlined in the Wiki: Give it a few days and if there's no reply from the reporter, close the UR. If there is a reply, then I've now got the same information that I would be giving in an unlock/update request I make for myself. Treat it at that point like any other unlock/update, make the request and when it's taken care of, close the UR in addition to the usual thank/solved in that thread.

Using the above example (General error), I've already run into three of those on roads I could edit where the reply was, essentially, "Oops." They hit it by accident or didn't realize they had done it. Problem solve, UR solved, done. In the case of a rank locked road, I wouldn't even have to post the unlock/update request since the UR itself can be closed.
SuperDave1426
Country Manager
Country Manager
 
Posts: 865
Joined: Wed Oct 16, 2013 5:27 pm
Location: Nevada, USA
Has thanked: 79 times
Been thanked: 248 times

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

Postby Thortok2000 » Sun Nov 10, 2013 7:42 pm

@jasonh - If I saw a report that needed additional information and I knew what information I needed to ask for, I would go ahead and ask for that information. Only when I knew what needed to be done to fix it would I even look to see what the locks are in that area. If I then didn't have a high enough rank to do the fix myself, I'd go to the unlock forum and request the correct fix. If I didn't know how to do the fix, I'd go to the proper forum and ask for help on how to do the fix.

This is how I learn and grow as an editor. This is the way it's done.

There's a difference between a NEW editor and a BAD editor. A bad editor can potentially be any rank, although you do tend to see more of them at lower rank, it's true. They usually get weeded out before rising in rank.

It's one thing to request to be able to prevent bad editors from messing things up, but it's another to block all new editors completely.

If anything, you should be able to lock a region so that if a report shows up in that region, someone below the lock level cannot 'solve' or 'not identified' the reports in that area. But I don't think you should block comments. The rank of the commenter shows up in the comment anyway, and anyone else can easily follow and/or join the conversation. And if someone says the wrong thing, you can report the editor for that and/or PM them about what they did wrong.

~

What I'd like to see is an option to automatically follow all UR's in my editable area since I'm going to do that anyway even if I'm not the first to reply (although I usually am since I check the Waze map several times a day.) Perhaps even getting an e-mail notification that a UR (or automatic report) has appeared, and then I won't have to obsessively check the map anymore. That would rock.
Thortok2000
Area Manager
Area Manager
 
Posts: 722
Joined: Tue Oct 15, 2013 1:01 am
Location: Greenville, SC
Has thanked: 190 times
Been thanked: 141 times

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

Postby jasonh300 » Sun Nov 10, 2013 7:33 pm

elle-emme wrote:Unless you follow the conversation as well.


Creating more work in having to pick out which URs have been commented on by unqualified users.

elle-emme wrote: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?


Once again, creating more unnecessary work.

elle-emme wrote: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?


Because during the testing phase, no unqualified users had access to it, so it wasn't evident how huge of a problem this would be come. But yes, all sorts of locking schemes were discussed...none were implemented.

elle-emme wrote: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?


The wiki can be addressed, but it's not really relevant because anyone who tries this should be able to see that they can't do anything to help and move on to other things that will actually improve the map.
jasonh300
 
Posts: 7567
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA, USA
Has thanked: 402 times
Been thanked: 978 times

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
 
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 jasonh300 » Sun Nov 10, 2013 6:23 pm

russblau wrote:Wow! Elle-emme, rest assured that not everyone feels that way. To me, if an editor's questions or comments are helping to clarify or resolve an issue, then their rank doesn't matter. For that matter, anyone whose comments aren't constructive shouldn't be editing, and in that case their rank shouldn't matter either.


This isn't about comments. It's about misrepresenting yourself as a person who can solve a problem when you can't. That will drive users away just as quickly as lying to them about having solved a UR when you haven't done anything.

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. So now, the lower level user has to ask for an unlock, or ask for someone else to fix the problem, creating additional complication.

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.
jasonh300
 
Posts: 7567
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA, USA
Has thanked: 402 times
Been thanked: 978 times

PreviousNext

Return to Waze Map Editor

Who is online

Users browsing this forum: No registered users