John in regards to you said
"User could add custom event that reports the status. But that would need to be added by user every time they did an upload." that is not correct. As an old user I had a custom event for Adoption and still have a few stragglers left. They get exported just fine and tng imports them nicely, Just make sure to "allow" the custom event in TNG. Jay On Thu, Mar 26, 2015 at 3:35 PM, John B. Lisle <leg...@johnlisle.com> wrote: > Jay, > > The child status triggers placing the status in the child list in Family > view and adding it to some of the reports. This is useful for Adoption, but > it is more interesting for Stillborn or Twin status. Child Status or birth > notes are only alternative ways or reporting these status in Legacy. > > The primary handling of adoption is with the Child-Parent relationship > tool. and use of an Adoption event to put a date and place and verbiage and > sourcing on it. > > However, setting this status gets it displayed in the family view child > list and may have some value when creating descendant and pedigree reports. > > --> Remember, historically, Legacy only had adopted status. Child-Parent > relationship status was only added with Legacy 6, I believe, so many long > time users have not converted to it. > > As an earlier writer mentioned, TNG does not natively have a way to add > this status (easily - User could add custom event that reports the status. > But that would need to be added by user every time they did an upload. > > john. > > > At 05:22 PM 3/26/2015, Jay Wilpolt wrote: > > John, > > After further review, I am not so sure this is as critical of an issue > (for me) > > As noted in other messg on this thread, Legacy does export and TNG does > properly import the "Child Relationship" status. > > Thats good enough for me. > > In a quick search for persons where Child Status = Adopted and Child > Relationship for either Father or mother was "blank" I only had 10 records. > > By changing those, the Adopted will show on their TNG pages. > > I only had one exception and that was for a child who was adopted by her > biological Uncle, and for future "genetic/cause of death" searches > I want to keep her Father Relationship as Biological. (with a note in the > record) > > Could you change your records to solve this?? Maybe I dont understand > why you use that field instead of the more specific Child Relationship. > > Jay > > > > On Wed, Mar 25, 2015 at 9:07 PM, John B. Lisle <leg...@johnlisle.com> > wrote: > Jay, > > 1/ Darrin could "fix" it, but that is not the right fix. And he says it > would not be an easy fix. He claims that only me and 1 other person has > ever noticed. > > 2/ No, there is no easy fix to the Gedcom. > > 3/ What you (and other can do) is to submit a suggestion at LegacyFT web > site to update Legacy go Gedcom export of Child Status is useful. Please > reference that I am submitting a detailed suggestion. > > 4/ Tell Darrin that this is a problem for you. Please feel free to send a > message to the TNG users list so more Legacy users may become aware of the > issue. > > I am sure that 100s, maybe 1000s, of users are importing Legacy Gedcoms > into TNG and most have never noticed that this status (actually an > attribute) field is not getting imported. > > thanks for your message, > > john. > > At 07:28 PM 3/25/2015, Jay Wilpolt wrote: > > John, > > I was unaware of this as well. > > I hope Darrin will fix it or is there an easy was to change the gedcom > contents before importing into TNG? > > > I am always frustrated when creating a gedcom in Legacy for "Changed" > persons, and then importing that (appending to an existing database) into > TNG ALWAYS screws up the family group > > Legacy has a check to add Parents and Spouses and Children, BUT what about > SIBLINGS!! > > so in TNG the FAMC gets replaced with only those included in the gedcom. > > so frustrating..... > > Let me know what I can do to help, as I am sure there are many Legacy > Users importing into TNG. > > Thanks > > Jay > 1FamilyTree.com > > > > On Wed, Mar 25, 2015 at 1:49 PM, John B. Lisle <leg...@johnlisle.com> > wrote: Hi, > A user recently reported to me that Child Status attributes, such as > Stillborn, > Twin, Adopted, etc., were not being imported into his TNG web site from a > Legacy Gedcom file. > Analysis shows that Legacy is exporting the Child Status in Gedcom, and > can import those Legacy Gedcoms properly back into in Legacy. But the TNG > web publishing application that many Legacy users use does not import the > tag that Legacy uses to report Child Status. (Legacy currently exports it > as an attribute of the child in the family structure.) > --> IE, none of your Child Status attributes have EVER been imported into > TNG. Maybe this OK with you? Maybe you have never noticed? Further > analysis shows that Legacy's approach to Child Status seems to be unique > among the major genealogy products and, although the best (as far as I am > concerned) actually, may not be optimal. In reality, there is no > consistency in how various products implement Child Status attributes, if > they handle them at all. > Consequently, the TNG developer has less incentive to provide the fix for > this mis-match with Legacy. > As this has been a problem for 10+ years with, supposedly, only myself > and one other user expressing concern over this to Legacy, I would like > to know if other users have seen this and would like to see this > resolved. Getting something resolved - and quickly - will require having > many folks second that this is an issue for them. > --> Let me emphasize that this is not a Legacy bug. Legacy itself works > fine. This is a mis-match in the interface between two products. > Also, do you know of any other programs where the current Child Status > implementation is causing a problem from Legacy Gedcoms? > Thanks for listening, > john. nashua, new hampshire > > > > > > Legacy User Group guidelines: > > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: http://support.legacyfamilytree.com > Follow Legacy on Facebook ( <http://www.facebook.com/LegacyFamilyTree> > http://www.facebook.com/LegacyFamilyTree) and on our blog ( > <http://news.legacyfamilytree.com/> http://news.LegacyFamilyTree.com > <http://news.legacyfamilytree.com/>). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > <http://www.legacyfamilytree.com/Etiquette.asp> > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: http://support.legacyfamilytree.com > Follow Legacy on Facebook ( <http://www.facebook.com/LegacyFamilyTree> > http://www.facebook.com/LegacyFamilyTree) and on our blog ( > <http://news.legacyfamilytree.com/> http://news.LegacyFamilyTree.com > <http://news.legacyfamilytree.com/>). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > <http://www.legacyfamilytree.com/LegacyLists.asp> > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: http://support.legacyfamilytree.com > Follow Legacy on Facebook ( http://www.facebook.com/LegacyFamilyTree) and > on our blog ( http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > <http://www.legacyfamilytree.com/Etiquette.asp> > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: http://support.legacyfamilytree.com > Follow Legacy on Facebook ( http://www.facebook.com/LegacyFamilyTree) and > on our blog ( http://news.LegacyFamilyTree.com > <http://news.legacyfamilytree.com/>). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > <http://www.legacyfamilytree.com/LegacyLists.asp> > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: http://support.legacyfamilytree.com > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and > on our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
