Small studio fileserver

Out of context: Reply #9

  • Started
  • Last post
  • 14 Responses
  • Amicus0

    I always name files this way

    Job number Client Name Job Description DDMMYY Version X.n

    every time a client change comes in 'n' changes. If a new concept is called for 'X' changes.

    eg.

    6969 Playboy March Issue (Cover) 260110 1.1.indd

    if I have multiple versions of images they get the same date and version number treatments, but every image has a plain english descriptor anyway. I always leave in any stock photo file names in case I need to track them down in the future.

    eg. marshmallows iStock_000005836864XLarge 260110 1.0

    Long file names make everything hassle free. :)

    Amicus 0Permalink
    UpvoteDownvote
    Flag
    • Shit the bed. You can read this stuff quickly and easily?rascuache
    • what happens if you want to revise an old version? branches and forks are sometimes necessarylukus_W
    • why the date? the file already has it.ESKEMA
    • If you save files to CD, long filenames are often truncated.lukus_W
    • each job goes in it's own folder, and yes it is pretty darn quick when you get use to the system. makes searches a dreamAmicus
    • revisions to old jobs get a new job number.Amicus
    • Burn CDs (or DVDs) in a format that doesn't truncate files. We would burn files to disk only every couple of months anyway with our workflow.Amicus
    Show [[ numHiddenNotes ]] more notesAdd Note
    SaveCancel

View thread