In my system, each piece of documentation is labeled with a unique name.
That name becomes the FILE ID when the document is added as a source.
My sourcing system more closely resembles the general example you gave.
For example -
New York, Niagara County, North Tonawanda - 1900 Federal Census wo
@legacyfamilytree.com
Subject: RE: [LegacyUG] Question about File Id and sourcing.
In my system, each piece of documentation is labeled with a unique name.
That name becomes the FILE ID when the document is added as a source.
My sourcing system more closely resembles the general example you gave.
For example -
New
I teach the use of categorizing before assigning File IDs.
Twelve categories work for me. Less I feel is too disorganized. More
becomes too unwieldy. This has worked for 25 years. I've been stumped
a few times--should it go here or there. It happens. It becomes a
judgment call. And then the
s and
cross referencing to Legacy.
Thanks again folks
Liz
From: "Olds-Wills-Anderson-Simonson Hodges-Harris-Liikala-Jukkara"
<[EMAIL PROTECTED]>
Reply-To: LegacyUserGroup@legacyfamilytree.com
To:
Subject: RE: [LegacyUG] Question about File Id and sourcing.
Date: Wed, 3 Jan 2007 21
Is the document picture added to the event or to the event source?
On 1/3/07, M. Brenzel <[EMAIL PROTECTED]> wrote:
In my system, each piece of documentation is labeled with a unique name.
That name becomes the FILE ID when the document is added as a source.
My sourcing system more closely res
In my system, the document picture is added to the source detail.
Randolph Clark <[EMAIL PROTECTED]> wrote:
> Is the document picture added to the event or to the event source?
>
> On 1/3/07, M. Brenzel <[EMAIL PROTECTED]> wrote:
> >
> > In my system, each piece of documentation is labeled
6 matches
Mail list logo
