Database

[Richard T. Eger]

Dear Luc,

You hit the nail squarely on the head.

But further is the question of the reliability of anyone's data, given that original records have typos or, if handwritten, subject to interpretation. More data means more corroboration, which is good, but old data may be based on what's available at the time, which may not be so good. So, then, who assumes the task of updating and correcting, especially a really massive database?

Regards,
Richard

[Werwolf]

Relational databases are not going away anywhere soon, the technology is simple and fast, I can assure you there will be here 30 years down the road if no more. I could program the scripts to move the database to new systems. SQL is the standard language for databases and you don't throw away backward compatibility easily. Even outdated software is still supported, there are hundreds of enterprises depending on it.

I didn't think originally on a centralized database, more like the same database structure as a frame to exchange data. Every one of you can have their own data and decide what you want to input. I think a key element could be a list of references to tell from where come the data. I will check how typos can be handled.

By the way my name is Gonzalo Nieva. I am beginning to feel a bit silly with my call sing, when I subscribed didn't know here you use your real names, maybe I will change that later.

[Bas Maathuis]

Originally Posted by Richard T. Eger

Dear Luc,

You hit the nail squarely on the head.

But further is the question of the reliability of anyone's data, given that original records have typos or, if handwritten, subject to interpretation. More data means more corroboration, which is good, but old data may be based on what's available at the time, which may not be so good. So, then, who assumes the task of updating and correcting, especially a really massive database?

Regards,
Richard

Richard, Luc and Conzalo,
For the Dutch Air War Study group's online database we ran into the same problems.
The database is built in MS access. The biggest problem is how to keep track of edits. Where do edits come from (origin, sources). What is reliable and what is not.
I’m keeping track by using digital dossiers for every crash recorded in the database. Every crash has it’s own written log for edits en additional info. There probably is a faster/better way, but this works for me.
I’m willing to share my experience although I’m not an expert on these matters.
For your information Conzalo, you can find our database at:
http://verliesregister.studiegroeplu...g.nl/index.php