The iPhoto Challenge I

You don't need a weatherman to know which way the wind blows
Over the years I've had to deal with many different forms of digital asset management solutions. I've managed big iron, I've wrangled the archaic and show mercy on the weak. But for my personal use, only one application was ever good enough; iView MediaPro (or iView Multimedia as it was originally called). iView was fast, it was feature packed, it was logical. iView was designed by people who understood what users like me need and want out of an image management application. And then came iPhoto; and absolutely nothing changed.

I am of course an Apple geek, and I love their in-house applications. When iPhoto surfaced, it seemed like a great idea; iTunes, for photographs! Absolutely logical. It also absolutely failed to deliver.

Gettin' in Tune
iTunes works well because it's is 100% tied to, and reliant upon, the id3 tags--the metadata--imbedded in the music files. If you're like me, you're anal about making sure the tags are correct, so you can quickly find the music you want. iPhoto failed on this front for a number of reasons. First, the equivalent metadata to images, IPTC, isn't automated as with music and CDDB, so each image has to be hand tagged. iPhoto's keyword function was anemic and buried. The "roll" system was weak and hard to navigate as well.

iTunes doesn't ask a lot in terms of working with your music files, short of the tagging and perhaps imbedding album art. Images are a whole different story; they are there to be handled, edits, cropped, printed; interacted with. And while iPhoto had rudimentary "mom and pop" features to handle this, more seasoned users found it wanting. Why bother with iPhoto when you can do real editing in Photoshop? But more than this, iPhoto's file system seemed to be openly hostile to anyone who wanted to make sense of the file structure of their images. And so, pro users sniffed and turned their noses at iPhoto. Users like me.

The Seeds of Discontent
iPhoto went through a number of revisions to address the biggest issues; speed and capacity were improved, the filesystem, while still quite dictatorial, at least made some visual sense. I gave every revision the benefit of the doubt, throwing all I could muster at it. But at the end of the day, I always returned to my faithful iView Media Pro.

By version 2, iView had grown some serious functionality, particularly folder watching (but, significantly, not sub-folder watching), which enabled me to alter my workflow enough so iView sitting in the background could automatically load up images I had dumped into my directory. It would also automatically generate dated and file-type folders.

You can now create nested folders
in iPhoto

Now comes iPhoto 5. It has RAW import and more advanced editing tools, but most significantly, Apple seems to realize how important organization is, and is addressing it. The only major feature missing is folder watching, but (and here's where this article is relevant to this website) it should be no brainer to create folder watching and other hot-folder functions tied into iPhoto with, you guessed it, Automator.

Annoyances remain, however. iPhoto's filesystem is unchanged, and it perplexes me there is no preference to choose your own images folder; iTunes allows this, why not iPhoto (yes, I'm aware you can alias it to another location and other tricks, but that doesn't count)? Camera import remains very slow, probably due to iPhoto's insistence on copying and databasing every image. Even EXIF auto-rotated images are treated by iPhoto as edits, so every rotated image is duplicated and backed up into the "originals" folder. I wish iPhoto had a "lower power" mode, wherein it would treat its filesystem as a "dumb" directory, make editing backups manual and turn off all the on-the-fly Quartz scaling. Then it might feel like a fast and nimble image cataloger.

Despite my initial misgivings and the repetition of history, I am now conducting an experiment: I am forcing myself to use iPhoto 5 for the next month. If-and this is a big if-its performance is up to par, and the folder management delivers, then I could be looking at "switching"; the promise of Automator and other subtle-yet-devious OS X integration and functionality is too great to ignore. I'll report back with my findings as time and inclination allow, but my gut feeling at this point is that iPhoto is now "good enough" for most anyone's personal image cataloging needs.

On to [Part II...](http://www.automatorworld.com/archives/the-iphoto-challenge-ii/)