[New Page] - Diagnosing Update Requests & Map Problems
I decided to move this to a discussion of a potential new page on the Wiki. I started it in the Canned Response thread, but that is not completely relevant, just related.
It has occured to me for some time that we should document knowledge about how to resolve User Reports and Map Problems. Many of you are much more adept at this process than me, but together we could provide some information that educates other new editors and also shares ideas amongst experienced editors.
What I put together is really an experiment about how to convey this information. We might need to convey the same information in multiple ways.
One way is kind of a flowchart or pseudocode process for doing this that embodies process and knowledge. The other is more a list of observable and tools that can be used as piecemeal concepts or like an encyclopedia. I didn't consider other formats in this page yet, like tables, etc. I was trying to keep it simple. New editors would eventually remember most this information from experience and only return to it for bizarre items -- a section I have conceived but not put down yet.
This is really like an artificial intelligence diagnostic system, but we have to do it in a linear written format. I am not interested in embodying this in a flowchart or some other complicated format since we mostly just have the Wiki.
In any case, here is what I have so far...
https://wiki.waze.com/wiki/User:Vectors ... Rs_.26_MPs
It has occured to me for some time that we should document knowledge about how to resolve User Reports and Map Problems. Many of you are much more adept at this process than me, but together we could provide some information that educates other new editors and also shares ideas amongst experienced editors.
What I put together is really an experiment about how to convey this information. We might need to convey the same information in multiple ways.
One way is kind of a flowchart or pseudocode process for doing this that embodies process and knowledge. The other is more a list of observable and tools that can be used as piecemeal concepts or like an encyclopedia. I didn't consider other formats in this page yet, like tables, etc. I was trying to keep it simple. New editors would eventually remember most this information from experience and only return to it for bizarre items -- a section I have conceived but not put down yet.
This is really like an artificial intelligence diagnostic system, but we have to do it in a linear written format. I am not interested in embodying this in a flowchart or some other complicated format since we mostly just have the Wiki.
In any case, here is what I have so far...
https://wiki.waze.com/wiki/User:Vectors ... Rs_.26_MPs
Re: [New Page] - Diagnosing Update Requests & Map Problems