Since we are all speaking, I keep folders (like Pictures>Pics in Legacy>
Waller) for 8 names, 4 for my grandparents and 4 for my husband's
grandparents, a few others for inlaws, cemetaries (filed by location
starting with State), vital records. Most docs I have as .jpgs (easy enough
to change format). The people: Last name, first & middle, date or dates,
type of pic, sometimes even s/o (or dau/o) if I think it helpful. Never have
used RINs. Prob because I feel it's a step away from the people involved.
Know what I mean? And, when I look for something, I usually start with a
name.

Jane in Phoenix

-----Original Message-----
From: LegacyUserGroup <[email protected]> On Behalf Of
David Cripps
Sent: Tuesday, January 23, 2024 7:16 PM
To: Legacy User Group <[email protected]>; Jenny M Benson
<[email protected]>
Subject: Re: [LegacyUG] Unique identifier

On 23/01/2024 11:11 pm, Jenny M Benson wrote:

> Why on earth not use the unique identifier provided by Legacy - the RIN. 

I'm with you Jenny and have done it this way for ages now, the only issue is
you must be aware never to overwrite or alter the current RINs & heaps of
backups too of course.

For Census Sourcing, I use 12345-1871Census.jpg then I use the same format
for Birth, Baptism & Death sourcing.
For marriage I use the MRIN & identify it as 12456-MRIN.

It works for me, but of course once decided on this course of action it's
(in my case) probably too hard to change it.

Each to their own I suppose.
David Cripps in Hobart



--
David Cripps <[email protected]>
Hobart, Tasmania
Gedmatch: EH6082465 & Gedcom ID: 3475815
FTDNA: N10906


-- 

LegacyUserGroup mailing list
[email protected]
To manage your subscription and unsubscribe
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/


-- 

LegacyUserGroup mailing list
[email protected]
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/

Reply via email to