<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Computer Tricks 3 &#8211; Naming Electronic Files</title>
	<atom:link href="http://blog.progenealogists.com/2009/11/computer-tricks-3-naming-electronic-files/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.progenealogists.com/2009/11/computer-tricks-3-naming-electronic-files/</link>
	<description>Regular posts from each member of our corporate office in Salt Lake City. We hope you’ll notice just how passionate we are about research and about the extensive services we provide to our clients.</description>
	<lastBuildDate>Thu, 29 Dec 2011 02:34:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dallyhorton</title>
		<link>http://blog.progenealogists.com/2009/11/computer-tricks-3-naming-electronic-files/comment-page-1/#comment-222</link>
		<dc:creator>dallyhorton</dc:creator>
		<pubDate>Thu, 29 Dec 2011 02:34:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.progenealogists.com/?p=467#comment-222</guid>
		<description>Thanks for the post Natalie, just what I was looking for. I&#039;ve been researching my family history for the past four years using The Master Genealogist, but the media capabilities of TMG are awful, so I&#039;ve never spent time in this area. I&#039;ve just purchased FTM 2012 with the awesome TreeSync feature, and now I&#039;d really like to nail the naming and storage of my images. Your post really makes sense to me, and I know it&#039;s two years old, but how do you go about naming group images?

Regards,
Troy</description>
		<content:encoded><![CDATA[<p>Thanks for the post Natalie, just what I was looking for. I&#8217;ve been researching my family history for the past four years using The Master Genealogist, but the media capabilities of TMG are awful, so I&#8217;ve never spent time in this area. I&#8217;ve just purchased FTM 2012 with the awesome TreeSync feature, and now I&#8217;d really like to nail the naming and storage of my images. Your post really makes sense to me, and I know it&#8217;s two years old, but how do you go about naming group images?</p>
<p>Regards,<br />
Troy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arthur Dirks</title>
		<link>http://blog.progenealogists.com/2009/11/computer-tricks-3-naming-electronic-files/comment-page-1/#comment-46</link>
		<dc:creator>Arthur Dirks</dc:creator>
		<pubDate>Fri, 08 Jan 2010 18:07:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.progenealogists.com/?p=467#comment-46</guid>
		<description>I&#039;ve bookmarked and returned to this page several times, as I struggle with this same problem. This is among the closest I&#039;ve found to a useful idea for me as I rethink it all. For more than a decade I&#039;ve tried many naming conventions and variations for what have become thousands of images and files. A scanned image often lands in a half-dozen places besides my family history file, in several croppings, resolutions, and states of digital improvement. Over time the same image can have many filenames, and I have wasted cumulative hours, if not days, trying to locate and identify the best version of perhaps slightly different images shot at the same time. Often I create yet another version from an original. My family images are associated with a text file with full description, provenance and identifications. Documents also get a transcription and a pdf. I&#039;ve tried to work with metadata to differentiate versions, but entering and maintaining it is cumbersome and uncompressed formats don&#039;t carry it. A clear file name is required to associate and reference all these related data. THAT SAID - your scheme has promise, particularly for documents and some photos - group photos might be a challenge. I like the rationale of your system, beginning with surname and including birth year - followed by date and subject. I&#039;m looking for ways to adapt this for my needs, but I suspect you came up on a Mac without the old Intel filename restrictions. I would find more than a 30-character filename cumbersome, requiring side-scrolling in lists, and perhaps error-prone. A numbering scheme, preferred by more impersonal researchers, is much clearer and shorter but not user-friendly. So, now I&#039;m moving toward conventionalizing on a filename with: a 4- or 5-character consistent surname abbreviation with unique initials - birthdate (if known) - document date (if known) - document nature abbreviation - version abbreviation (including resolution). And I&#039;ll try to get it all under 20 or so characters. Now I just have to figure out how (or whether) to migrate to it.
Thanks for sharing your methods.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve bookmarked and returned to this page several times, as I struggle with this same problem. This is among the closest I&#8217;ve found to a useful idea for me as I rethink it all. For more than a decade I&#8217;ve tried many naming conventions and variations for what have become thousands of images and files. A scanned image often lands in a half-dozen places besides my family history file, in several croppings, resolutions, and states of digital improvement. Over time the same image can have many filenames, and I have wasted cumulative hours, if not days, trying to locate and identify the best version of perhaps slightly different images shot at the same time. Often I create yet another version from an original. My family images are associated with a text file with full description, provenance and identifications. Documents also get a transcription and a pdf. I&#8217;ve tried to work with metadata to differentiate versions, but entering and maintaining it is cumbersome and uncompressed formats don&#8217;t carry it. A clear file name is required to associate and reference all these related data. THAT SAID &#8211; your scheme has promise, particularly for documents and some photos &#8211; group photos might be a challenge. I like the rationale of your system, beginning with surname and including birth year &#8211; followed by date and subject. I&#8217;m looking for ways to adapt this for my needs, but I suspect you came up on a Mac without the old Intel filename restrictions. I would find more than a 30-character filename cumbersome, requiring side-scrolling in lists, and perhaps error-prone. A numbering scheme, preferred by more impersonal researchers, is much clearer and shorter but not user-friendly. So, now I&#8217;m moving toward conventionalizing on a filename with: a 4- or 5-character consistent surname abbreviation with unique initials &#8211; birthdate (if known) &#8211; document date (if known) &#8211; document nature abbreviation &#8211; version abbreviation (including resolution). And I&#8217;ll try to get it all under 20 or so characters. Now I just have to figure out how (or whether) to migrate to it.<br />
Thanks for sharing your methods.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

