-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
10m Populated Place: Puducherry, India #454
Comments
it is so complicated ; wikipedia voting: |
Hi @ImreSamu, long time no see! Thanks for the deep dive into Wiki Talk. I'm in favor of updating the default name to Puducherry with name_alt of Pondicherry since it's a big town with a long time conventional name in the earlier form and the official name has been in circulation for 14 years (!!!). For all the localizations the script follows https://www.wikidata.org/wiki/Q639421, which would result in the older name being used for name_en... and hilariously the alternative name is noted as the new name (but wouldn't be picked up by the script). @mizmay Note that while we audit |
We can put anything in NAME, NAMEALT and NAMEPAR as these are not currently populated. It's likely that @elliotap is flagging the
|
@mizmay yes - flagging for name_en. I've been checking issues against a copy of the 10m shapefile downloaded 5/21/2020 where I am also seeing NAME populated with "Pondicherry" |
@nvkelso is it appropriate to use NAMEDIFF or some other existing field to denote where NAME is not expected/required to match name_en? |
In the past namediff has been used to indicate (and combined with note field for explanation) when a change has been made version to version. It hadn't been maintained in several major versions. In most cases it may be better to simply edit the wikidata value upstream? It's only loosely associated with Wikipedia and it's controversies? |
In this case I understand the request to be that we NOT reflect the Wikidata “en” value in NAME. Looking for a programmatic way to do that.
S.
… On Dec 28, 2020, at 9:44 PM, Nathaniel V. KELSO ***@***.***> wrote:
In the past namediff has been used to indicate (and combined with note field for explanation) when a change has been made version to version. It hadn't been maintained in several major versions.
In most cases it may be better to simply edit the wikidata value upstream? It's only loosely associated with Wikipedia and it's controversies?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
There is a limit to number of columns in a DBF (it is an old but reliable format) and we're running up against that. I could see a new column with a JSON object to store such a mask for the ~ 2 dozen localizations? The crux is how often we update name vis-a-vis name_en? I think not very often and human reviewed? What about noting deliberate deltas in notes column and including that column in the wikidata QA generated tables? |
Suggested resolution: We'll use Puducherry in NAME and NAMEASCII but continue to rely on consensus from Wikidata editors for the localizations. |
Agree with these changes for ne_id =
|
Here we go! BEFORE:
|
AFTER:
|
Pondicherry, ID: 1159150163, was renamed to Puducherry in 2006. English-language wikipedia and wikidata (Q639421) still use well-known former name for page title.
https://en.wikipedia.org/wiki/Pondicherry
https://www.india.com/news/india/cabinet-approves-constitutional-amendment-to-change-name-of-the-union-territory-from-pondicherry-to-puducherry-1801316/
https://www.openstreetmap.org/node/245600130
The text was updated successfully, but these errors were encountered: