Jump to content

Organizational Morass


Recommended Posts

<p>Ok, here's the quandry over <strong>what I have</strong>: I have archived digital and scanned images on two hard drives (internal and external) and CD's (fortunately no dvd thrown into the mix). I usually have an archive file folder named: 2006 Archive I; 2006 Archive 2; 2007 Archive 1-3; and then usually individual folders named 2006 July Fourth; 2007 Birthday; 2008 Parades; Submissions (to publications). In the individual folders may be a mix of scanned images and digital images. I've owned two digital cameras so the chronological archives many have duplicate _dscxxxx numbers (which is why I have multiple archive folders by year). In the individual folders there may be dupes of the dsc files, dsc converted to DNG, a jpg folder, and photoshopped images named something like happybirthday001.psd. My scanned images are large tif files but I could save as nef if you all think so.<br>

<strong>What I'd like to end up with</strong> is: a searchable archive of all images (keyword search will work) duplicated on three external harddrives (two at one location; another offsite). I'd like to maintain the syncronicity between the two hard drives when images are added as either scans or digital files.<br>

<strong>What I need is advice on:</strong> software to help me accomplish this and suggestions on how to go about it. (Lightroom?)<br>

<strong>If needed</strong>: I think I have about 500GB total of images and have a Windows based desktop.<br>

Happy New Year in many ways...</p>

Link to comment
Share on other sites

<p>You seem to be flying off in several directions, some of which are non-productive.</p>

<p>The basic requirement of a relational database is that each record (i.e., image) has a unique identifier. You don't necessarily have to rename each file, because the identifier consists of the entire path name. It is sufficient to create a directory named based on a date code and subject, and place the image files therein.</p>

<p>A related concept is that there are two sides to "organization" - storage and retrieval. It's best to stick with a simple and scalable means of storage - changing it later is costly (and the most common mistake made or "recommended" by neophytes). You can be quite flexible with retrieval functions. In particular, you don't have to store things by topic, just in a known location. The query (retrieval) can be as elaborate as you wish as long as it points to the master location(s).</p>

<p>If you copy the images to several locations, you must use one as the master and the others strictly as backups. If you deliberately (or accidently) alter files in a backup, you have to resynchronize all the directories. This can lead to mistakes and data loss.</p>

<p>There are several books on database management for photographers, loosely known as "Digital Asset Management", or DAM. "The DAM Book" by Peter Krogh is an excellent place to start.</p>

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...