The DAM Forum
Welcome, Guest. Please login or register.
May 22, 2013, 08:42:07 PM

Login with username, password and session length
Search:     Advanced search
Jan 9, 2012
John Beardsworth's new Lightroom site
Lightroom Solutions
27960 Posts in 5113 Topics by 2914 Members
Latest Member: imthedamstar
* Home Help Search Login Register
+  The DAM Forum
|-+  General
| |-+  General Discussion
| | |-+  From CF card to archiving buckets - some Best Practice workflow questions...
« previous next »
Pages: [1] Print
Author Topic: From CF card to archiving buckets - some Best Practice workflow questions...  (Read 1429 times)
MarkP
Newbie
*
Posts: 12


View Profile
« on: July 15, 2006, 01:48:47 AM »


Hi Peter and Friends,

I’m a newbie who is just starting out to build a large and hopefully productive stock image bank.
I’ve read the DAM Book and found myself reviewing and using the Index quite a bit to fill in
some of the conceptual holes. I’ve also spent quite a bit of time following relevant threads
here on the forum, but I’m hoping to short -cut some of the study by asking a few questions
that may have been answered a hundred times - just so I don’t head down a blind alley
and find myself mugged by the data thugs.

Some workflow sequencing questions follow:

 
I was unable to unambiguously connect the Download/Workflow data structure and .DNG  processing
(Chapter 7) back to the "bucket" Archival data and information structures from Chapters 1 and 3.

If I have extrapolated this correctly, you download all of your raw (eg: .NEF) files in the original
 "temp"  CF-sequenced folders ( eg: 0001-0235, etc. ).

You then RENAME the files, either by using the Rename function or Import From Camera copying
them to a single ‘new’ folder/directory which has the entire image sequence with the new naming
convention (eg.: MMP_060708_1234).

Q: Do you force bridge to cache all of the initial temp directories - individually in order to utilize
    one of the rename capabilities or can this be done outside of the application or somehow bypassing
   the cache building process from within Bridge?

OK, so now you have a “working” folder/directory that has the entire image sequence - this makes
it convenient for Bridge to cache the entire project and have it all accessible on one ‘page’.

Q:  Has anyone else had stability issues with Bridge when the folder has 1350+  19.5 Mb
    .NEF’s? I’ve found that If I let the radar icon finish, and work very, very slowly, I can avoid
     crashes that can take many reloads/reboots to self-repair.
 
    ( I’m unfortunately still running OSX 10.2.8 with 2Gb RAM on a G4 Dual 1.25 - is this the
     problem?)

OK, so now, we have a large folder with a single set of Bridge cache files and have completed
(we hope) all of our ranking and sorting work. - it’s time to build our archival buckets:

Q: Optimizing folder size for DVD backup (4.4 Gb) is a bit problematic if you want to save them
     with a new set of Bridge caches included with each bucket - how do you know how large
    The cache files will be so that you don’t find yourself cascading  .DNG files downstream by hand
    to get each bucket back down to 4.4 Gb? Is there a standard amount of headroom to leave for
    this?

    Also, if you include a sub-directory scheme for when jobs overlap buckets - you are not
    compounding the issue by having to manually create new caches in each sub-directory?
     Is this correct or is this not “ best practice”?

    Additionally, If the final archive is comprised of .DNG’s why are the buckets  not named
    DNG_001_060708  instead of RAW_01_060708 as in Chapter 1? I'm questioning this
    since you clearly do not back up  your .NEF files once the .DNG's are archived.


    Next, on your workflow checklist, the next to last stage before Cataloging is "Archive Raw"
   (after  "Backup DNG"). Is this a non-essential step (if the Raw files are to be deleted) which can
    be removed from the checklist and the previous step labeled  "Archive DNG".?


Lastly, it seems that Ranking, Key-wording and Captioning are never completely done; at some point
you just decide that it’s time to put those originals to bed. To what extent are you “locked in” if you
want to continue massaging the metadata in the DNG’s but not have them sitting around  ‘pre-archived’
indefinitely.

     Once images have been ranked, can you re-rank the DNG’s in Bridge and just re-run Rank and File without
     appending to the previous rankings and making a big mess?

     Can you change/add keywords  to the DNG’s in iView as well as Bridge? I’m assuming that re-ranking is not
     backwards compatible to Bridge from iView so that Re-Ranking MUST be done in Bridge - if you want the
     rankings  displayed correctly in that application - this correct?

     I know that this means your write-once backups become obsolete - does anyone run into this issue and do
     you then ‘re-burn’ the project if you make any later modifications to its metadata?


I have read the workflow as carefully as possible and apologize if I have somehow missed  key elements that
address any of these issues. If not, I hope that you or someone else might be willing to clarify these finer points
as I'm hoping to make use of the workflow/pipeline to it‘s maximum advantage and efficiency (and not spend
another week back-tracking because I set out with iView before getting CS2 and reading the book!!!)

Thanks in advance for any help with all of this.

Mark P.


Logged
Marc Sabatella
Newbie
*
Posts: 41


View Profile
« Reply #1 on: July 15, 2006, 11:15:58 AM »

Lastly, it seems that Ranking, Key-wording and Captioning are never completely done; at some point
you just decide that it’s time to put those originals to bed. To what extent are you “locked in” if you
want to continue massaging the metadata in the DNG’s but not have them sitting around  ‘pre-archived’
indefinitely.

This is a question that interests me as well, and is probably relevant to anyone who is fairly new at this process.  Until we completely work out the kinks in our keywording process, we'll probably continue to find, for example, legacy images we imported a bit too hurriedly and are therefore light on keywording.

As I am not using Bridge or iView, I can't really address the specifics of how you might want to go about actually accomplishing these updates.  Just from what I remember reading in Peter's book, iView most certainly can write keywords to IPTC (be sure to sync!), and of course virtual set info has no meaning to Bridge anyhow, so really, ratings are the only thing I think you might worry about about transferring to Bridge.  I would say it seems to me that once you've done your initial processing with Bridge, you would probably be better off just using iView for as much as possible, and not worrying if Bridge can correctly see the new ratings, but if there is a straightforward and automatable to communicate the info back to Bridge, you might as well do it before running another backup to DVD.

In general, I think this is mostly an issue for legacy images and the first few batches of new images you bring in.  I suspect that once you've developed a good process, you'll get better at doing your initial kewording.  If nothing else, you won't be spending as much time keywording when you doing only new images as you may be now, when you might also be trying to import legacy images, so you won't be as tempted to skimp.  I'm sure that's one reaosn Peter recommends not bothering with legacy images until you've worked out a process, but as someone to doesn't shoot hundreds of images a day, I felt that looking at my legacy images was important in figuring out what kinds of metadata make sense for me - working out my own "controlled vocabulary", for example.

Quote
I know that this means your write-once backups become obsolete - does anyone run into this issue and do
you then ‘re-burn’ the project if you make any later modifications to its metadata?

The approach I am taking right now is to expect this and use re-writable media for backup until I feel things have stabilized.  I began this whole DAM process a few months ago after having my DSLR for about a year, and because my previous camera was only 2 MP and I shot moderately compressed JPEG, my entire archive - around five years' worth of pictures - fits on four DVD's.  I've updated these backups several times as I've added more metadata, and expect I'll do so at least a couple more times before I feel like it would be worthwhile to burn them to write-once media.  Realistically, I seem to have stopped active work on those files a couple of weeks ago, so I could probably just sync everything to IPTC and burn it now.  But there doesn't seem to be any harm in waiting, and since I only just last week brought everything online on my wife's computer, now she gets to spend some time browsing around and maybe we'll find more organization to do.

Ultimately, though, it is a mistake to assume that because you are using "write-once" media, that means you really literally only *need* to write it once.  We use write-once media because it is more stable long-term than re-writable, but still, I would not want to trust a backup I made to write-once media today to still be readbale in twenty or even ten years.  Sure, it's possible we'll still have devices capable of reading DVD.  But I would think it would be smart to expect to completely replace one's DVD backup library periodically.  How often - well, I'm sure you'll get vastly different recommendations there.
Logged
MarkP
Newbie
*
Posts: 12


View Profile
« Reply #2 on: July 15, 2006, 02:04:05 PM »

Marc,

Thanks for your response and insight into a few of these questions.

The ongoing keywording issue, as you point out, is probably due to being new to the process and
being sure that I will likely leave out some important catagory or reference. I finally checked out
some of the Controlled Vocabulary websites and at the very least, the checklists that I found there
should alleviate some of the anxiety over this

The second part of this is more of a specific issue related to iView, so I may ask it on another thread
(when there is a .xmp, does iView write to the .xmp or into the IPTC fields of the RAW file?).

Mark
Logged
peterkrogh
Administrator
Hero Member
*****
Posts: 5682


View Profile
« Reply #3 on: July 15, 2006, 07:46:13 PM »

It would probably be better to break your questions into multiple posts.  That said, here are some guidelines.

Q1.  I suggest letting Bridge build the cache before doing a lot of work on the files unless you are under deadline pressure.

Q2. I process images in Bridge in groups of generally no more than 300 or 400 images.  otherwise Bridge gets slow and unstable.  I bring them through in these chunks and then archive them and catalog with iView.

Q3.  Although I will generally create a Bridge cache for individual folders of DNG files before I put them away - if time permits - it really is not essential for me. I almost never go back to Bridge after I have created the DNGs and cataloged them in iView.

Peter

Logged
MarkP
Newbie
*
Posts: 12


View Profile
« Reply #4 on: July 16, 2006, 02:40:37 PM »


Thanks Peter, and I will start working on my blog skills as well.  Wink

Mark
Logged
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!