RE: Image repository

Subject: RE: Image repository
From: "Hemstreet, Deborah" <DHemstreet -at- kaydon -dot- com>
To: <john -at- garisons -dot- com>
Date: Tue, 22 Jul 2008 09:08:19 -0400

Hi John,

There are a few ways you can do this. The real problem will be getting
the cooperation of the other people to make it work.

I had to control the graphics for all of my documents, but many people
wanted to use them. In addition, they engineers had documents with
graphics that often needed to be redone since they were drawn in Word.
The minute I applied the corporate template to their documents, the
formatting when all haywire (of course).

(Note: if you have a content management system - this all becomes very
easy. But if you have to work manually, this solution MAY work).

Here is how I handled them:


1. Manuals: A subdirectory to the main manual, called "figures". Under
figures, a subdirectory called "originals". All SOURCE files, such as
PPT, visio, whatever, were stored in originals. The files in the main
"figures" directory were all stored there. The Word document Link+Embed
to those documents. Thus, no matter where the full directory moved,
links remained solid, and as long as no one updated a document, I could
send it for review, keeping figures intact.

2. Other employees: 1) training how to make their graphics outside of
Word, and how to use Paste>Special to embed as an Enhanced Metafile
(linking usually did not work with these documents because of the way
they were stored on our network). 2) Train employees on how to resize
documents and what to look for. 3) Provide a network directory where all
critical graphics were stored by category (the employees loved this); 4)
Provide a shared folder in the graphics network directory where
employees could dump all graphics they wanted to be sure were not lost.
In this case, I always asked them to make a folder with their name, and
subfolders that categorized the graphics by topic or document number.

3. Critical graphics should be controlled. We did this via document
control - for example, manual coveres, CD labels, etc. These were all
given numbers and had to be signed off. This way they could be stored
and were retreiveable. Again, we made sure to save the SOURCE file (for
example .pst) as well as the final distribution file (for example,
*.png). Naming, in this case, was usually DocNumber_Description.fileType
(example: UG-10-3333-A_OrtaCDLabelV6.png).

The main thing is to come up with a system that makes sense to your work
situation and which will be as user-friendly as possible to the people
who must live with this system. Don't forget, to make whatever system
you implement work, you will need to train people, remind them why this
is important, and probably nurse a few people through the how-tos until
the system is running smoothly.

I hope this is helpful.

Deborah


-----Original Message-----
From: techwr-l-bounces+dhemstreet=kaydon -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+dhemstreet=kaydon -dot- com -at- lists -dot- techwr-l -dot- com] On
Behalf Of john -at- garisons -dot- com
Sent: Monday, July 21, 2008 1:34 PM
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Image repository

Hi All,

I'm in a new position and I've been given the hot potato of coming up
with
a way to manage the images that are used in documents and specs.

People create images in a variety of ways - PowerPoint (!) being the
primary tool - and are then converted to WMF and included in documents
using references (rather than embedding them).

So ... what do you recommend to:

- number or otherwise identify graphics?

- control look & feel issues - color, size, line style & weight, etc.?

- associate final format with original version?


Thanks!

John G

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create HTML or Microsoft Word content and convert to Help file formats
or
printed documentation. Features include support for Windows Vista & 2007

Microsoft Office, team authoring, plus more.
http://www.DocToHelp.com/TechwrlList

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com

---
You are currently subscribed to TECHWR-L as dhemstreet -at- kaydon -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit
http://lists.techwr-l.com/mailman/options/techwr-l/dhemstreet%40kaydon.c
om


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/ for more resources and info.




^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more.
http://www.DocToHelp.com/TechwrlList

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/ for more resources and info.


Previous by Author: RE: Value of basic computer science qualification?
Next by Author: RE: Setting up acronyms > and moving more to philosophy of such...
Previous by Thread: RE: Copyright verbiage for PDF manual
Next by Thread: RE: Image repository


What this post helpful? Share it with friends and colleagues:


Sponsored Ads