<?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: Deep Thoughts on File Naming Conventions</title>
	<atom:link href="http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/feed/" rel="self" type="application/rss+xml" />
	<link>http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/</link>
	<description>Design, Development, Technology and My Life.</description>
	<lastBuildDate>Tue, 27 Dec 2011 16:30:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Developers are from Mars, Designers are from Venus with Chad Udell &#124; UsableWebb</title>
		<link>http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/comment-page-1/#comment-146025</link>
		<dc:creator>Developers are from Mars, Designers are from Venus with Chad Udell &#124; UsableWebb</dc:creator>
		<pubDate>Sat, 19 Jun 2010 20:06:13 +0000</pubDate>
		<guid isPermaLink="false">http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/#comment-146025</guid>
		<description>[...] File organization and directory structure. We shouldn&#8217;t be arguing over how things are named. Directory structure is not a battlefield, but try to make naming make sense and shouldn&#8217;t include names, version numbers, etc. Deep Thoughts On File Naming Conventions. [...]</description>
		<content:encoded><![CDATA[<p>[...] File organization and directory structure. We shouldn&#8217;t be arguing over how things are named. Directory structure is not a battlefield, but try to make naming make sense and shouldn&#8217;t include names, version numbers, etc. Deep Thoughts On File Naming Conventions. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Killian</title>
		<link>http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/comment-page-1/#comment-107150</link>
		<dc:creator>Killian</dc:creator>
		<pubDate>Tue, 09 Jun 2009 16:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/#comment-107150</guid>
		<description>I prefer using the yymmdd or yyyymmdd along with a descriptive naming system for attaching dates to files. 

I usually keep several daily versions with an a, b, c, or d addendum. Then I can save or delete daily finals, weekly finals, and monthly finals fairly easily. I like having the older versions around so I can go back in case I decide I took the wrong path somewhere.

The main reason is that for a similarly named file an alphabetic sort will put the files in chronological order. 

People might find the naming structure initially a bit backwards, but once you get over that small hump it really performs well.</description>
		<content:encoded><![CDATA[<p>I prefer using the yymmdd or yyyymmdd along with a descriptive naming system for attaching dates to files. </p>
<p>I usually keep several daily versions with an a, b, c, or d addendum. Then I can save or delete daily finals, weekly finals, and monthly finals fairly easily. I like having the older versions around so I can go back in case I decide I took the wrong path somewhere.</p>
<p>The main reason is that for a similarly named file an alphabetic sort will put the files in chronological order. </p>
<p>People might find the naming structure initially a bit backwards, but once you get over that small hump it really performs well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Red5dsd</title>
		<link>http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/comment-page-1/#comment-10525</link>
		<dc:creator>Red5dsd</dc:creator>
		<pubDate>Thu, 01 Nov 2007 07:07:18 +0000</pubDate>
		<guid isPermaLink="false">http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/#comment-10525</guid>
		<description>My file naming convention goes like this:
v1-(CLIENT ACRONYM)_(BriefProjectDescription,i.e.Brochure,HomePage,etc.)

So, the first version of a tradeshow flyer designed in InDesign for IBM might look like this:

v1-IBM_TradeFlyer.indd

If I had three initial versions of that same flyer project I would probably have three files like this:

v1a-IBM_TradeFlyer.indd
v1b-IBM_TradeFlyer.indd
v1c-IBM_TradeFlyer.indd

I use a &quot;v&quot; at the beginning to indicate a working master file version. I use a &quot;c&quot; for the client comp version, a &quot;m&quot; for the mechanical (say the working file needs to have the type outlined or saved as a flattened tiff for output), and an &quot;f&quot; for the final file going to press.

So my working file would be:
v1b-IBM_TradeFlyer.indd

Comp to client:
c1b-IBM_TradeFlyer.pdf

Flattened file to ensure gradients blend nicely:
m1b-IBM_TradeFlyer.tif

Final artwork going to press in CMYK with crop marks
f1b-IBM_TradeFlyer.pdf

I keep each of these file types within folders:
v1b-IBM_TradeFlyer.indd goes in the Builders folder

c1b-IBM_TradeFlyer.pdf goes in the Comps folder

m1b-IBM_TradeFlyer.tif goes in the Mechanicals folder

f1b-IBM_TradeFlyer.pdf goes in the FinalArt folder

---

I use initial caps on the words because I avoid using spaces in file names. This convention helps me automatically produce files that are web friendly when working on web projects.

That&#039;s my scoop!</description>
		<content:encoded><![CDATA[<p>My file naming convention goes like this:<br />
v1-(CLIENT ACRONYM)_(BriefProjectDescription,i.e.Brochure,HomePage,etc.)</p>
<p>So, the first version of a tradeshow flyer designed in InDesign for IBM might look like this:</p>
<p>v1-IBM_TradeFlyer.indd</p>
<p>If I had three initial versions of that same flyer project I would probably have three files like this:</p>
<p>v1a-IBM_TradeFlyer.indd<br />
v1b-IBM_TradeFlyer.indd<br />
v1c-IBM_TradeFlyer.indd</p>
<p>I use a &#8220;v&#8221; at the beginning to indicate a working master file version. I use a &#8220;c&#8221; for the client comp version, a &#8220;m&#8221; for the mechanical (say the working file needs to have the type outlined or saved as a flattened tiff for output), and an &#8220;f&#8221; for the final file going to press.</p>
<p>So my working file would be:<br />
v1b-IBM_TradeFlyer.indd</p>
<p>Comp to client:<br />
c1b-IBM_TradeFlyer.pdf</p>
<p>Flattened file to ensure gradients blend nicely:<br />
m1b-IBM_TradeFlyer.tif</p>
<p>Final artwork going to press in CMYK with crop marks<br />
f1b-IBM_TradeFlyer.pdf</p>
<p>I keep each of these file types within folders:<br />
v1b-IBM_TradeFlyer.indd goes in the Builders folder</p>
<p>c1b-IBM_TradeFlyer.pdf goes in the Comps folder</p>
<p>m1b-IBM_TradeFlyer.tif goes in the Mechanicals folder</p>
<p>f1b-IBM_TradeFlyer.pdf goes in the FinalArt folder</p>
<p>&#8212;</p>
<p>I use initial caps on the words because I avoid using spaces in file names. This convention helps me automatically produce files that are web friendly when working on web projects.</p>
<p>That&#8217;s my scoop!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Best Practices of Adobe Flash CS 3 &#171; RTFM - Stop being a retard.</title>
		<link>http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/comment-page-1/#comment-9244</link>
		<dc:creator>Best Practices of Adobe Flash CS 3 &#171; RTFM - Stop being a retard.</dc:creator>
		<pubDate>Wed, 10 Oct 2007 19:03:31 +0000</pubDate>
		<guid isPermaLink="false">http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/#comment-9244</guid>
		<description></description>
		<content:encoded><![CDATA[<p>[...] Naming Conventions :¬† Deep Thoughts on File Naming Conventions [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tsun1234</title>
		<link>http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/comment-page-1/#comment-4145</link>
		<dc:creator>Tsun1234</dc:creator>
		<pubDate>Tue, 24 Jul 2007 19:29:14 +0000</pubDate>
		<guid isPermaLink="false">http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/#comment-4145</guid>
		<description>I don&#039;t know if time is totally irrelevant on filenames. It&#039;s up to file type, but the original date is recorded only on original machine. Once you download the file, the date is the download date, not the original release. I still think is important maintain the date on file names, according to the project.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know if time is totally irrelevant on filenames. It&#8217;s up to file type, but the original date is recorded only on original machine. Once you download the file, the date is the download date, not the original release. I still think is important maintain the date on file names, according to the project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lawrence</title>
		<link>http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/comment-page-1/#comment-2191</link>
		<dc:creator>Lawrence</dc:creator>
		<pubDate>Wed, 13 Jun 2007 17:31:05 +0000</pubDate>
		<guid isPermaLink="false">http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/#comment-2191</guid>
		<description>I typically use Subversion when I need to maintain multiple versions.  But for situations where Subversion or CVS would be overkill, its still best to automate this process as much as possible.  When doing this its often easier to move the backups to a separate directory (to avoid clutter) and append a date to the directory name (its redundant yes, but its easy to get that information from the system.)

With this convention, you can use simple tools that come with your OS like Automator (http://macapper.com/2007/05/28/tutorial-automator-basics/) or on Windows, a simple batch file (http://lifehacker.com/software/version-control/hack-attack-simple-version-control-170164.php) to backup your files.

Of course, if you need multiple backups from the same day, or if you want them visible and not hidden in backup directories, you might be out of luck there.  In that case, I like to use simple scripts to &quot;roll&quot; the files easily enough (rolling means to do something like this: rename foo_v2 to foo_v3 if it exists, rename foo_v1 to foo_v2 if it exists, then copy foo to foo_v1; this way the most recent backup is always the _v1 -- that&#039;s just a personal preference of mine.)

On Windows, I would recommend spending a few bucks to get a commercial product called KeepSafe from Stardock since it automatically backs up files you want with no user action required.</description>
		<content:encoded><![CDATA[<p>I typically use Subversion when I need to maintain multiple versions.  But for situations where Subversion or CVS would be overkill, its still best to automate this process as much as possible.  When doing this its often easier to move the backups to a separate directory (to avoid clutter) and append a date to the directory name (its redundant yes, but its easy to get that information from the system.)</p>
<p>With this convention, you can use simple tools that come with your OS like Automator (<a href="http://macapper.com/2007/05/28/tutorial-automator-basics/" rel="nofollow">http://macapper.com/2007/05/28/tutorial-automator-basics/</a>) or on Windows, a simple batch file (<a href="http://lifehacker.com/software/version-control/hack-attack-simple-version-control-170164.php" rel="nofollow">http://lifehacker.com/software/version-control/hack-attack-simple-version-control-170164.php</a>) to backup your files.</p>
<p>Of course, if you need multiple backups from the same day, or if you want them visible and not hidden in backup directories, you might be out of luck there.  In that case, I like to use simple scripts to &#8220;roll&#8221; the files easily enough (rolling means to do something like this: rename foo_v2 to foo_v3 if it exists, rename foo_v1 to foo_v2 if it exists, then copy foo to foo_v1; this way the most recent backup is always the _v1 &#8212; that&#8217;s just a personal preference of mine.)</p>
<p>On Windows, I would recommend spending a few bucks to get a commercial product called KeepSafe from Stardock since it automatically backs up files you want with no user action required.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Moats</title>
		<link>http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/comment-page-1/#comment-2158</link>
		<dc:creator>John Moats</dc:creator>
		<pubDate>Tue, 12 Jun 2007 23:05:15 +0000</pubDate>
		<guid isPermaLink="false">http://visualrinse.com/2007/06/12/deep-thoughts-on-file-naming-conventions/#comment-2158</guid>
		<description>I have a small tip to add.  For example if we were working on a site mock and made only small changes made it would be named: site_mock_v1_r1.psd.  Adding the revision to the filename gets people out of the habit of just overwriting current versions because the changes are &quot;small&quot;.  At the end of the day/stage just keep the most recent version out and the others in a folder called &quot;revisions&quot;.</description>
		<content:encoded><![CDATA[<p>I have a small tip to add.  For example if we were working on a site mock and made only small changes made it would be named: site_mock_v1_r1.psd.  Adding the revision to the filename gets people out of the habit of just overwriting current versions because the changes are &#8220;small&#8221;.  At the end of the day/stage just keep the most recent version out and the others in a folder called &#8220;revisions&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

