CE, I am not suggesting any renumbering of the "master" file. Your point about maintaining RINs used for your website is very good. Re-read what I was discussing about importing files. If an import file has the same RINs that already exist in the master file, then the imported RINs must be renumbered whether you like it or not. My point was to force the renumbering of the imported records to a number range which could be easily identified after the files have been combined. Then complete any merging that might be possible. Then look for the higher RIN numbers to see which imported records were not merged and therefore are probably new additions to your file. Ron Taylor
--- On Wed, 4/11/12, CE WOOD <[email protected]> wrote: > From: CE WOOD <[email protected]> > Subject: RE: [LegacyUG] Using IntelliShare > To: [email protected] > Date: Wednesday, April 11, 2012, 5:22 PM > > I am not talking about renumbering my Legacy file. I > am so frustrated when website genealogies renumber their > files. Then the links I have put into my sources no > longer work because the url incorporates the RIN number. > > > > Yes, I can go to the index and find the person again, IF the > author uses the same name that I do. There are so many > bariations of names - by title, with the "de" or without, > etc. As I said, since it makes no difference to the > authors, unless OCD, why renumber and make it so difficult > for those who otherwise like the site? > > > CE > > > > > Date: Wed, 11 Apr 2012 08:55:52 -0700 > From: [email protected] > Subject: Re: [LegacyUG] Using IntelliShare > To: [email protected] > > > > > That's what I meant. You stated it well. > Ron Taylor > > --- On Wed, 4/11/12, R G Strong-genes <[email protected]> > wrote: > > > From: R G Strong-genes <[email protected]> > Subject: Re: [LegacyUG] Using IntelliShare > To: [email protected] > Date: Wednesday, April 11, 2012, 9:34 AM > > > > <!--<br>.ExternalClass #ecxyiv141474377 > .ecxyiv141474377hmmessage > P<br>{padding:0px;}<br>.ExternalClass > #ecxyiv141474377 > body.ecxyiv141474377hmmessage<br>{font-size:10pt;font-family:Tahoma;}<br><br>--> > > > > > > > > > Ron, CE, > > > Though I too agree with you and also use the web to display > my family tree, > however, I do believe this should not affect those RIN and > MRINs already in your > database, since the only RINs being renumbered would be the > incoming file and > since the duplicates would be merged into the main they > would retain the main > file’s numbers and only the added people would end up with > the higher > re-numbered IDs. > > > Russ > > > > > > > > > > > > From: CE WOOD > > > Sent: Tuesday, April 10, 2012 9:48 PM > > > To: [email protected] > > > > Subject: RE: [LegacyUG] Using IntelliShare > > > > > > > > > I can't agree > more!!! It is incredibly frustrating when people renumber; > the url entered > becomes totally useless. There is absolutely no need, beyond > OCD, to > renumber. Sites that do not are the sites of choice! > > CE > > > > > > > From: [email protected] > > > To: [email protected] > > Subject: Re: [LegacyUG] Using > IntelliShare > > Date: Tue, 10 Apr 2012 19:30:16 +0100 > > > > > Ron, > > > > There is one very good reason for *not* renumbering > RINs, > if one creates > > Pedigree Webpages. These pages use the RIN for the > file > name eg. on my > > website the URL for myself is > http://www.fergys.co.uk/genealogy/1.html > > (actually I use the .php > extension, but for this illustration it does not > > matter). > > > > > All search engines, such as Google, use the URL to > identify the > page > > location, i.e. if someone is searching for me they will > find that > page > > (sooner or later!) at the above URL. If the RINs are > changed then > all > > bookmarks which people have made will be rendered > invalid, before a > search > > engine can register the new URL there will be a delay > (which may > be a long > > delay), and thus all the effort which one should have > put in > promoting the > > site and contents will end up being a waste of > time. > > > > Ron Ferguson > > http://www.fergys.co.uk/ > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 > 2009: > http://www.mail-archive.com/[email protected]/ > 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/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ 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
