OK, I’m a little behind the news on this but Google has now finally released Urchin 6.5. Google bought Urchin a few years back and reused some of that technology in the Google Analytics suite. Google Analytics is fine as long as your in the public space but just doesn’t work for intranets and “behind the firewall” knowledgebases.
A problem with cloud computing, what happens if your private documents are shared with people without your permission. Admission from Google that this has now happened with their services.
http://www.realsoftwaredevelopment.com/google-shares-your-private-documents/
http://www.cio.com/article/389613/Three_Things_the_CIA_Learned_About_Implementing_an_Enterprise_Wiki?page=1
I’d imagine the CIA is extremely sensitive about information published to a Wiki so its good to see what they see as important.
The 3 items:
Issues like leaking of corporate secrets, confidentiality, liable, etc with the Enterprise Wiki.
“Companies need to be alert to the dangers that free comment made in wikis and blogs may be libellous or infringe employee rights laws.” - Crispin O’Brien, KPMG’s head of technology
The KPMG press release: http://www.kpmg.co.uk/news/detail.cfm?pr=2898
Article is http://www.socialmediatoday.com/SMC/13450
http://www.e2oh.com/2008/03/02/a-banana/ is an interesting article on the pitfalls and best practice from implementation of an enterprise wiki.
Items like “painting lines on the road” are important but equally not styming uptake with overly agressive security models, excessive taxonomy, and extreme management styles.
http://distributedresearch.net/wiki/index.php/Wiki_facilitation is practical on the process of facilitating wiki contribution. Simple concepts like not creating a full skeleton of blank pages for the wiki but rather concentrate effort on small content centres.
Now, New, Next