Re: Historical Events Database
Looks good! On the location issue, should that also be categorized like with the event type in order to make it easier to correlate later?
Data said:I could make an online app rather quickly, which all of you could access. Based on your input I've created a mockup for the input form, attached to this post.
I guess the main purpose is to have enough data/event points so that we can correlate later with modern records of tree rings, eclipses, position of stars, etc. to estimate the 'historical gap' that Laura mentioned. Because of this, the app could be a generic historical events tracker; generic enough so that the characteristic properties of all kinds of events can be entered.
It doesn't care about categories and actual event names, they can be added by the users. In case the lists get too long, there would be a search function to avoid duplication. New event names should be added only when an event is very different from the existing ones, so that 'thinning out' of the number of available data points is avoided. That is why the initial event list should be well thought out.
As many properties as possible can be entered. If a property is not known, it can be left empty or zero. I've added to the mockup as many characteristic properties that I could think of. Which properties to be used to present the data, and how the actual presentation of the data will be (maps, graphs, lists, filtered lists, etc.) we can decide later, after the data has been entered.
Looks good! On the location issue, should that also be categorized like with the event type in order to make it easier to correlate later?