Found a nice description of top Content Management Sites http://aiim.typepad.com/aiim_blog/2009/03/just-the-facts-please-top-content-management-sites.html
All are really good, except … where I can’t find the way to subscribe on RSS updates. It’s a bit awkward – the site is about Information Management and e-Discovery, but no way to find the connections to the information.
Some sites publish information in the aspects of SharePoint.
Some interesting facts about ECM systems:
- only 18% percent of ECM projects ever make it into full production
- for every “current” document in an Exchange Server or on a file share, there are 14 other older, legacy documents in PST files, laptop hard drives, local archives, etc
- The average user creates or receives between 100 to 300 electronic documents per day
- if classification process requires five seconds or longer (including referring to the schedule) end-users will ignore request to classify
Thanks to Dario Mratovich, Microsoft Consultant, for his awesome recommendations of preparing the testing data. Citing the section from his “Capacity Planning Testing for SharePoint 2007”
Make sure you have adequate sample data. This tends to be a very common stumbling block – sites are built with only a tiny percentage of content that production will have. Not enough sites, not enough content, not exercising a broad enough sampling of your dataset, not enough users – these can all fatally influence your test results.
Another common problem is having enough content for a reasonable search corpus. What many people try doing is uploading the same document many times – sometimes hundreds or thousands of times – and think that if it has a different file name then it will be okay. Unfortunately in that scenario the search duplicate process can start taking significantly longer than it otherwise normally would, so this too can unfairly reduce your query throughput.
A document that is uploaded multiple times will affect the way that SharePoint performs duplicate detection: where SharePoint’s search calculates a hash based on the contents of a document – it doesn’t look at the filename! So uploading a document 30,000, even with a different filename, will cause the search retrieval to become slower and slower as SharePoint tries to resolve duplicate documents.
You will need tools in all likelihood to populate sample data. Some tools you can start with are on CodePlex at http://www.codeplex.com/sptdatapop. You will probably end up writing additional tools for other data population tasks, or possibly to work in combination with these tools.
Using PowerShell for scripting the creating of objects and data for testing is also very useful.
Michael Porter and Alan Weintraub published really good article regarding four pillars of collaboration project.
When looking to implement a collaboration project, it is critical to understand that there are four pillars and that a single pillar alone will not address the requirements of your project. These four pillars are - Messaging, Real Time Collaboration, Team Collaboration, and Social Networking. In you projectss you often take capabilities from multiple pillars to address all of your needs.
- Messaging: enables teams and individuals to communicate in a formal, auditable manner.
- Real Time Collaboration: focused on ad-hoc communications providing capability to initiat a real-time conversation between one or more individuals
- Team Collaboration: provides the content management services that collect, store, and manage the documents that are pertinent to the team’s activity.
- Social Networking: provides a way for teams and individuals to share knowledge not only within the team, but to be able to reach out to an extended group for their input and feedback
Will be presenting on Moscow SharePoint UG in Russia this September 14th, about "SharePoint Farm Deployment and Configuration - Recommendations"
This is the third version of my whitepaper I was working on this year. In this session I will put attention on farm optimization and provide guidelines how to indentify the right values for the SQL Server settings and Farm Size settings in terms of RPS (requiest per seconds).
Registration is necessary. More details are there http://sharepoint.su/Lists/Posts/Post.aspx?ID=22 (on russian). The place is the same - Microsoft office in Krylatskoe.
Traditional Enterprise Content Management (ECM) solutions are characterized by number of factors, such as cross-team collaborations and document management. Most of them are aligned with the SharePoint functionality, but unfortunately, in most cases, SharePoint does not prove to be a solution that can meet all of the organization’s ECM requirements.
In this post I'd like to start collecting the scenarios that hits the SharePoint architecture design limits and lack of functionality on the way to meet ECM requirements. If you know more scenarios, please share via comments.
Requirement 1: Large ECM scenarios can require to store millions documents in the single folder or document repository, including deep, nested folding structure to accommodate all of the organization’s documents.
Issue: SharePoint 2007 has limitation of sub-folders support, number of documents stored in list libraries, crawling limitations and etc.
- SharePoint 2010 solves such issues, and you can store millions items in folders and subfolders without impact on quering data, rendering and search
- "ECM systems" product, because there is no OOTB support in SharePoint. We can emulate sub-folders using meta-data and customizing views, but nothing helps us to have millions items per library, because performance will degrade drastically on showing thousands documents, not millions.
Requirement 2: Certified state of record management system. Government and military organizations requires the standard and classified record management compliance with U.S. government's DOD 5015.2 certification.
Issue: SharePoint 2007 doesn't support classified records compliance (for DOD 5015.2 Chapter 4).
Solution: "ECM systems" product, because there is only general records support. Chapter 2 via The DOD 5015.2 Resource Kit in SharePoint.
Requirement 3: Sites and document repository need to be classified, encrypted and archived
Issue: List item limitations hinders the capabilities of Record Center feature of MOSS, and no support for reviewing archived content and restoring sites from archive.
Solution: n/a, albeit "OpenText ECM Suite" tool provides some features enhancing search and archiving functionality of Record Center.
Requirement 4: Ability to render, search and manipulate print streams such as AFP, Xerox Metacode formats, PCL
Issue: SharePoint supports rendering the mainstream formants only, such as as PDF, Office documents and etc.
Solution: n/a. Custom solution, based on the print stream converters (Crawford and others)
Requirement 5: Ability to collaborate without bounds
Issue: SharePoint 2007 and SharePoint 2010 collaboration is limited to site collections. Albeit SharePoint 2010 provides additional features to Collaboration scenarios, it still can't solve cross-collections collaboration issue.
Solution: n/a due to architectural design, albeit you can use 3rd part components to achive some collaborations , 
Update: According to Forrester Research, only 18% percent of ECM projects ever make it into full production (a moment to point out the obvious: 82% do NOT reach full production). Mark Diamond published 5 reasons when ECM may never be deployed
They pointed 3 critical aspects when developing document management for SharePoint:
- Create taxonomy, first describing the high-level content type and associated attributes that the other content types can inherit from
- Define the Information Architecture; this is the layouts for the sites, document libraries, and document folders. This is critical as SharePoint has some performance limitations that need to be considered during the design phase
- Develop a governance plan that addresses content ownership, process, and security rights
These steps should be a part of your SharePoint project documentation