Colleagues interested in the use of Sharepoint as an RM application or as a 'front end' to a 'back end' EDRMS/ECM application might be interested to having a look at the following websites:
http://www.takingaiim.com/2009/01/sharepoint-good-enough-good-for-the-economy.html
including the slide show 'Sharepoint - Truth or Fiction' and
http://www.informationarchitected.com/blog/qa-sharepoint-webinar-and-whitepaper-part-1/
Change ...'part-1' to parts 2, 3 and 4 to see all the questions and answers.
One specific question and answer that may be of interest, in part 2:
Q: What are the key functionality weaknesses that make SharePoint a weak solution for records management.
A: Two main issues. First, the records management functionality, known as the Records Center is a MOSS component and does not function in Windows SharePoint Services (WSS). Thus, right off the bat it requires further investment beyond SharePoint itself. Secondly, the Records Center is a platform, not a near-turnkey records application like that available from products such as CA, HP/Tower, Autonomy/Meridio, OpenText, IBM and EMC Documentum. Most records functionality has to be built using the toolset. There is no auto-declaration of records for example, nor rendition control or clawbacks. SharePoint provides only the most basic of records management features. Consider that MOSS Records Center is not DOD 5015 compliant out of the box, but requires a "resource kit" to make it compliant. If you attempt to download the resource kit from the Microsoft site you receive the following message:
"This additional download provides an easy way to learn about the pack while deciding if it is useful for an organization. It is not for production use. Please work with your account manager to engage a partner that has been trained on the DoD 5015.2 Resource Kit to support your DoD implementation." - enough said.
Andrew Warland
Senior Consultant
Converga (Australia)
P: +61 2 9433 7048 (from 24 November)
M: +61 413 043 934
F: +61 2 9433 7099
For any technical queries re JISC please email [log in to unmask]
For any content based queries, please email [log in to unmask]
|