Search for content in message boards

FTM2012 Well-formed GEDCOMS

Replies: 39

Re: Re: FTM2012 Well-formed GEDCOMS

Posted: 12 Aug 2012 3:12PM GMT
Classification: Query
Edited: 12 Aug 2012 3:15PM GMT
I copied the following from kj_norway 11 Aug 2012 10:05 post


“For example in very recent threads in this board several people have given their individual way of recording specific pieces of data. One example is street address. Do you put it in the address tag, the place tag or the "description" field? Do you put it in several places so the information is correctly documented? A best practices document for FTM should be produced to tell everyone where the best place for this data is AND why.”

I agree with the statement, [A best practices document for FTM should be produced to tell everyone where the best place for this data is AND why] and would like to use the “concept”/idea discussed here to further explain some of the concepts I have been discussing in a few of the posts I have made on this thread

Basically the thrust of my discussion has been:

1- I agree that a best practices document should be developed
2- The best practices document should be the responsibility of Ancestry.com with interaction from the user community
3- Best practices developed by users are sometimes workarounds to overcome the deficiencies of the system and takes the responsibility away from Ancestry.com and in a sense give the responsibility for the best way to do things [example FTM 2012] to the users themselves

I would like to go a little further on item 3

Not only do I think they take away the responsibility from Ancestry.com I think that in some cases when they are used to show other users how to do things they can lead to incorrect results.

I am just going to use one example to make this case and it is the example indicated in my response to AGHatchett in my 10 August 2012 10:58 posted on this thread, partially extracted as follows:

“--- one SMALL example. The software used to generate the Ahentafel(?sp) report is incorrect/wrong and does not agree with long established standards for handling a case where a female has a child out of wedlock and then subsequently gets married to a person[who is not the father of the child born out of wedlock] and then has a child . The output in this case is wrong and should not be used”

What I did not indicate in my response to AGHatchett was the issue of handling “out of wedlock” was/ is an issue that has been discussed many times on this forum. And in some cases many different “best practices” were shared with other users on how to handle these cases. But in some cases these “best practices” were incorrect and if they were used they just “hid the problem.” So if a user accepted that [incorrect] best practice/way of handling the situation and used it the system was still incorrect and would still generate incorrect reports [and very importantly the incorrect best practice takes the onus/responsibility/priority away from Ancestry.com for solving the issue]

And the only way to solve this example problem is for FTM to take the responsibility for fixing the problem and then issue “their best practice” on how to really to solve the problem[which by the way will require software changes]

kj, I apologize for including this here and possibly mudding the water on the discussion of GEDCOMS, but your statement did provide the opportunity, which I just couldn’t pass up, to discuss this important subject

SubjectAuthorDate Posted
KATHYMARIEANN 12 Aug 2012 9:12PM GMT 
Linda Matthew... 13 Aug 2012 7:59AM GMT 
silverfox3280 13 Aug 2012 2:24PM GMT 
KATHYMARIEANN 13 Aug 2012 3:07PM GMT 
padmin1 29 Dec 2011 3:24PM GMT 
serenity20061 1 Dec 2012 10:00PM GMT 
serenity20061 1 Dec 2012 9:52PM GMT 
kj_norway 2 Dec 2012 2:19PM GMT 
serenity20061 3 Dec 2012 11:27PM GMT 
kj_norway 4 Dec 2012 2:18AM GMT 
per page

Find a board about a specific topic

  • Visit our other sites:

© 1997-2014 Ancestry.com | Corporate Information | Privacy | Terms and Conditions