But there are no source icons for the children unless you go into their page, 
are there? I do like the idea of adding the UNSOURCED master source so at least 
when I'm ready to work on those, I can pull them up.
Thanks!




>________________________________
> From: Leon Chapman <chap...@gmail.com>
>To: LegacyUserGroup@LegacyUsers.com
>Sent: Thursday, April 19, 2012 8:43 PM
>Subject: Re: [LegacyUG] What to do with the "I think" and "maybe" individuals?
>
>Peggy:
>
>The source icon is Grey if there are no souces for an individual in
>the family view.
>
>You could add a new Master source called UNSOURCED and attach that to
>each person you have unsourced and then you can see a list of people
>who have that source named UNSOURCED.
>
>___
>Leon Chapman
>chap...@gmail.com
>-----
>
>
>
>On Thu, Apr 19, 2012 at 5:31 PM, Marg Strong <tiny...@yahoo.com> wrote:
>>
>> When I read this (posted as a comment in another topic) I wondered again if
>> there was a way to put individuals into your tree and identify them as
>> unsourced. I have a number of branches (not as important as my main line,
>> but still of interest) with names, dates, children, spouses, etc that are
>> found on family trees on ancestry.com without sources. The information is so
>> specific it seems they have family knowledge so I hate to leave those
>> individuals out of my tree. But I would like some way to identify them as
>> unsourced. I suppose there is a "report" that wil show me a list of unsouced
>> individuals; I haven't come to the point yet of using reports since I'm
>> still working on cleaning up my database.
>>
>> I've sent messages to several of the owners of the trees, but rarely receive
>> an answer.
>>
>> I know there are colors to use in Legacy, but those are used for family
>> lines, is that not correct? I'm thinking of adding something in parenthesis
>> after the given name of these individuals - Maybe in the prefix option -
>> such as NS for "not sourced." Would that be a mistake? Is there a better way
>> to tell at a glance when a family is pulled up, without having to go into
>> each individuals window? I have enough cleanup to do on main family lines
>> before I start on the branches that are further out. But I hate to leave out
>> information that I hopefully will be able to check more throughougly later.
>>
>> Would appreciate your thoughts. Peggy
>>
>>
>> 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

Reply via email to