Skip to content
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

CRM-21407 - Fix ISO compliance for German counties #11255

Merged
merged 1 commit into from
Nov 15, 2017

Conversation

tschuettler
Copy link
Contributor

@tschuettler tschuettler commented Nov 8, 2017

Overview

Fix spelling and abbriviation for German counties.

Before

Not ISO3166-2 compliant

After

ISO3166-2 compliant

Comments

I used target version 4.7.29. Can be modified if required.


@totten
Copy link
Member

totten commented Nov 8, 2017

(CiviCRM Review Template WORD-1.0)

For r-technical, I'm a little uncertain.

  • Suppose somebody has a workflow where they periodically import data from another service (via GUI or API or somesuch)...
  • Maybe... some folks have coded the import to match the current abbreviations (eg with BR instead of BE). Then upgrading would break their routine?
  • Maybe... everyone in Germany knows that it's BE, and this hasn't really come up, or the system is silently failing in ways that people don't recognize.
  • Maybe... the abbreviation has actually changed historically. (Ex: In the US, California is conventionally "CA", but "Cal" or "Calif" are historically valid.) This really requires a bit more cultural knowledge.

Any opinions @tschuettler @systopia. Proceed as-is? Add a note to make this a bit more visible to upgraders?

@seamuslee001
Copy link
Contributor

@totten its probably worthwhile noting that i believe we have been aiming to be consistent with ISO3166-2 I agree that it might have caused some issues on import but I think its better to keep the standard. The only improvement could be a pre/post upgrade message or similar but also i would have thought that on the Import you would use the full name not the abbreviation. BE certainly is correct as per https://en.wikipedia.org/wiki/ISO_3166-2:DE also ping @mlutfy for thoughts

@mlutfy
Copy link
Member

mlutfy commented Nov 9, 2017

If we get a few reactions from people in Germany, I would be OK with merging this. I suspect it simply went unnoticed for many years.

I tried finding which convention used "BR", but couldn't find any. If people noticed the error but did not report it, it's hard to find sympathy about breaking their workflow.

@bjendres
Copy link
Contributor

bjendres commented Nov 9, 2017

If we get a few reactions from people in Germany, I would be OK with merging this. I suspect it simply went unnoticed for many years.

Thanks @mlutfy, I'd also agree with the merge.

And since @totten made a good point about people currently using BR, I'll also send an email out to the German mailing list just in case.

@tschuettler
Copy link
Contributor Author

To make matters worse BR was used in the draft ISO/DIS 3166-2, but it was for the county Brandenburg: http://www.statoids.com/ude.html

@systopia Thanks for writing the mail.

@mlutfy mlutfy merged commit 901c7d7 into civicrm:master Nov 15, 2017
sluc23 pushed a commit to ixiam/civicrm-core that referenced this pull request Jan 10, 2018
CRM-21407 - Fix ISO compliance for German counties
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants