TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
As one example, VSS allows you to delete versions (they call it
"destroy"). This is generally a restricted administrator function. The
audit track indicates who deleted the version and when.
Here's a scenario where proper version control and version deletion go
together:
There are 15 numbered versions of a Word document. When you try to open
version 10, you instead see a notice that reads: "Version 10
accidentally included Personal Health Information (PHI) in violation of
company policy, and was therefore deleted by John Doe at 3:15 PM on
12/1/09. Version 11 is identical to Version 10, with the exclusion of
the PHI."
> -----Original Message-----
> From: McLauchlan, Kevin
> Sent: Tuesday, December 01, 2009 8:45 AM
> To: Dan Goldstein; techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: RE: New Poll Question
>
> With the latter, you don't need the former.
>
> In audited environments, one of the things the system is
> supposed to do is to ensure that versions don't get deleted.
>
> Just as with software CMS and version control, you can lock
> streams against further development, effectively orphaning
> them, but you always have the record of what was done.
>
> No matter how dumb or misguided or illegal an action or a
> document was, you should not be able to hide it.
>
> After all, at a later date, you (or your inheritors/the
> company that buys you out) want to know what you did wrong,
> as well as what you did "right" on the way to getting to the
> current state of affairs/code/documents.
>
> Revisionist history and version control/content management
> systems don't go together. :-)
>
This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. Thank you.
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Help & Manual 5: The all-in-one help authoring tool. True single- sourcing --
generate 8 different formats and as many different versions as you need
from just one project. Fast and intuitive. http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
