Archive for May, 2010

Readers using Microsoft Internet Explorer may have noticed a difference between the “previewed document” arrows in recent posts on our clustered/related documents section (Clarify of Review & Dealing with Duplicate Emails) and what they’re actually seeing in the app.

The crux of the situation is JavaScript and rendering performance in various browsers. Internet Explorer has made some strides in IE 8 but still lags a bit behind some of the other browsers; most notably for us: Firefox and Safari.

More details on these timings at Backbase.com
y-axis is render time in milliseconds

Where Firefox and Safari are able to keep up (well enough) with repositioning the “currently previewed” document arrow, Internet Explorer has a completely unacceptable lag. We’re pretty happy with the fairly simple solution that we have in place for Internet Explorer – it doesn’t look quite as snazzy but has a much lower reliance on JavaScript and performs well.

Firefox 3.6.3

Internet Explorer 7

Nextpoint recommends upgrading to Internet Explorer 7 or Internet Explorer 8, if you are using Internet Explorer 6.

Read Full Post »

Our clustered/related documents section is crafted to keep things as simple and straightforward as possible, even when the relationships between documents get tricky.  The most convoluted situations are often the result of duplicate documents being loaded.  Normally that pain can be alleviated by detecting and removing the duplicates (you can “Request Document Deduplification” in the sidebar of your “Imports/Exports” section), but when de-duping at a sufficiently aggressive level isn’t an option – the result can be some tricky threads.

Here is an example where two copies of the email “FW: Spread sheets” have been loaded — each with the 2 spreadsheets that had been attached.

We know that we have one email “Freight Charges” that has 2 separate replies loaded into the system (the 2 copies of “FW: Spread sheets”).  Each of the duplicates is a valid document, so we need to display them “under” the email that they answer.

We flag this (hopefully unusual) situation in your dataset with a header: “Duplicate Message ID (2)” and a dotted border encompassing the duplicates and their attachments.

We always recommend (and are happy to help with) de-duping across your dataset (or a subset, like by-Custodian), but when not everything can be cleaned up — our interface shows you what you’re dealing with in as clean a way as possible.

Read Full Post »

Our review/privilege status interface will receive a bit of tightening up overnight tonight, making things more straightforward and easy to use, without sacrificing any of the power that allows you to move through a review quickly.

Let’s take a look at some conventions in the new interface via example.

Your boolean search for “discovery” has resulted in 14 documents and you are currently working with #2 of that 14.  Document #2 (an email with the subject “Defensible Discovery”) is  denoted by a gray background with a thick border in the related documents section.

The document whose preview (and “coding”, “review history”, etc) are currently displayed is denoted with a blue arrow pointed towards the preview area.  Initially, this is the same document as above (“Defensible Discovery”).

If you decide that (as part of the review of “Defensible Discovery”) you would like to take a look at it’s attachment, you may click on it to view the preview/meta.  Because you are looking at the attachment as part of your review of “Defensible Discovery” — the border/background color stay with “Defensible Discovery” while the arrow denoting the currently previewed document moves to the attachment (“Considerations & concerns”).

To take a closer look at the attachment, you can pop-it-out into a new window via it’s green arrow.  Doing this will make the attachment the focus of the new window — and thus the “related documents” will now revolve around it.  Because this document may not have been one of the 14 documents in your initial set — it will be opened in a window without that context.

To set/alter a review status or privileged status, check the boxes next to any/all of the documents that you would like to modify => choose an option from the “Review Status” or “Privileged Status” dropdown => hit “Apply”.

The status of the document(s) will be updated to reflect the change.

Read Full Post »