After many years of organizing image files I find there is good reason to have a Places folder, and in that folder I keep images of places and things (homes, headstones, cemetery entrances, etc). Most of the files in my Places sub-folder, are named beginning with the surname they are associated with (works for headstones, homes, businesses, vehicles, etc.), but there are some categories of place and thing images that lend themselves to being grouped together with a common leading term. A good example is photos of cemetery entrances, for which I start the filename with "Cemetery_" followed by the name of the cemetery followed by the geographic locations. For example "Cemetery_Woodlawn_Cemetery_Detroit_MI". That groups all the cemetery entrance images together and sorts them alphabetically by cemetery name. Another category is "Aviation_" which I use to preface photos of aircraft, flight simulators, etc. Yet another category with its own preface is "Structure_" which groups all photos of buildings, bridges, etc. together. The idea is that photos of anything that is not associated with a specific surname will benefit from being grouped with other, like things.
I enter all surnames in all uppercase letters, and do the same for state name abbreviations, and I separate each component of a filename with an underscore (_). Making all surnames uppercase allows other preface entries to stand out in a list and separating components with an underscore gives visual separation to those components, making them easier to read. All photos of individuals are kept in the topmost image folder. In Legacy that is currently the Pictures sub-folder. I have three subfolders under Pictures. They are Docs, Groups and Places. Docs contain all images of documents. Groups contain all images of two or more people, and Places contain images of places and things. This system has worked for me for many years in dealing with thousands of image files. It allows for easy lookups and minimizes the number of folders and therefore the complexity of filing and of hard drive searching. If I need to copy, or move, the entire collection I can do so by copying, or moving, the topmost folder (Pictures) and all subfolders. John Zimmerman Mesa, AZ On 11-May-13 2:51 PM, Syble Glasscock wrote: > Glad to be of help, I don't think you'll regret using the > Surname approach, yes, I too have some "Places" folders > becasuse of various reason. > Syble > Families Researching: /Cline/Klein, Daniel, Newton, > Witherspoon, Perryman, Gilbreath, Lindsey, Brown, > Foote, Curry, Fleming, Glasscock, Edwards, Waters, Wheat/ > > *From:* Paula Ryburn <[email protected]> > *To:* [email protected] > *Sent:* Saturday, May 11, 2013 1:46 PM > *Subject:* Re: [LegacyUG] Organization of Photos, > Scanned Documents and etc. > > Thanks, Syble, for your feedback. After pondering the > decision quite a bit, I use the surname-first approach > & you've made me sigh in relief. ;) I've just > recently added a folder for "places" that aren't > really linked to an individual. Otherwise, all > documents and photos are named for the primary person. > --Paula in Texas > Researching: Adair Baker Beasley Benson Betz Bigley > Blagrave Burton Chapman Clement Clough Coppernoll > Costine Daulton Dinwiddie Doody Ellis Exline Field > Floran Floyd Gates Goodale Gordon Gump Hale Harbaugh > Hind Hopkins Hughes Hurdle Jones Klein Koyle Laswell > McDonald Misner Passwaters Pelton Roberts Roche Ryburn > Sanford Short Singer Sullivan Weller Williams > > > *From:* Syble Glasscock <[email protected]> > *To:* [email protected] > *Sent:* Sat, March 16, 2013 9:44:20 AM > *Subject:* Re: [LegacyUG] Organization of Photos, > Scanned Documents and etc. > > <snip> > A word of caution, when I started, I'd name the > document, i.e.: wwi_draft_curry_james, thinking this > would be good to have all WWI Draft Registration > together, but as the years have gone by, how I wish, > I'd named everything with the surname first that way > all items for that particular individual would have > been together. > Now, with having my own website, it would be a lot of > trouble renaming all items. > Hope this helps, consider all ideas, but try as best > you can to plan for many more items attached to Legacy. > Syble > <snip> > > > 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 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
