tag:blogger.com,1999:blog-5512311610334754148.post8901073976705822033..comments2023-04-20T12:46:11.858-06:00Comments on The Ancestry Insider: The Evidence Architecture of the New FamilySearch TreeThe Ancestry Insiderhttp://www.blogger.com/profile/02490682912125335188noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5512311610334754148.post-77272412023086307142010-06-22T12:41:04.967-06:002010-06-22T12:41:04.967-06:00Dear brucefuimus,
You make a good point regarding...Dear brucefuimus,<br /><br />You make a good point regarding occupation. The philosophy the vendors need to take is that users never have to type anything twice. Consider this scenario:<br /><br />The user wishes to enter the occupation and only the occupation from a census. He doesn't have an evidence summary for the person/record.<br /><br />* He clicks on Add Occupation.<br /><br />* Whether he knows it or not, the popup for entering the occupation is an evidence summary. He enters the occupation.<br /><br />* He has an opportunity to enter a source if desired. If not, it requires no additional clicks. Entry of the source requires minimal keystrokes by utilizing previously entered information.<br /><br />* He has an opportunity to enter additional assertions from the source. If not, it requires no additional clicks.<br /><br />* He clicks done.<br /><br />-- The InsiderThe Ancestry Insiderhttps://www.blogger.com/profile/02490682912125335188noreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-80471166007817393302010-06-22T05:50:26.381-06:002010-06-22T05:50:26.381-06:00Good, thought provoking stuff. The examples are re...Good, thought provoking stuff. The examples are really beginning to make sense to me now.<br /><br />I was interested in your comments about "a different user experience to immature users and mature users". Since this stuff is not self-evident, I believe any software must be able to do this in some fashion - wizards or whatever. The beginner will undoubtedly start by entering their own family details and their attitude will be "I KNOW who my own father is, I just want to enter it - NOW please!" But these simple statements need to be entered and stored in such a way that later on, it must be possible for them to peel back the layers to what they've previously done and see the assertions, evidence, whatever, that have previously been masked. (Apologies for going on again about the user experience)<br /><br />I also wonder whether mature genealogists will necessarily want to write out the full process for every item. I can see the benefit for something like a birth date or establishing a relationship, because are multiple bits of evidence to deal with. But if I'm processing a census, do I really want to go through a full investigation just to record someone's occupation at that time? Yes, we may get contradictory evidence later so we need to be able to see the detail, but I need to have a smooth workflow that starts with a single document first.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-42086953036959321952010-06-21T10:27:09.525-06:002010-06-21T10:27:09.525-06:00Good article. It's too bad that FamilySearch d...Good article. It's too bad that FamilySearch decided to suck in all of the IGI instead of cherry-picking it.<br /><br />You seem unfamiliar with the Gentech Genealogical Data Model (GDM). (http://www.ngsgenealogy.org/cs/GenTech_Projects There's a summary of the main concepts here: http://xml.coverpages.org/GenTechLexiconDataModel1998.html) <br /><br />A "persona" in the GDM is the representation of a person in a source. The GDM incorporates layers of "assertions" to extract evidence from sources and to combine that evidence into a description of an actual "person".<br /><br />The point of all of this is that NFS has picked out one small piece of the GDM, that personas from individual sources should be linked to the conclusional aggregate "person" -- and that those links might be erroneous and should therefore be movable. That's analogous to TMG's tags, which allow one to easily change a person link in a tag to assign it to a different person in the database.<br /><br />As you rightly point out in the article, it's not evidence management. But it's a lot further away from evidence management than you seem to think.John Rallshttps://www.blogger.com/profile/12286491286619906933noreply@blogger.com