The Data Working Group (DWG) recommendation for suspected vandalism is to contact the editor first. Contacting through the changeset comments provides an open discussion platform that also enables the DWG to view the entire discussion and decide if and what intervention is needed on their behalf, in cases of repeated vandalism.
Did you contact BMM994 in any way before posting here? He/she may or may not be reading the posts here.
Albarshat shunka, Marhaba (and for all the others too)
Notice that before you started changing names of Arab places to arabic, all the arab places inside the State of Israel was named in Hebrew, so it looks to me like your editions were vandalist. but if it’s agreed to name arab places in Israel in arabic only, it will be fine.
You also changed the name of Judea Desert Nature Reserve to Arabic, but I changed it back to English because it is not an Arab place. Originaly i named it in English and not in Hebrew or Arabic to prevent argument about who is “the owner” of it. In ground it is on area B, but both of the Israeli Authorities and The Palestinian Authority doing what they want there.
I agree with dsh. Let’s not use the word “vandalism” lightly and assume good faith, this is probably just a mistake or a misunderstanding of conventions.
Some people seem to try taking this too far and renaming places where there’s obviously a Hebrew speaking majority to Arabic. (Recently Ashkilon’s name was changed to Arabic and was reverted). This is not acceptable.
Albarshat shunka, please take care to preserve name:he and not destroy data regardless, if only “name” is present, please make surecopy it to “name:he” before putting the Arabic name.
Are there any objections to the following Wiki guideline?
Are there any objections to this related guideline?
Disclaimer: This is a guideline written by me, but there was a discussion with the community.
The rationale is: The name tag can get messy and multilingual due to edits similar to Albarshat shunka’s, but this guideline guarantees name:he is always present and is Hebrew, and name:ar is often present and is Arabic. SafwatHalaby_bot enforces this guideline by copying over name to name:he if “name” is detected to be Hebrew, (or to name:ar if “name” is detected to be Arabic)
I agree that we should encourage both name:he and name:ar to be set with the appropriate values on any feature that has a name at all. (Not just in Israel, by the way; some major streets in Berlin have name:he tags, and that’s absolutely fine.)
Aside: perhaps we should document our conventions on that wiki page too? So tourists who map in Israel know what our conventions are?
Not an objection to the guideline, but a question: due to this guideline, when I add, say, a convenience store, I have to add its name twice. Could we perhaps document to mappers that they can set either name or name:he, and the other one will be set automatically by the bot? The idea is to reduce the workload on the volunteer human mappers.
A properly debugged bot never makes mistakes. Humans, on the other hand…
The bot can set the other one automatically, yes. The bigger problem is when name and name:he already exist, but a human changes one of them and forgets the other. The bot is capable of detecting this and changing the forgotten one, but some didn’t agree to this feature, so it’s disabled.
The main argument against it is: “what if the new value is wrong? Humans should manually review it and a bot shouldn’t auto copy it”. But I think humans should manually review all edits regardless, via Osmcha or the like. Any new edit could be wrong.
Yes, it’s unrealistic; regardless of what the bot does, some bad human edits will make it through.
It doesn’t matter anymore since I’ve settled on just letting the bot print logs that are manually inspected (in the case of name/name:he mismatch)
Note that with the proper filter*, reviewing all Israel changes is possible, and rather easy via Osmcha and I regularly do it. (It has useful quick links to other viewers like Achavi, Deep History, etc). Though for experienced users, I only skim their edits, which are the majority of edits.
Bbcode seems to dislike the filter URL. copy it from here:
I always review a sample of the bot’s changes before upload. It’s not a fully automatic bot. Feel free to make further reviews, all changesets are logged.