|
These pages provide technical information about various aspects of Catalyst CR. You will find some of this information under Policies as well.
If you have any questions regarding any of the information contained on these pages or the policy documents linked to these pages, please contact a Catalyst representative.
1. Reviewing Using Search or Dynamic Folders
When CR users review documents that have been retrieved from a search or from dynamic folders, there are circumstances which can cause the record counts to change during the review. It can cause confusion for the user who thinks that they reviewed all of the documents, when in fact, they have not.
We have created a document that fully explains the issue, why it happens, and ways to avoid it. Please click here to download it.
2. Firefox Compatibility
The latest release of Catalyst CR offers partial compatibility with the Firefox browser (a variant of the Mozilla open source project). Because Firefox is the second-most widely used browser, and works on a variety of operating systems, we felt it was important to make our software compatible to accommodate our uses who prefer this option.
To view the list of compatible features and known issues, click here.
3. Measuring Documents Per Hour
Many reviewers using CR are able to sustain review speeds of 125 to 140 documents per hour. Compared to the traditional range of 45 to 65 documents, Catalyst may double the speed of your review. To learn more about how we measure documents per hour, click on this link.
4. About Indexing HTML Documents
We index HTML files natively but assume that all HTML is properly formatted. In most cases this does not present an issue but it can present an issue when processing systems do not properly escape special characters like angle brackets (). If special characters like angle brackets are not properly encoded, our indexer will treat them as formatting tags and will ignore the content inside the brackets. The content will not display on the HTML page either.
Some email systems, including Notes, will sometimes enclose content in angle brackets. Please make sure this content is processed properly so that data within the angle brackets will be indexed if appropriate. Either remove the brackets or use standard HTML tags for them, such as > or <.
We do not check the content we load for these kinds of issues unless special arrangements are made.
5. Bulk Updates in CR
CR allows administrators and others given appropriate rights the ability to batch or bulk update multiple records. Requests involving less than 5,000 records run automatically.
If the request involves more than 5,000 records, then it will be forwarded to Application Support for approval and scheduling. The request may be run that night rather than in the day.
Why schedule the request? Simply because updating massive amounts of information can lock records and use SQL resources that are being shared across many users. If we feel the request might cause conflicts wth active users, we reserve the right to schedule the update at a more convenient time.
You can always discuss this issue with your Project Manager. Most bulk updates are scheduled and run promptly after being requested.
6. Highlights in CR
Catalyst CR will highlight search hits from the body of documents rendered in PDF or HTML. PDF highlights are shown when viewing documents using Acrobat or the Acrobat Reader. All you need do to see the highlights is click on the Highlights link.
HTML highlights are rendered on native files and emails viewed in the HTML Preview mode or for emails rendered in HTML.
We limit hit highlighting to the first 20 search terms submitted. We do this because calculating highlight coordinates for more than 20 search terms is processor intensive and might slow down display performance. In addition, when clients run massive text searches with thousands of search terms, our experience is that they don't want to wait additional time for highlights to render.
The 20-term limit includes search terms added by an administrator for special consideration. If the search has more than 20 text-based search terms, then administrative highlights will not be displays.
Please contact your Catalyst Project Manager for more information on this functionality.
7. About Time Zone Displays in Email Messages
Time zones present an interesting challenge for electronic discovery. Outlook, by default, will convert time displays in a message to your local time zone. Thus, if you are on Pacific Time and open an email sent to you at 11AM Eastern Time, it will show the email as being sent at 8AM. That is because the time is translated to Pacific time. Conversely, if you respond at 8:15 PT, your recipient on the East Coast will see it as being sent at 11:15.
Catalyst CR provides several options for viewing email files. If the file is converted to HTML during processing, the time will typically display in the local time zone where the file was processed. If the file is not pre-converted and is loaded into CR as a MSG file, we will render it to HTML on the fly. In that case the time will be converted to Mountain Time, because that is where our servers are located. If you happen to open the MSG file itself, the time will then be converted to your local time zone.
When we process files for you, we offer the option of selecting a base time zone for that processing. If you want to convert all messages to Eastern Time we can do that. Likewise for Pacific or Greenwich Mean Time. At the least, this will provide one consistent time zone for your messages. However, we can't change the time zone when you open the native file. Outlook will convert the message to your local time zone. This means that the sent time will be different dependng if it is opened on the East coast or the West.
8. Adobe Acrobat Version 9
On July 1, 2008, Adobe released version 9 of its Acrobat product line, which includes two paid versions of the product and the free Acrobat Reader. This is an important development for users reviewing Acrobat files. Version 9 changed and substantially improved how Acrobat interacts with Internet Explorer. As a result, the frustrating crashes in Internet Explorer that users sometimes experienced seem to have stopped.
Past versions of Acrobat could have memory conflicts with IE depending on what options were chosen and how the produtions were installed. This caused problems for users who were trying to review large numbers of PDF files.
We worked with Adobe on the beta versions of Acrobat 9 and helped guide them as they changed their approach to memory management. As a result, Acrobat now seems crash free when used as plug-in to Internet Explorer. This means users won't be forced to reboot or re-open their browsers when Acrobat/IE fails.
We are excited at the release of Acrobat 9 and recommend that all users upgrade to this version when possible. If not, click here to view troubleshooting tips for dealing with earlier versions of Acrobat.
|