Looking at InCopy for our Study Guides

16 12 2008

Given the current situation at the University, I want to see how we can continue to improve the process we started with our Study Guides. (earlier posts explain this process, including InDesign and it’s XML features to do various things).

I thought, I might as well look at InCopy.. So.. I’ve looked at it, and I’ve been thinking. It seems like a good tool for starters, I like the whole assignment based workflow idea where multiple authors can work on pieces of a document simultaneously. However. At this time I don’t see the value in adding InCopy to the study guide process and I’m going to abort my testing on it. Unless we significantly change things, it’s not going to impact or improve our workloads in any great beneficial way as far as I can see.

To get big gains on workflow we’d need to use InCopy completely instead of MS Word, and thus we would need to either:

ONE: get our real authors to use InCopy, our lecturers would then be more directly involved in their study material creation, but the downside is I’m sure they wouldn’t have time..? We would then take the designer role and manage the content and assignments – just like a real publishing house. OR;

TWO: get InDesign Server, develop a front end which lets authors edit their content without needing InCopy. This would take time, money, money and I don’t know what else! It’d be great, extensible, but we’d need to be careful and ensure that it met our real needs and improved our processes without getting carried away.

So, where to next? Who knows.

This is what I’d do if I had unlimited skills, time, and money from the University:

Look at MS Word’s XML docx format, investigate how we can effectively (automatically) transport this structured XML content in to InDesign, or generally just a more usable XML format than straight docx.

It’d be great to have a front end where the content could then be checked out for any needed updates – checked out by Authors or Designers – then at a certain date (or manually) the server does all the work.. TOCs, tagging, footers, PDFs for print and online, XML exports, web pages to display the content as well, the whole lot.

Hrm, wouldn’t that be nice.

Advertisements