atw: Re: Sharepoint user docs wiki

Bob - The intranet model is what I am currently using. I like the simplicity
of the concept, but the reality of it here has me tearing my hair out. A
minor point is that the approval process to get a new version of a doc
posted takes in excess of 3 weeks on a good day, by which point we have
already already moved on to the next code drop and am scrambling to document
that in all its flavours for the multiple user groups. No, I can't have
Flare either. I do it all the old-fashioned way.

Chris - Will investigate Plone. We are also looking at Confluence, but
haven't engaged them in the same process as we have for SP. We are up to
Office 2003 but I don't see 07 in our future. So we will miss out on some
neat features as a result, or worse, run into the problems you discussed. We
do have a MS bias, however we are about to launch the deluxe TRIM Context so
to me, alot of the document-oriented features of SP are redundant. They
aren't keen on replacing the intranet with SP, which is a shame as that
would be something useful. I think they just want the project work space
aspect of SP and I probably won't end up with anything out of it.

2008/12/10 Chris lofting <lofting@xxxxxxxxxxxxxx>

> See the open source equivalents such as Plone - http://plone.org - there
> are
> others but plone is REALLY easy to install on laptops/desktops etc and
> allows for a lot of customisation.
>
> Sharepoint 2007 comes with the usual MS issues re compliance to 'standards'
> (it used MHTML to customise HTML for enclosure in the DB etc - and it
> covers
> MS version of XML that is 95% 'standard'! - why the hell they did not go
> the
> full 100% is a worry) - if you are an MS shop and have MSWord in its 2003
> premium version (not small business) or later then it has some nice
> capabilities in document management, group sharing etc etc (uses XML
> features). IOW to get the full benefits of MSOffice operating in sharepoint
> you need to upgrade MSOffice to AT LEAST 2003 Premium version or go all the
> way into 2007 etc - then come issues with dropping of data etc that can
> happen if you create a hybrid environment that allows for 2003-2007
> transfers where going 2007-2003 can be an issue in some cases. IOW if
> management don't want to update their laptops with current MSOffice/Vista
> there can be issues in editing on one system and transferring to the other,
> editing there and then going back (and so more backward compatibility
> issues). THEN comes issues of existing archives files that MAY need
> upgrading and so need to be considered re possible update issues (I.e. they
> get stored back in the archive but are then retrieved by an older MSWord
> system (2002-2003) etc etc)
>
> The hierarchy has to be managed VERY carefully - and you need a dedicated
> sharepoint administrator to take care of it all (and that covers 'garbage'
> collection etc with variations on version control rules - there are LOTS of
> tables to fill in for the initial planning/configuring the use of the
> system
> and its management - it is not a "fire-up and forget" product)
>
> All of that said, my last exposure was two years ago (beta 2007 etc) so
> perhaps some issues were fixed!? (something tells me - "doubtful"!)
>
> The wiki-like features of plone are easier to deal with and more 'in tune'
> with open source users (developers etc) - Sharepoint can be overkill. SO -
> if your a rigidly MS focused shop then the logical path is to introduce
> sharepoint. Otherwise at least review Plone (or other CMS open source
> systems).
>
> Plone on laptops needs to get into the ability to seek-out other plones on
> a
> network and link-up to form a transparent interface and present as if 'one'
> plone. I dont know if this exists now or is planned-for but something
> useful
> to have - whereas sharepoint on a laptop? not a good idea! - and there are
> issues with virtual system setups, have to be carefully managed as if one
> goes down then all others go as well - this gets into server costs and so
> dedication of resources or use virtual capabilities etc etc etc - all part
> of the planning stage filling in all of those tables!
>
> have fun!
>
> Chris.
>
> > -----Original Message-----
> > From: austechwriter-bounce@xxxxxxxxxxxxx
> > [mailto:austechwriter-bounce@xxxxxxxxxxxxx] On Behalf Of
> > Jasmine Andrews
> > Sent: Wednesday, 10 December 2008 3:37 PM
> > To: austechwriter@xxxxxxxxxxxxx
> > Subject: atw: Sharepoint user docs wiki
> >
> > Hello
> >
> > My organisation (state govt) is considering implementing
> > Sharepoint and I've been dragged in for the requirements
> > gathering process. In a previous life, I attempted to
> > demonstrate Sharepoint's suitability as a means of handling
> > training administration without tears, but am now more
> > interested in its wiki for user documentation, discussion
> > forums for user groups etc.
> >
> > Does anyone have any experience with this application of
> > Sharepoint and want to a) knock some sense into me, b) give
> > me some good news stories to encourage me to proceed.  I have
> > enough on my plate as it is and am trying to quickly evaluate
> > whether I should continue my involvement with this project or
> > not. Any war stories would be greatly appreciated.
> >
> > Jasmine
> >
>
>
>  **************************************************
> To view the austechwriter archives, go to
> www.freelists.org/archives/austechwriter
>
> To unsubscribe, send a message to austechwriter-request@xxxxxxxxxxxxx with
> "unsubscribe" in the Subject field (without quotes).
>
> To manage your subscription (e.g., set and unset DIGEST and VACATION modes)
> go to www.freelists.org/list/austechwriter
>
> To contact the list administrator, send a message to
> austechwriter-admins@xxxxxxxxxxxxx
> **************************************************
>

Other related posts: