after the DAM workflow checklist

[Oliver]

After the initial workflow checklist has been created and the files placed in their spot in a client-named sub-folder in the RAW buckets in the live and local archive.  I then batch out the images I want to give to the client to a Derivative folder with a sub folder with the client's name where I access the files to tweak and make psd and master files. 

Do I then create another subset in my DAM Catalogung subfolder with my clients name filled with images from the RAW and DRV folders before putting that client away?

This seems crucial if I discard my jpeg batch leaving only master files and BW versions etc...  in the DRV bucket because I will then rely totally on the cataloguing software to see the whole shoot and my variations on the original files, correct?  If I wanted to see those images in a browser I would have to navigate to the appropriate bucket in both RAW archive and DRV archive and I would still need the cataloguing software to tell me which bucket that client was in.  Is that correct?

As Peter says in the book, it is difficult to let go of subject based heirarchy.

Any thoughts or directions appreciated.

Oliver.

[peterkrogh]

Oliver,
Here's what I do after putting DNG files away:

1. I make web galleries and put them online.  I save these in a folder, but do not catalog these.
2. If I batch out delivery files, I will generally keep these as a business record in a Derivative files bucket.  If they are a straight batch-out, I will probably not catalog them.
3. If I make Master files, I will usually be opening these files through Camera Raw again, making some changes to the RAW files, and save the layered Master Files in a Derivative Files bucket.  I will keep both Master Files and Delivery files.  These get cataloged.

Does this clear it up?
Peter

[danaltick]

Peter,

Can you tell me what you mean by straight batch out?  What other type of batch outs do you do?

Also, I haven't yet fooled around with web galleries.  My original plan for portrait shoots was to create an emailable quicktime or pdf slideshow with filename captions for client selection.  I would then email it to the client to maintain privacy.  Can you tell me if a web gallery would be more beneficial here, and can I still maintain privacy with it?  Thanks.

Dan

[peterkrogh]

A Straight batch-out would be just that, images batched out without any further adjustment.  These can be re-created at any time.

This would be as opposed to batching the images out, and thenn running them through another process, like the CaptionMaker, or NikSharpenerPro.

I almost always use web galleries.  They are immediately accessible, easy to share, and generally, clients love them.
Peter

[danaltick]

Peter,

Thanks for the info.  Time to start learning about web galleries.

Dan

[Rick McCleary]

Dan,

An unexpected benefit of this enitre DAM exercise has been web galleries.  They have absolutely revolutionized the way I am able to share images with my clients.  In one step, I am able to share the selects from a shoot as well as offering good-sized comping images for my clients to use in their layouts.  (I set up the iVIew prefs to create 800x800 large views.)  Once you customize one of the templates available in iView, it is automatic to create a web gallery.  The templates available range from utilitarian html to very elegant CSS.

I handle private viewing in the following way:
1) On my web server, I place the uniquely named folder of new images (including the index.htm files) in a directory named "webgallery".  
2) I confirm its presence by navigating to it with a browser.
3) I copy the url from the browser and paste it into an email that I send to my client.
4) Done!

For example, a client will go to www.rickmccleary.com/webgallery/NFCU_California_051123.
The privacy issue is by default.  Unless you are directed to that url, there's no way you could guess it.  Since I'm not dealing with national security here, that's good enough for me (and my clients) at this point.

I'm open to any suggestions on how to better handle this.

[danaltick]

Rick,

Thanks so much for letting me know this.  I can easily do that on my webserver.  That definitely sounds like the way to go.  I had forgotten that those URL are private by default.  Now all I will have to do is email a URL.... awesome!

Definitely time to start learning about iView's web gallery capability.  Any tips on that would be much appreciated.  Thanks again.

Dan

[Rick McCleary]

Best way to get started is to read the iVIew manual about HTML Galleries.  Feel free to ask questions as you go.

The thing you'll definitely want to do is customize one of the templates by adding things like your logo, banner, disclaimers, email link, etc.  If you have some basic HTML knowledge, it's pretty straightforward to customize a template.  There are a new series of CSS templates on the iView downloads site that are quite nice.

From a cataloging standpoint, Peter's recommendation (and my confirmation) is to NOT catalog the web galleries.  No need to since the images themselves are already cataloged.  Just make 'em and save 'em in a separate folder.  Also, I leave them on the server indefinitely.  This allows the client to return to them at any time.

[Oliver]

Peter,

1. Do you keep the web gallery folder with the derivatives?
2. Do you then have orig drive:/Raw_xxx/Client Folder,  drv drive:/Raw_xxx/Client Folder,  and client subset in your cataloguing program?

Many thanks,

Oliver.

[peterkrogh]

I keep the web galleries in a folder of web galleries.  This is a pretty small data set (three years of digital shooting can fit on one DVD).

As Rick points out, no need to catalog these; they will just confuse the derivative catalog.

They are useful to have if the client ever wants to look at them again, and you need to re-upload.

They are also useful as a business record: a record of what is presented to the client.

They are also useful as a copyright submission.  I consider the posting of the web gallery to be first publication, so that is my deposit.
Peter

[danaltick]

Rick & Peter,

Thanks again for the info... much appreciated.  I will put this on my list of things to do.  I'm finally nearing the end of my migration.  All I've got left are my legacy JPEG's from my Sony compact camera that are still in Photoshop Album.  I tried to import that Photoshop Album catalog directly into iView using the iView script, but it aborts, so looks like I will have to dump them in manually.  I think I'm just going to create a legacy subfolder in the bucket and legacy virtual set in iView and export them from Photoshop Album one virtual set at a time.  That way I can at least maintain the virtual sets under legacy in iView.  Should wrap that up in another day or two.  I will just keyword them all with "legacy" for now and worry about metadata or ratings later, if I ever even do that for these.

Dan

[peterkrogh]

Dan,
Sounds like a plan.
As I have been going through 2005, I have run across a number of images that were never rated (Pre-CS2 files, plus some JPEGs from the family Point and Shoot).  I have tagged these as Unrated, and will be working on these as time permits
Peter

[danaltick]

Peter,

Good idea.  I'll definitely tag them as unrated.  I'm so close now I can taste it.  Now that I've got all my RAW's converted and cataloged with virtual sets, keywords, and ratings, I'm really starting the see the beauty of this system!  I even deleted my old CR2 files and bid them farewell... those JPEG previews just look too good .  I ran a slideshow of all my 1 star and higher photos...very nastalgic looking back through time over my shoots.

Dan