You can download the paper right from here:
http://incopysecrets.com/dloads/InCopyCS3_Workflow.pdf
… I’ll edit the post in the next couple minutes to fix it.

The remote workflow is meant for *InCopy* users working from home, not designers. (Or at least, designers only work from one location … either home or on-site.) That’s because everything works best when the ID file stays where it is.

So the designer working from home could keep the ID file on her (or his) computer, and generate assignments and assignment packages from there, and editors email her their return packages, where she updates the ID layout locally on her computer with the updated content. I know a bunch of companies where the whole workflow is done remotely.

If you’re trying to come up with a workflow where the ID file can be moved from the server to a designer’s local computer and back again, I’m sure it’s possible but there are too many factors to consider in coming up with the safest, easiest strategy for you here in a comment.

Perhaps other readers can chime in? (Soon the site’s redesign will make it easier for people to find recent comments to older posts … sorry!) In the meantime you might try asking on the Adobe InCopy user-to-user forums.

(I put a note on ID Secrets about this, but no one’s responded, so I thought I’d try it here.)

I’m trying to figure out the best way to design a workflow where everyone–designers and editors–can work remotely.

Right now, we’re running ID and IC, with everyone working directly on a local server.

I’m assuming that if we all worked remotely, working directly on the server (as we do now) would be very slow. I understand how the packaging thing works, so it seems like the basic workflow would be:
1. Designer pulls the ID file off the server to work on it.
2. Designer packages ID file for IC and e-mails to editor for editor to work on it.
3. Editor works on it, then e-mails it back to the designer.
4. Designer puts it back on the server.
Is this the most sensible way to think about this?
My main worry is that the designers are the gatekeepers to the server. If they forget to put something back, no one else can get to it.
Also, what happens if an editor needs to work on a file that’s on the server? Can they pull it off the server, open it with IC, work on it, and then put it back without major repercussions? (Jason Blair, on ID Secrets, seemed to imply that he ran into trouble.)
I don’t know anything about how servers work. Perhaps the solution actually lies in how we set ours up?
Any thoughts on how this might work best would be appreciated.
Thanks.

As cool and as simple as InCopy is, I find some people have a hard time getting their head around the concepts involved in the workflow. This is a superb paper – very clearly written. Thank you!

Peter