Abstract: A system and method of dynamic search result permission checking. A system that provides end users the ability to search an index (i.e., Shinydocs Index) built from content from one or multiple source repositories, and only display results for which the user has sufficient permissions at source to view. User credentials are validated “on the fly”, such that these checks are performant across a multiple of possible back-end repositories sequentially or simultaneously. The resultant search results from the Index may be sourced from many disparate repositories, each of which have their own unique permission structure (to view individual items). A method for handling permissions in multiple repositories in a secure (yet performant) fashion in order to only display search results that the end-user is allowed to view based on source system permissions.

Abstract: A system and method for extracting full text from source files of any size in such a manner that all text can be rapidly and accurately searched via search engine while maintaining satisfactory system performance. A software tool that integrates with file shares or an enterprise content management system with the ability to merge and serialize the results of the extracted text via surrogate index files. The software tool is configured to handle text from large files in order to extract, store and access the file such that all of the text is searchable, regardless of the size of the original document in a reasonable amount of time. The Analytics Engine will omit this field during search and handle this field separately from other fields.

Abstract: In large installations of document management systems, files are often duplicated. Users may place their own copies of files in convenient locations, or for other reasons files may be unintentionally duplicated. Duplication of files causes many problems for systems reliant on document management, chiefly because the additional (identical) files accept extra storage space, and must be handled like all other files, which results in greater network and resource utilization (with a concomitant increase in processing, search and retrieval times). A tool to standardize the identification of duplicate files (based on their binary contents), as well as the identification of a primary duplicate (the original file) across multiple repositories in a manner that minimizes the time for identification is disclosed.

Abstract: A local cache content management is configured to improve the speed and reliability of access of the content management system across poor or intermittent connections. Additional techniques are used to allow document use and storage when the content management system is unavailable, and to maintain synchronization between the local cache and the content management system.

Abstract: A system and method of updating Content Server metadata on order to update and re-organize documents in a content management system (i.e., Content Server). A content management system includes a tool for setting Content Server metadata attributes, based in values in the index. Content Server Category Attributes can be set, as can Content Server Classification values, as can Content Server RM Classification values.

Abstract: A local cache content management is configured to improve the speed and reliability of access of the content management system across poor or intermittent connections. Additional techniques are used to allow document use and storage when the content management system is unavailable, and to maintain synchronization between the local cache and the content management system.

Abstract: A content management system enables a central server to connect to remote nodes at client sites. Software modules on the remote node is responsible for making necessary calls to the central server in order to create an index of the relevant data (or metadata) and fetch the appropriate binary information and files for the related metadata. Remote nodes are populated with data from the content management system via crawl/synchronize methods, or alternatively a hard drive of the data is initially configured at headquarters whereby data is saved to prevent trafficking data over a potentially unreliable connection over an extended period of time. The hard drive is then installed at the remote site and synchronized with the software module running in high performance enterprise library (HPEL) mode. The HPEL enabled server is configured to crawl and synchronize all the data and pick up differences in data using differential crawls.