Here is my take on the File ID field in sourcing. Let's assume that you are an organized Genealogist that keeps meticulous records. You have organized all of your original paper documents including sources by family names. Within a given set of family names you have several families, e.g., Jones, Bill family records Jones, Jerry family records Jones, Tom family records
You keep all your paper records in folders in a filing cabinet. You have a folder for each family above. Your "Jones, Bill" folder might include three documents as noted below: 1. Jones, Bill - Birth certificate - Document 1 (File ID: 1 - Jones, Bill - Birth Cert) 2. Jones, Bill - High School Graduation Picture 1 (File ID: 2 - Jones, Bill -HS Pic 1) 3. Jones, Bill - Census record, 1850 (File ID: 3 - Jones, Bill - Census - 1850) The File ID used in my filing cabinet folders in my paper filing system is a detailed system to help me manually locate my paper records within my filing cabinet. It is my own personal filing cabinet folder/document numbering system. Now, if I have such a filing cabinet with all my folders, I can point to my hard copy papers in my Legacy sourcing using the File ID # to correspond with my filing cabinet numbering system. I would guess most people may not be this organized with their hard copy materials, but in case you are, you can use the File ID # to correspond to your personal filing system. This field is meant to be for a user to point to their hard copy filing system if they have one. The File ID numbering system can be anything the user has created or wants to use. If you don't have such a detailed paper filing system, then you would probably never use the File ID field and would always leave it blank. The reporting feature provides you a way to create a hard copy index for your filing cabinet files or whatever. As another example, you may have all of your documents on shelves like in a library and use some library numbering system to help your keep things organized. You have numbers like "Bookcase 1, shelf 2, book 13". That could be a File ID # that you would use in Legacy to correspond to your bookcases. Anyway, I hope this helps explain the concept for the File ID field. It may be used however the user sees a need, but would normally be a pointer to personal records kept in ones possession. Chap ___ Leon Chapman chap...@gmail.com ----- On Fri, Dec 18, 2015 at 8:32 PM, Walter DeWaele <wdewael...@gmail.com> wrote: > Hi Steve, > Could you give us an example of one of your indexed documents? Thanks. > Walt > > Sent from my iPad > > > On Dec 18, 2015, at 10:12 AM, Steve Hayes <hayes...@telkomsa.net> wrote: > > > >> On 18 Dec 2015 at 10:16, BARTON LEWIS wrote: > >> > >> Thanks. But I'm not asking where you can add the File ID. That > >> information is readily available in the Help feature. What I am asking > is, > >> what is the purpose of the File ID? > > > > I suppose one can use it for a variety of purposes, but I use it for the > > number of a hard-copy document I file away. > > > > I give each such document a serial number as I file it. > > > > I think I mentioned in another program that I use the Research Data Filer > > program (RDF) to index the documents. It has a description of the > document, > > and, and an index of persons mentioned in the document. If I use that > > document as a source for information in every,y Legacy database, then I > would > > give the file Id, so I can go straight to that document to see what it > says. > > > > > > > > -- > > Keep well, > > Steve Hayes > > Blog: http://hayesgreene.wordpress.com > > Web: http://www.khanya.org.za/famhist1.htm > > E-mail: sha...@dunelm.org.uk > > > > > > > > > > > > > > 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 > > 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