History widget

Chris, I see what you mean - we are trying to put too much info into
some fields, so that it is difficult to get straightforward data out of them
Colin, could you have a look at this? I guess the answer is to make
more fields, and stick to numbers or text, but not mixtures of the
two in one field.

Troy, are you listening in? Do you have a simple answer about the
syntax of JSword Bible references?

David IB

At 13:31 27/10/2009, Tyndale STEP Project wrote:
>What I meant is that columns like the certainty column with values
>such as 45/0, etc. might be difficult to query later on, so it would
>be best to transform that internally into something that can be
>queries and indexed.
>
>We may want to add a column, where only a start date is populate to
>indicate that this is an event at a point in time. We'll probably
>want to transform the scripture reference into numerical form to
>store it into fast indexable and retrievable format...
>
>Also, for the references, we might want to store that in a different
>table. For eg. 1Kgs.2.13-4.34;2Chr.1 refers to the event "Solomon
>establishes his kingdom, granted wisdom". But if you're looking at 2
>Chr 1:1-5 then I think it might be hard to work out whether that
>event is part of the passage or not. (I'm assuming at some point
>we'd like to tie the timeline in with what the user is currently reading).
>
>Same problem, if the user is looking at 1Kgs.3, then clearly the
>event is valid, but yet, we can't do a simple comparaison between
>the reference and the user passage, since the only part in common is the 1Kgs.
>
>So we'll want to be able to query the database, and it should
>respond fast if we ask the question "Give me all events relevant to
>...".Otherwise, we'll have to retrieve all the events out (and
>possibly articles, and all our material) to do string comparaisons
>on them to work out whether or not they are relevant.
>
>One way of representing it, although not sure if it will satisfy all
>of our needs
>Scripture Block (book, chapterStart, verseStart, chapterStart, chapterEnd)
>Scripture Reference(many Scripture Blocks).
>
>This would be the primary key, indexed and all for all of our data.
>So we'd need to get this right as early as possible.
>
>Another way, would be assign each verse of the bible a number, and
>key everything on the verse_id start, verse_id end. Then with a
>passage reference we'd first look up the ranges of verse_ids that
>we're interested in, and then with those ranges query our data.
>
>Or a combination of those solutions, or some better solution.
>
>Does anyone know if JSword internally uses the question "Does this
>passage overlap with this other passage?"
>
>
>Hope this makes sense?
>
>Chris