SharePoint does not offer the requisite technology necessary to comply with the latest regulatory demands. It fails to be forensically sound in several areas:
It cannot search for every piece of relevant data because it does not index all critical content due to its lack of connector support. Even fundamental document types like PDF require a third party connector before they will be indexed
It enhances performance through “jump out” (process used to achieve performance by stopping search when a set number of results have been found)
It uses indexing techniques that compromise important metadata
It lacks litigation hold function that preserves data from normally scheduled or ad hoc deletion
It federates searches to different search engines, which often do not employ FRCP-compliant search methods
Specifically, SharePoint’s native search places limitations in the following areas that do not comply with FRCP requirements:
Large files not indexed: By default, the fetch will not index any single file of more then 16MB.
Files with long filenames not indexed: Filenames of over 128 characters will not be indexed.
Limited Results Sets: No query can return more than 10,000 documents.
Limited Query Length: The SharePoint search box only accepts around 200 characters. There is no wildcard search. This can be a problem for legal investigations that often involve complex queries.
Files with large word-count not fully Indexed: Any words after around the 470,000th word of a document are not indexed
Files with high-level of distinct words not indexed: Any new words after around the 18,000th distinct word in a document are not indexed.
Behavior of commas in numbers is erratic and inconsistent: If a document contains ‘30,000’ then searching for 30000 matches it. However if a document contains ‘3,000,000’ then a search for 3000000 does not.
If this post helped you, please visit the sponsors from SharePointAds.com to check the latest offerings
Subscribe