Comments on: Consistency Checking http://www.beholdgenealogy.com/blog/?p=1140 the Development of my Genealogy Program named Behold http://www.beholdgenealogy.com/blog http://www.beholdgenealogy.com/blog/../beholdblog.gif Comments by Louis Kessler are Copyright 2000-2013 Louis Kessler, All Rights Reserved. Comments by others belong to the people who made them. By: Louis Kessler http://www.beholdgenealogy.com/blog/?p=1140#comment-548 Louis Kessler Thu, 08 Nov 2012 15:00:53 +0000 http://www.beholdgenealogy.com/blog/?p=1140#comment-548 Brett: Hopefully hard work and preparation mitigate the need for luck. :-) Louis Brett:

Hopefully hard work and preparation mitigate the need for luck. :-)

Louis

]]> By: Louis Kessler http://www.beholdgenealogy.com/blog/?p=1140#comment-547 Louis Kessler Thu, 08 Nov 2012 14:59:15 +0000 http://www.beholdgenealogy.com/blog/?p=1140#comment-547 Sue: Yes. That's the goal. I'll have an initial (and hopefully close to comprehensive) set of checks with some based on age criteria that will be user-settable. When I add editing to Behold, I'll be including a way to easily override a reported problem for a specific individual and mark it as "confirmed". There's no use in adding that yet, because currently there is no way to save that info between runs. Sue:

Yes. That’s the goal.

I’ll have an initial (and hopefully close to comprehensive) set of checks with some based on age criteria that will be user-settable. When I add editing to Behold, I’ll be including a way to easily override a reported problem for a specific individual and mark it as “confirmed”. There’s no use in adding that yet, because currently there is no way to save that info between runs.

]]> By: sue-adams http://www.beholdgenealogy.com/blog/?p=1140#comment-546 sue-adams Thu, 08 Nov 2012 09:41:26 +0000 http://www.beholdgenealogy.com/blog/?p=1140#comment-546 Ideally consistency checking should be happening at all stages. Checking at data entry or import helps cut down on new errors. Checking prior to report production reduces the need to proof read the report. The seemless, non-irritating incorporation of checking is the challenge. Presumably you have decided on criteria for the checks. What data have you used to arrive at the limits for flagging? There will always be some data that fails the checks, but is correct e.g. a tiny minority of children are born to women over 50. Ideally consistency checking should be happening at all stages. Checking at data entry or import helps cut down on new errors. Checking prior to report production reduces the need to proof read the report. The seemless, non-irritating incorporation of checking is the challenge.

Presumably you have decided on criteria for the checks. What data have you used to arrive at the limits for flagging? There will always be some data that fails the checks, but is correct e.g. a tiny minority of children are born to women over 50.

]]> By: Brett http://www.beholdgenealogy.com/blog/?p=1140#comment-545 Brett Thu, 08 Nov 2012 09:06:49 +0000 http://www.beholdgenealogy.com/blog/?p=1140#comment-545 Not sure to congratulate you for the 10 years Louis, or again reiterate my support for your product. I am very keen to see the next version and subsequent after that. Good luck for the future of Behold. And good luck for the cruise presentations. Brett - Forum member since 12 Jan 2009 Not sure to congratulate you for the 10 years Louis, or again reiterate my support for your product. I am very keen to see the next version and subsequent after that.
Good luck for the future of Behold. And good luck for the cruise presentations.
Brett - Forum member since 12 Jan 2009

]]>