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.
We have used it a lot to share documents on projects, including the
check in and check out capabilities. However, Sharepoint doesn't seem to
provide as much protection or safety as other source control options, so
for things we absolutely need to archive, we use Sharepoint when we are
working on a project and then archive the document using our usual
source control tool. We have had complaints from people that Sharepoint
sometimes loses their changes, and that may just be because it works a
little differently from what they would expect. Until I got the hang of
it, and I have used several different source control tools, I also lost
changes once or twice.
I do not use it to store the source documents for my technical user
documentation, however, because of these problems. We use it for things
like design documents, requirements documents, and so on.
We also had Sharepoint recently lose a lot of information when we
upgraded it, but that was not archived documents, as far as I know. We
had modified Sharepoint so that we could use it to track our tasks,
stories, and use cases for scrums (moving these things through different
gates to show what stage they were in, etc.), and all the scrum tasks
disappeared during the upgrade, which threw our teams off really badly
for several days.
Kay R.
-----Original Message-----
From: techwr-l-bounces+kay -dot- robart=tea -dot- state -dot- tx -dot- us -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+kay -dot- robart=tea -dot- state -dot- tx -dot- us -at- lists -dot- techwr-l -dot- com]
On Behalf Of Sam Lightbourne
Sent: Thursday, February 10, 2011 2:24 PM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: SharePoint Document Libraries
Is anyone using SharePoint for a technical documentation library.
I'm probably going to be using it to house a small but growing
documentation
library.
Our company has installed SharePoint and will be using it for
collaboration
on various projects and business related activities.
SharePoint also provides versioning and check-in/check-out capabilities
that
can be useful as well.
There will also probably be a workflow created for review and approval
of
documents.
Anyone have any thoughts, comments, best practices in your experience
with
this tool.
Create and publish documentation through multiple channels with
Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as kay -dot- robart -at- tea -dot- state -dot- tx -dot- us -dot-
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
