<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Ordering Events by Date</title>
	<atom:link href="http://www.beholdgenealogy.com/blog/?feed=rss2&#038;p=883" rel="self" type="application/rss+xml" />
	<link>http://www.beholdgenealogy.com/blog/?p=883</link>
	<description>the Development of my Genealogy Program named Behold</description>
	
		<image>
	<link>http://www.beholdgenealogy.com/blog</link>
	<url>http://www.beholdgenealogy.com/blog/../beholdblog.gif</url>
	</image>
	<copyright>Comments by Louis Kessler are Copyright 2000-2013 Louis Kessler, All Rights Reserved.  Comments by others belong to the people who made them.</copyright>
		<item>
		<title>By: Louis Kessler</title>
		<link>http://www.beholdgenealogy.com/blog/?p=883#comment-529</link>

				<dc:creator>Louis Kessler</dc:creator>

		<pubDate>Wed, 08 Aug 2012 17:15:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.beholdgenealogy.com/blog/?p=883#comment-529</guid>
		<description>Tony:

Behold does some of that already. If there are no dates, then births will come first, then living events, then the death, and then a few post-death events (burial, cremation). 

But in the long run, I think all dates (for at least births and marriages) should be estimated as best as possible and indicated as estimated. I hope to allow an option in the future for Behold to do the estimation for you. This would be very valuable, because it will point out inconsistencies and possible problems in your research. 

Louis</description>
		<content:encoded><![CDATA[<p>Tony:</p>
<p>Behold does some of that already. If there are no dates, then births will come first, then living events, then the death, and then a few post-death events (burial, cremation). </p>
<p>But in the long run, I think all dates (for at least births and marriages) should be estimated as best as possible and indicated as estimated. I hope to allow an option in the future for Behold to do the estimation for you. This would be very valuable, because it will point out inconsistencies and possible problems in your research. </p>
<p>Louis</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Proctor</title>
		<link>http://www.beholdgenealogy.com/blog/?p=883#comment-528</link>

				<dc:creator>Tony Proctor</dc:creator>

		<pubDate>Wed, 08 Aug 2012 16:51:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.beholdgenealogy.com/blog/?p=883#comment-528</guid>
		<description>I know this thread is a little old now but ordering Events by date alone is not the only option. STEMMA supports optional constraints between Events that force a given order, even when the dates themselves are so vague or suspect that they do not imply that same ordering, e.g. forcing a baptism to be ordered after a birth.

Tony</description>
		<content:encoded><![CDATA[<p>I know this thread is a little old now but ordering Events by date alone is not the only option. STEMMA supports optional constraints between Events that force a given order, even when the dates themselves are so vague or suspect that they do not imply that same ordering, e.g. forcing a baptism to be ordered after a birth.</p>
<p>Tony</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louis Kessler</title>
		<link>http://www.beholdgenealogy.com/blog/?p=883#comment-406</link>

				<dc:creator>Louis Kessler</dc:creator>

		<pubDate>Tue, 06 Dec 2011 17:23:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.beholdgenealogy.com/blog/?p=883#comment-406</guid>
		<description>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 separately. I think their reasoning is that each of the dates and places can then be indexed and found, whereas that would not be possible if they are embedded in custom notes.

Both methods work and is really a user preference. The GEDCOM standard tells programmers what to write to the GEDCOM file. That need not be the same as what the programs allow their users to enter. Behold will easily allow either preference, and then just make sure it outputs the data to GEDCOM (or BetterGEDCOM) in a compliant way. 

Louis</description>
		<content:encoded><![CDATA[<p>GeneJ:</p>
<p>I don&#8217;t mind (and maybe even like) giving a single event, e.g. Birth with the &#8220;preferred&#8221; place and date attached to it, then including all the evidence and alternative dates within the notes or subtags of the event.</p>
<p>But the GEDCOM standard strongly recommends including conflicting events separately. I think their reasoning is that each of the dates and places can then be indexed and found, whereas that would not be possible if they are embedded in custom notes.</p>
<p>Both methods work and is really a user preference. The GEDCOM standard tells programmers what to write to the GEDCOM file. That need not be the same as what the programs allow their users to enter. Behold will easily allow either preference, and then just make sure it outputs the data to GEDCOM (or BetterGEDCOM) in a compliant way. </p>
<p>Louis</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: genej</title>
		<link>http://www.beholdgenealogy.com/blog/?p=883#comment-405</link>

				<dc:creator>genej</dc:creator>

		<pubDate>Tue, 06 Dec 2011 16:55:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.beholdgenealogy.com/blog/?p=883#comment-405</guid>
		<description>Hi Louis,

At least in part, I see this as the classic "combined" (record data) vs "conclusion" (person) issue. 

One conducts research and gathers various records that relate to their person of interest. These records contain incomplete and sometimes inaccurate information, and so frequently, conflicting information related to the same event. 

Selecting a "preferred" record from a host of records when each is only partly correct doesn't resolve the conflictes. Not only that, but in traditional genealogical reporting then results in those "lesser" records will frequently go  unreported ... so the evidence gods gave us the proof argument. 

Short of solving the proof puzzle (which I think BetterGEDCOM hopes to do), my desire to preserve all the evidence (direct, indirect, negative, conflicting) and still generate a genealogy, Rather than create the alt event tags/pfacts, I create a single pfact and report the various evidence in a series of citations that point to the single pfact.</description>
		<content:encoded><![CDATA[<p>Hi Louis,</p>
<p>At least in part, I see this as the classic &#8220;combined&#8221; (record data) vs &#8220;conclusion&#8221; (person) issue. </p>
<p>One conducts research and gathers various records that relate to their person of interest. These records contain incomplete and sometimes inaccurate information, and so frequently, conflicting information related to the same event. </p>
<p>Selecting a &#8220;preferred&#8221; record from a host of records when each is only partly correct doesn&#8217;t resolve the conflictes. Not only that, but in traditional genealogical reporting then results in those &#8220;lesser&#8221; records will frequently go  unreported &#8230; so the evidence gods gave us the proof argument. </p>
<p>Short of solving the proof puzzle (which I think BetterGEDCOM hopes to do), my desire to preserve all the evidence (direct, indirect, negative, conflicting) and still generate a genealogy, Rather than create the alt event tags/pfacts, I create a single pfact and report the various evidence in a series of citations that point to the single pfact.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louis Kessler</title>
		<link>http://www.beholdgenealogy.com/blog/?p=883#comment-399</link>

				<dc:creator>Louis Kessler</dc:creator>

		<pubDate>Mon, 05 Dec 2011 15:50:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.beholdgenealogy.com/blog/?p=883#comment-399</guid>
		<description>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 example, which is talking about the order that you find and enter your data into the program, and the order in which the program outputs the data. GEDCOM implies that the program should provide assistance to allow the user to order the events, and thus order them so that the most sure event is listed first when exporting to the GEDCOM. That need not be the order in which they were found or entered.

Louis</description>
		<content:encoded><![CDATA[<p>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 &#8220;best&#8221; birth date when a single date is required.</p>
<p>However, there is a difference between your example, which is talking about the order that you find and enter your data into the program, and the order in which the program outputs the data. GEDCOM implies that the program should provide assistance to allow the user to order the events, and thus order them so that the most sure event is listed first when exporting to the GEDCOM. That need not be the order in which they were found or entered.</p>
<p>Louis</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: agh3rd</title>
		<link>http://www.beholdgenealogy.com/blog/?p=883#comment-397</link>

				<dc:creator>agh3rd</dc:creator>

		<pubDate>Mon, 05 Dec 2011 08:25:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.beholdgenealogy.com/blog/?p=883#comment-397</guid>
		<description>Louis,

You said ". But that is wrong for multiple specifications of a single event, e.g. birth, where GEDCOM says the order of the listing of the event is significant."

The ordering of the listing of the event can only be significant in comparison to another like event and both events were entered at the same time. Take this scenario...

1). I find a 1900 census where it shows John Doe's age as 5 (Birth would be 1895)
2). Six months later I find a transcription of a bible page that says john was born in 1899
3). A year after that I finally find the original bible page and it actually says born 1894.

Just because I happened to find the census first and entered it first (due to lack of any other information) doesn't, imho, give it more significance than the other two events.

My firm belief is that *all* genealogy programs should totally disregard the order of event entry into the GEDCOM and deal only with the actual dates of the events and not the date or order they were keyed into the GEDCOM. Anything else is, as Dr. Spock would say, illogical.</description>
		<content:encoded><![CDATA[<p>Louis,</p>
<p>You said &#8220;. But that is wrong for multiple specifications of a single event, e.g. birth, where GEDCOM says the order of the listing of the event is significant.&#8221;</p>
<p>The ordering of the listing of the event can only be significant in comparison to another like event and both events were entered at the same time. Take this scenario&#8230;</p>
<p>1). I find a 1900 census where it shows John Doe&#8217;s age as 5 (Birth would be 1895)<br />
2). Six months later I find a transcription of a bible page that says john was born in 1899<br />
3). A year after that I finally find the original bible page and it actually says born 1894.</p>
<p>Just because I happened to find the census first and entered it first (due to lack of any other information) doesn&#8217;t, imho, give it more significance than the other two events.</p>
<p>My firm belief is that *all* genealogy programs should totally disregard the order of event entry into the GEDCOM and deal only with the actual dates of the events and not the date or order they were keyed into the GEDCOM. Anything else is, as Dr. Spock would say, illogical.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louis Kessler</title>
		<link>http://www.beholdgenealogy.com/blog/?p=883#comment-396</link>

				<dc:creator>Louis Kessler</dc:creator>

		<pubDate>Tue, 29 Nov 2011 14:24:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.beholdgenealogy.com/blog/?p=883#comment-396</guid>
		<description>Thanks, Robert. That makes sense and it's quite doable that way. 

Now I'm thinking that maybe I'll not bother at all with grouping the events in the Source Details section and just go by date there as well. It is expensive (time and memory) for Behold to maintain the sorting both ways, and it seems to me that the events would be easy to pick off because they're always first on the line.</description>
		<content:encoded><![CDATA[<p>Thanks, Robert. That makes sense and it&#8217;s quite doable that way. </p>
<p>Now I&#8217;m thinking that maybe I&#8217;ll not bother at all with grouping the events in the Source Details section and just go by date there as well. It is expensive (time and memory) for Behold to maintain the sorting both ways, and it seems to me that the events would be easy to pick off because they&#8217;re always first on the line.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Burkhead</title>
		<link>http://www.beholdgenealogy.com/blog/?p=883#comment-395</link>

				<dc:creator>Robert Burkhead</dc:creator>

		<pubDate>Tue, 29 Nov 2011 07:28:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.beholdgenealogy.com/blog/?p=883#comment-395</guid>
		<description>One more thing about date ordering in FH 4.1.3... It respects the dates, if the are provided. So if someone was born in 1900, but had a census event in 1898, died in 1910, but a buried event in 1908, and immigrated in 1912, then the order would be census, birth, burial, death, immigration.</description>
		<content:encoded><![CDATA[<p>One more thing about date ordering in FH 4.1.3&#8230; It respects the dates, if the are provided. So if someone was born in 1900, but had a census event in 1898, died in 1910, but a buried event in 1908, and immigrated in 1912, then the order would be census, birth, burial, death, immigration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Burkhead</title>
		<link>http://www.beholdgenealogy.com/blog/?p=883#comment-394</link>

				<dc:creator>Robert Burkhead</dc:creator>

		<pubDate>Tue, 29 Nov 2011 07:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.beholdgenealogy.com/blog/?p=883#comment-394</guid>
		<description>Over on twitter I suggested that you might group those tags that could only happen once, and then date-order the remaining ones. I also confirmed that Family Historian 4.1.3, when reordering by date, makes birth the first event, then all dated events, then undated events, then death, and then events that happen after death (burial, cremation, etc.).

I took a quick look through the list of GEDCOM tags (nothing in-depth, just a quick pass over them), and the only events that might truly happen only once are birth and death (assuming folks don't document near-death experiences with the DEAT tag). :-)  Cremation might also happen only once--but then again....maybe not? Burial certainly happens more than once, especially when a cemetery is moved. Other things that don't commonly happen more than once (e.g., naturalization, bar mitzvah, baptism), could happen more than once. John Doe could have two christenings for some esoteric reason. He could immigrate to and get naturalized in more than one country over the course of his life.

In the end, birth and death might be the only two you could treat as singular events. Of course, I might have missed one or two others in my quick once-over of the list.</description>
		<content:encoded><![CDATA[<p>Over on twitter I suggested that you might group those tags that could only happen once, and then date-order the remaining ones. I also confirmed that Family Historian 4.1.3, when reordering by date, makes birth the first event, then all dated events, then undated events, then death, and then events that happen after death (burial, cremation, etc.).</p>
<p>I took a quick look through the list of GEDCOM tags (nothing in-depth, just a quick pass over them), and the only events that might truly happen only once are birth and death (assuming folks don&#8217;t document near-death experiences with the DEAT tag). <img src='http://www.beholdgenealogy.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  Cremation might also happen only once&#8211;but then again&#8230;.maybe not? Burial certainly happens more than once, especially when a cemetery is moved. Other things that don&#8217;t commonly happen more than once (e.g., naturalization, bar mitzvah, baptism), could happen more than once. John Doe could have two christenings for some esoteric reason. He could immigrate to and get naturalized in more than one country over the course of his life.</p>
<p>In the end, birth and death might be the only two you could treat as singular events. Of course, I might have missed one or two others in my quick once-over of the list.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.564 seconds -->
