In a food centric world good data quality system could be like a good restaurant that serves whats necessary to survive and in good portions. 

In this restaurant you can only get one of everything and when you ask for something you do not get something else.
When the waitress or waiter have got your order it will be served at the exact same time as you want it to be served and with the right preparation (no salt needed, since its perfect).

This restaurant would get a couple of stars in my data quality version of Guide Michelin

If you enjoyed this post, make sure you subscribe to my RSS feed!

A thought came up when I built a simple website for displaying points in a indoor fotball tournament a couple of weeks ago and it was actually a mistake when I was stressed getting data into the system that rendered an error for me that is the source to the question in the title

I wrote Timmele GoiF in one place in the system (id of a team in the tournament) and Timmele GoIF (capital i in GoIF) and of course the system did not work since i used a bit of scripting in the page.
As a human I know, of course, that this is the same team since I know the team. But should a system know this?

Of course, I should not have used the teams name as an ID in the system, it would have been easier/better to have used a numeric id or something that is better for the database engine to index and for, in my case, scripting to understand.

But if names is an identifier in a system, the question arise:
Is a capital version of TIMMELE GOIF the same as the lower case timmele goif?
In older system, for example the ERP Garp, it is a distinction but in more modern SQL server based systems (depending on setup of course) there is no distinction.

How should it be? What is the best, integrationwise?

A lot of questions and, Im sure, a lot of answers.

In my world it should be the same if I want to integrate between two system and if it is a standalone system it could be different since I dont have to talk to others but myself (myself being the system)

If you enjoyed this post, make sure you subscribe to my RSS feed!