Louis Kessler’s Behold Blog The Behold User Forum
Louis Kessler (lkessler) Entries, Comments and Posts
742.
Out on a Bad Date - Blog comment by lkessler - 15 Dec 2011
Brett:
I don't think the reason for fail will be lack of developer involvement. Tom Wetmore who developed Lifelines, was involved in GenTech and is now developing DeadEnds has been a major contributor. Michael Martineau of Family Pursuit has also been a contributor.
Then we've had involvement from ...
743.
Out on a Bad Date - Blog entry by lkessler - 14 Dec 2011
It seems that I’ve created a series of posts about dating. First there was Sort of a Date where I discussed the problems in sorting GEDCOM dates. Then there was How About a Date? where I reviewed the GEDCOM syntax for dates and how many programs break them. While writing my FixDate function to correct those ...
744.
The RootsTech Developer Challenge - Blog entry by lkessler - 8 Dec 2011
Behold has been submitted as an entry to the RootsTech Developer Challenge.
When I read the challenge: "Create an application or service that introduces a compelling new concept or innovation for family history." - well, there was no better description of Behold that I could have made up myself.
Along ...
745.
How About a Date? - Blog entry by lkessler - 6 Dec 2011
Last post, I discussed what would be necessary in Behold to properly sort dates. I also wrote a bit about input of dates and output of dates.
I started implementing date sorting and I was using the raw DATE value as input into Behold. I had to interpret it and fix it prior to setting up the sort ordering ...
746.
Ordering Events by Date - Blog comment by lkessler - 6 Dec 2011
GeneJ:
I don't mind (and maybe even like) giving a single event, e.g. Birth with the "preferred" place and date attached to it, then including all the evidence and alternative dates within the notes or subtags of the event.
But the GEDCOM standard strongly recommends including conflicting events ...
747.
Sort of a Date - Blog comment by lkessler - 5 Dec 2011
GeneJ:
I personally think it's better to have an EST or ABT date which shows your assumption about the sort order, rather than having a hidden date that allows you to make an assumption without validating or giving reason for it.
If you have the date specified, even if it's a wild estimate, then you ...
748.
Sort of a Date - Blog comment by lkessler - 5 Dec 2011
Thanks, Dave. That's a great idea. And you're right. I should check for the long names as well.
749.
Ordering Events by Date - Blog comment by lkessler - 5 Dec 2011
Illogical or not, it is what GEDCOM says. But probably the best way to do is by strict date order, with a QUAY or something that indicates your surety. Then the date with the highest surety could be used as the "best" birth date when a single date is required.
However, there is a difference between your ...
750.
Sort of a Date - Blog entry by lkessler - 4 Dec 2011
Behold up to now has really not done much with the DATEs that have come in from the GEDCOM. It does look at the date value to pull out the year so it can display birth and death years in the Index of Names. And it was attempting to sort the dates in the event references in the Details sections, but in a very ...
Prev 731-740
Out on a Bad Date - Blog comment by lkessler - 15 Dec 2011