Multiple machines/operators working on shared images?

[cyber3d]

Workflow - logistics question. Multiple machines/operators working on shared images.

The machines are separated by some distance and cables are not in the equation. The problem is the logistics of sharing a "master" images drive (via airport). One advantage we have is that all machines will be running Photoshop/Bridge.

Here is my possible solution:
I figure we have 2 partitions. One for the RAW files, another for the finished PSD edited files.

In Bridge, each local machine will have a favorites showing:
1. the "airported" Master partition (untouched RAW files)
2. the "airported" Finished partition (Edited PSD files)

a) "download" a master to local hard drive, do edits and rename with version number.
b) "upload" the final version to the airport drive in the "finished" partition in a folder.

If someone needs to do any tweaking they can grab the latest "final" edited version, download to their local drive and tweak away. Once done, upload it back with a revision number.


Does that sound reasonable? Any thoughts? Comments?

[OsmosisStudios]

I'm no network admin, but that sounds like it should be feasible. The trick will be working with so many "revision" numbers: you'll need to work on a system for each user.

User A
User B
User C

File1.RAW would be your original.

File1_A_v1.psd
File1_B_v1.psd
File1_C_v1.psd

Then you'll end up with

File1_A_v2.psd -- OR -- File1_A_v1-1.psd
File1_B_v2.psd -- OR -- File1_B_v1-1.psd
File1_C_v2.psd -- OR -- File1_C_v1-1.psd

You see how this would get very difficult very quickly.

Your other option would be to have various folders on the "Server":

Master folder - Contains RAW files
Folder A - For User A
Folder B - For User B
Folder C - For User C
etc.

Within each folder could be further subfolders for .psd, .jpg, .tiff, small versions, BW versions, etc.

So, you'd end up with a folder on the "server" for each EVENT like this:
EVENT NAME
--> Unedited RAW
--> Final selected version(s)
USER A
--> PSD Folder V1
--> PSD Folder V2
--> PSD Folder V3
--> ...
USER B
--> PSD Folder V1
--> PSD Folder V2
--> PSD Folder V3
--> ...
USER C
--> PSD Folder V1
--> PSD Folder V2
--> PSD Folder V3
--> ...


This is closer to how I operate locally.

[IABoomer]

My gut says start learning about version control. There are plenty of open-source (freely available and well-documented) solutions that are designed for remote collaboration.

This article is probably a good start to get some background.

7 Version Control Systems Reviewed - Smashing Magazine

[cyber3d]

Awww, you guys are awesome! I'll check out the article and OsmosisStudios thanks for the great write up. Very clear.

cheers,

[Aegea]

I'm with IABoomer. You need a formal collaboration/version control system - once you have lost control it's the devil's job to restore it.