Database
 

I am a software engineer and as contribution to this community I can design a database. The question is if you are interested on this project since I am not expert on this topic and I will need a lot of feedback about your requirements.

Anyone interested?

Re: Database
 

Hello Werwolf,

Do you mean a database of the posts in this forum? That is a very good idea, since the search function is not comprehensive. I am not a software engineer, but would be happy to help financially.

Regards,

Paul

Re: Database
 

Well I didn't mind to host the database here but it could be possible. Internet development is not my area.

What I can offer is a database designed to the needs of this community, including ways to share and co-relate information.

I don't ask for money I just want to contribute a little. If the community thinks this project is worth their time, I will ask for a lot of patience and talking to understand what you need. I can design automatic ways to access the most common queries or ways to integrate the information for difficult questions, even ways to validate the information before it is introduced.

Re: Database
 

Well, looks like there is no any takers. Maybe do You think it would be too complicated?

As last resort I will explain what it is need, with luck it will spark your interest.

Attachment 12760

This diagram shows a quick (and surely erroneous) model of some of the entities that will conform the database's tables. The lines shows the relationships between different tables, take care about the n-s that shows the cardinality of the relation. For the relation Squadron-Aircraft it reads: A squadron has many aircrafts, an aircraft can belong to many squadrons (An aircraft can be transferred.)

Sure you could see some problems, like example the "register" attribute (wrong name?) like White-16 for a Luftwaffe plane. Does it conserves the old register when changing squadrons?

The Aircraft-Mission has a table that defines the relation, in this case crew. This models the fact that from mission to mission the crew of an aircraft can vary.

There is a lot of details like those that I ignore, I can't do it myself. With knowledgeable people we can construct a good model, the closest to reality. I will learn and maybe You will learn about an odd case or anecdote.

Any voluntaries?

Re: Database
 

Hi Werwolf,

Many thanks for your kind request to design a database.


Already for more than approx 25 years I'm using pc's to store the data of my aviation related researchprojects. During those 25 years I have been using different software to store that data. First I started it was with Microsoft Works when I was still using dos (and not windows). Later I switched to DBase and Foxpro (also both dos), to be followed by excel and access (various versions with Windows). At this moment I'm using excel (as hmtl file) with hyperlinks to additional data stored as html (designed in Word) and pdf-files for copies of original documents. This system however requires a lot of data-input and is therefore not very efficient.


What I think is that one of the most important things with the design of a database is that the data must remain available when a switch to other software is made, as the data will remain in use over a very long period. At this moment I'm still using some files which I started 25 years ago and therefore it is necessary that the software used has a certain standard so that - if required - it can remain in use after x years, using other software.


Perhaps it is easier if you contact me via pm so that we can go more into details, so that your kind proposal to design a database doesn't disappear unused ....


Looking forward to receive your pm.


best regards


Luc

Re: Database
 

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

Re: Database
 

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.

Re: Database
 

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