openstreetmap / iD

🆔 The easy-to-use OpenStreetMap editor in JavaScript.
https://www.openstreetmap.org/edit?editor=id
ISC License
3.34k stars 1.2k forks source link

Make issue warning clearer when offering to add `brand:wikidata` or `brand:wikipedia` #6517

Open matkoniecz opened 5 years ago

matkoniecz commented 5 years ago

Whole point of brand:wikidata and brand:wikipedia is that name alone (or combined with other indicator like object type and location) is not sufficient to identify object as belonging to a specific brand.

Despite that iD is asking user to add brand:wikidata and brand:wikipedia and describes this action as "XYZ looks like a brand with nonstandard tags" and offers user to "Upgrade the tags".

There are multiple problems here

See for example http://preview.ideditor.com/master/#background=Bing&disable_features=boundaries&id=w488118123&map=20.29/38.74517/-75.15497

Selection_004

After #6443 it was improved a bit but is still far from OK version.

Note also that

All features of the same brand should be tagged the same way.

displayed after clicking "i" is wrong - for example shops of the same brand may have different opening_hours or other tags.

quincylvania commented 5 years ago

Whole point of brand:wikidata and brand:wikipedia is that name alone (or combined with other indicator like object type and location) is not sufficient to identify object as belonging to a specific brand.

Despite that iD is asking user to add brand:wikidata and brand:wikipedia and describes this action as "XYZ looks like a brand with nonstandard tags" and offers user to "Upgrade the tags".

The message says "looks like", which means that iD isn't sure. The user is still making their own judgement. "Ignore this issue" is an option.

iD is adding new tags, not "upgrading" ones that are present, so description is misleading

Upgrading means iD will update to the preferred tagging for the same thing. Whether this involves adding, removing, or changing tags isn't really a factor.

such heuristic usually gives good results, but there are some false positives. iD must mention to user that he is responsible for verifying this and that suggested change may be wrong

Maybe. The wording doesn't imply absolute certainty and the user is always responsible for their edits anyway.

what is actually changed should be displayed in form readable to user

It is when you click the info button. We're not going to show this all the time since it takes up a lot of space.

All features of the same brand should be tagged the same way.

displayed after clicking "i" is wrong - for example shops of the same brand may have different opening_hours or other tags.

The message doesn't mean that all the tags should be identical. It's like answering "how should I tag a new Walmart?" A new Walmart should be tagged the same as an old Walmart. If this wording causes real problems we can change it.

matkoniecz commented 5 years ago

The user is still making their own judgement. "Ignore this issue" is an option.

"Upgrade the tags" vs "Ignore the issue" at least for me sounds like, "are you willing to fix this issue", not "please check is it correct".

Note that it is combined with (by default) hiding what will actually happen.

Upgrading means iD will update to the preferred tagging for the same thing. Whether this involves adding, removing, or changing tags isn't really a factor.

My problem here was "XYZ looks like a brand with nonstandard tags" message - there are no "nonstandard tags" here what is even more confusing. "XYZ looks like a brand where tags may be added" would be better.

For cases where iD changes/removes existing tags "XYZ looks like a brand where tags may be changed" would be better.

matkoniecz commented 5 years ago

In general, I think that it should be "Mark as brand XYZ {Brand XYZ logo image} {link to wikipedia/wikidata page}" to allow proper verification by tagging user.

1ec5 commented 5 years ago

The message says "looks like", which means that iD isn't sure. The user is still making their own judgement. "Ignore this issue" is an option.

“Looks like” is the only thing about this warning that equivocates. A typical user unfamiliar with the purpose of the QIDs will see a yellow background, ⚠️ icon, and the negative words “issue” and “nonstandard” and conclude that ignoring isn’t the right thing to do.

The upgrade message is intended to be merely a helpful suggestion, so it should look informational, not alerting. For example, a light blue background, ℹ️ icon, and even a “Did you mean?” kind of message would go a long way toward ensuring an unbiased appearance.

In general, I think that it should be "Mark as brand XYZ {Brand XYZ logo image} {link to wikipedia/wikidata page}" to allow proper verification by tagging user.

Yes, showing the brand’s icon would help the user immediately determine whether the detection was accurate or ignorable. It would be a nice complement to the use of brand icons in the preset search results. How about replacing the ⚠️ with a slightly scaled-down copy of the brand icon?

matkoniecz commented 5 years ago

To be more specific, here is my mockup of solution that

Selection_006

For comparison current behavior:

Selection_004

1ec5 commented 5 years ago

⚠️ Mark this object as operated uder brand
described at Citizens Bank (South Bend,
Indiana)
Wikipedia page?

I find this wording a bit confusing too. Without knowing the purpose of this warning, the fact that it’s presented as a warning would probably still lead an inexperienced mapper to upgrade the feature without checking. An icon and more descriptive message could potentially overcome the warning-like presentation:

Does this feature belong
to the Noah's Bagels brand?

matkoniecz commented 5 years ago

Yeah, that would be even better.

CloCkWeRX commented 5 years ago

Does this feature belong to the Noah's Bagels brand?

A related issue that might be worth revisiting; on selection of the wikidata brand via a preset, the name is often overridden; then locked.

There seem to be two styles of "brand" vs "name" - for example, a car dealership which is branded with Holden (https://www.wikidata.org/wiki/Q29281) but named "Duttons Holden": image

This is likely because the dealer is independent, but has signed up to a franchise or similar; vs more "corporate owned" stores; which rely on strictly the branding:

image

... even if internally or on websites, they refer to themselves as some variant of Brand + Location - ie - https://www.coles.com.au/store-locator/stores/sa/firle-401 and https://www.kmart.com.au/store-detail/Firle

It might be worth relaxing the locking of name on setting of brand:wikidata; or otherwise loosening the relationship between brand + name autocorrection.

matkoniecz commented 5 years ago

@CloCkWeRX It is a related but separate issue - can you consider moving it into a new issue (if not yet reported)?

hfs commented 1 year ago

A similar situation arises when the name is not unique and there are several potential matches in the NSI.

In Germany we have the situation that there are two supermarket chains with three brands all colloquially called “Netto”.

If you edit a supermarket tagged name=Netto, e.g. https://www.openstreetmap.org/edit?editor=id&way=31727346#map=19/52.65117/13.19552, it suggests to brand it as Netto (Salling).

image

Instead, it would be better if it would recognize that there are several potential matches in the NSI and offer all of them with logos. This would make it clear that the user has to make a choice and that iD can’t know which brand is the right one.

When adding a new node and searching for Netto iD lists the brands with logos (if enabled):

image

That makes it much more likely that a correct choice is made. I imagine that a similar choice could be displayed for the case of unambiguous brands, with the additional choice of “none of these”.