Re: from zero doc control to pub dates

["heidi arnold" <heidi -dot- w -dot- arnold -at- gmail -dot- com>]

someone has pointed out to me that i hijacked a thread.  i will post
this question where the topic can be addressed in the context i
intended.  so sorry.  it was intended as a question.

best,

heidi

On 9/5/07, heidi arnold <heidi -dot- w -dot- arnold -at- gmail -dot- com> wrote:
> Hello,
>
> one issue i might point out is the difference between 1) unpublished
> documents and 2) revised, released documents submitted for
> publication, and 3), published documents that have been through an
> editor.  i believe copyright law applies to all three.  so that it is
> not legal to take content from 1) or 2) without quoting and crediting
> the author.
>
> document release dates apply in all three cases, for internal
> documents as well as external documents.  version or authority control
> of the versions is the legal property of the author.  i believe in
> corporate environments this is the standard for technical documents
> with copy that is generated in-house.
>
> best,
>
> heidi
>
> On 9/5/07, Pamela Denchfield <PamelaD -at- onyx -dot- com> wrote:
> > Hello fellow techwhirlers,
> >
> > Any gotchas I should be aware of when adding publication dates to uncontrolled PDF manuals? For software manuals, are publication dates typically identical to software release dates to "avoid looking strange" to customers?
> >
> > The documentation department I belong to has historically omitted publication dates from manuals, relying on the "Date Modified" property of the PDF file to indicate this information. PDF files are delivered on software CDs and updated PDF files are posted on the customer portal page of our website. Document control version indicators are absent.
> >
> > I proposed adding publication dates to the manuals so that customers and internal folks would have another way to confirm that their manual was the latest. For one thing, if a customer prints the manual, they may not want to visit our customer portal to check the date, and they won't even have a way to confirm a match or mismatch without knowing what the differences are. (Document control is another matter for another day.)
> >
> > Today the documentation department agreed on the following practices:
> >
> > * Include the phrase "Published September 5, 2007" on the copyright page, at the bottom of the page to visually distinguish it from the "legalese" paragraphs at the top of the page (type the PDF publish date instead of using a saved-date variable). The idea of a date or other control indicator on every page was rejected.
> >
> > * If this document is for an upcoming software release, change the date to the software release date. >>I wonder if this is typical practice.
> >
> > * Do not track versions of the document as our department is still defining what constitutes a new document versus a document revision (title changes and other things being considered). For example, an "ABC User Manual" created today would say "Published September 5, 2007" and an updated "ABC User Manual" (or "ABC User Guide") created a month from now would say "Published October 5, 2007" with no indication that the document is a revision.
> >
> > * Add an action to the final output checklist to confirm the above publication date.
> >
> > Have any of you been down this road before, going "from zero document control to publication dates"? Any issues I should be aware of? Please note that I'm on the daily digest list, so send messages directly to me (in addition to the list) if you'd like a speedy reply.
> >
> > Thanks,
> > Pamela
> >
> > Pamela Denchfield
> > Sr. Technical Writer, Onyx
> > Consona CRM
> > E-mail: pamelad -at- onyx -dot- com
> > Direct: +1 (425)250-5817
> > Fax: +1 (317) 249-1942
> > Visit: www.onyx.com
> > CONFIDENTIALITY NOTICE: This e-mail and any attachments are confidential and may be protected by legal privilege or otherwise. If you have received this e-mail in error, please do not read, copy, or distribute this e-mail or any attachments, and please notify us immediately by returning it to the sender and delete this copy from your system. Thank you.
> >
> >
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > 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 heidi -dot- w -dot- arnold -at- gmail -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/heidi.w.arnold%40gmail.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.
> >
> >
>
>
> --
> www.heidiarnold.org
> www.peaceraptor.blogspot.com
>


-- 
www.heidiarnold.org
www.peaceraptor.blogspot.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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.