Note: The Rootsweb Mailing Lists will be shut down on April 6, 2023. (More info)
RootsWeb.com Mailing Lists
Total: 1/1
    1. [FO] Potential problem in switching from FO to Rootsmate
    2. Paul Studly
    3. Message text written by INTERNET:[email protected] >Since I had no intention of ever leaving FO for any other genealogy program I named my files using FO's record number of the (an) individual in the picture. This system has worked great for me (and for at least one other person who came up with it). However I understand that the only way to transport our databases to Rootsmate is by Gedcom effectively rendering my filenames meaningless for the most part since a lot of record numbers will change. If I had never deleted an individual or performed a merge of two individuals the record numbers would possibly make it through intact but as you might imagine that is not the case.< >Can anyone think of a workaround for this problem short of renaming a thousand+ graphics files or keeping the existing, soon-to-be meaningless, filenames? Will there possibly be any other way to transport our databases to Rootsmate other than a Gedcom?< As others have noted, merely packing the database which needs to be done from time to time would cause the same record number change problem. From time to time FO operation gets a little flacky in my experience, and "packing" essentially a reindexing fixes the problem. Would you put data at risk by flacky operation merely to preserve a dynamic photo numbering scheme? However, "meaninglessness" in filenames is in relative terms not very important. Transitorily I would use the REF NUMBER preformatted fact to record the existing photo file name as a fact for each person, alternatively, use MISC and "photo file no." to record. Last choice for me would be to create a new fact "PHOTO No." fact and record the number there. I try to avoid new fact creation due to wanting to minimize GEDCOM compatibility problems. The FO searcher would readily take you to any "photo filename" to see which person that the photo is associated with. Find MISC <containing> <photo> for example. Since you WILL commence a new naming scheme, there will not be any duplications when the previous FO record numbers change as they are certain to do some time. Last but not least do not forget that in FO <reports> <lists> <multimedia list> should generate a report which you could copy/paste and squirrel away under a fake person named List Photo as note material. I like 3 or 4 digit name surname control, plus given name initials and a photo year or estimate plus a dash number, I'd use 4 rather than 3 unless you have many 3 digit surnames in order to best preserve proper alphabetical listings. Most 4 and a few 3 will alphabetize differently by the computer. Thus a Paul A. Studly 1986 photo becomes Stud-PA-1986-01.jpg use underscore for 3 digit surnames,the 01 allows up to 99 for a given year for any person Lee_-RE-1864-01.jpg for Confederate Gen. Robert E. Lee Stud-PA-will___.jpg Stud-PA-probate.jpg Stud-PA-birth___.jpg Stud-PA-farm___.jpg Wise-J_-2002-01.jpg Wise-JJ-2001-01.jpg or Stu_-PA-1986-01.jpg only if you have many 3 digit surnames You ought to be able to fix say 30- 40 an hour without killing yourself, so 30 days will fix say 900-1200 filenames. Just remember, the tortise and the hare, gently plodding along will get the job done. Good Luck - you know you gotta change, stop fighting it <g> Think you could talk your wife into doing it, and trust the data - get lost sayeth she !!! Paul Studly Cleveland/Chesterland, OH [email protected]

    07/27/2002 05:51:38