I can’t see why a Source Writer source can’t be uploaded to Family Tree exactly as it appears in Legacy. Source Writer sources (as opposed to basic sources) appear to have a ‘template’ and a whole bunch of discrete fields for data elements that allow Legacy to produce the source in a very specific format. That formatted source can be transferred exactly as is to Family Tree (i.e. exactly as it appears on a printed report). I’m sure Family Tree will take it in as a just one long string of characters, but it should still be formatted correctly. Surely the existing API does that.
The other direction (Family Tree to Legacy) is much more problematic. Family Tree must produce a generic API to work with multiple client programs like Legacy, Roots Magic, and all the others interfacing with it, and all of those programs have different database structures for “Source Writer”, or more generically ‘Templated” sources. I can’t see how Family Tree, or even Legacy, could parse the outgoing/incoming source data to meet the needs of these various systems. In fact, even if they had a data structure that fit Legacy’s needs, how would Legacy know which template among several options to use? Paul From: Ch [mailto:howell...@gmail.com] Sent: July-31-13 4:15 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Fwd: Sources To be clear, will LegacyFT sources/citations entered into SourceWriter ever be up-loadable to FamilySearchFT? I know it won't look the same once its transferred. Is this the API we are waiting on from the church? I am not too concerned with going the other way (FamilySearchFT to LegacyFT) Charles On 7/31/2013 4:45 PM, Sherry/Support wrote: When the church gives us an API that will transfer sources other than the basic one referencing that the information came from the FamilySearch site. Sincerely, Sherry Technical Support Legacy Family Tree On Wed, Jul 31, 2013 at 2:40 PM, Ch <howell...@gmail.com> wrote: I would really like to know how the Legacy sources to FamilySearch Family Tree is going to work. Whoever figures that out has earned their money. The last thing I want to do is manually transfer of my sources/citations/reason/notes. Charles 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://www.LegacyFamilyTree.com/Help.asp 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://www.LegacyFamilyTree.com/Help.asp 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://www.LegacyFamilyTree.com/Help.asp 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
