Feeds:
Posts
Comments

Archive for the ‘Discovery Cloud’ Category

Electronic redaction in DiscoveryCloud is not only more failsafe than it’s “magic marker” counterpart – it saves time in the process.  It’s that same “failsafe” requirement that makes proper auditing a bit tricky — make the redaction permanent… except when it’s necessary to see what was under there in the first place.  Newly available to DiscoveryCloud is a feature that does just that — making auditing available users who themselves have the authority to redact.

Documents that have redactions made in DiscoveryCloud will have an additional icon in their “Viewer Tools” section.

post-red-1

A view of the document pre-redaction will be temporarily displayed.  The version of the document available for (normal) export / production is not effected by using this audit mode.  Navigating away from the document will not leave the setting on.  Likewise, any other users viewing the document at the same time would see the redacted copy.

post-un-1

Checks & balances are in place to prevent production of unredacted images remain in place, ensuring that those copies are provided only when explicitly requested.  We hope this feature comes in handy and makes the process of auditing redactions simple and straightforward.

Read Full Post »

Transmitting images utilizing Privilege Protect (or exporting) is a common use case, but some filetypes just don’t have a logical image:  What does a pst “look like”?  To account for this issue, a “placeholder” image can be employed to fill a spot – providing the ability to have something indicating that there is a native file that does not have images available.

Placeholders may be assigned as part of a Bulk Action:

bulkplaceholders

In DiscoveryCloud, placeholders may also be assigned as part of Bates number assignment/stamping:

placeholderbates

This functionality will make bates application – and more importantly: production itself – a more consistent process.  The functionality is available immediately in Discovery Cloud and Trial Cloud.

Read Full Post »

Several small/medium enhancements have been made available over the last couple of weeks.  This is not a complete list, but we’d like to highlight a few:

Deposition Summary Report

Available in TrialCloud, this feature provides a high level overview of what is currently loaded.  It’s quite handy when conducting a “what are we missing” audit following extensive uploading.
deporeport

“Responsive w/o Issues” Filter

Available in DiscoveryCloud, this handy feature helps you isolate documents that have been flagged as responsive but are potentially missing a reason code.
noissue

Copy Export to S3 Folder

Downloading large files via the browser can be inconvenient.  Moving them to a location where you can utilize a more robust upload/download tool can simplify the process.

snipexport

 Rotate Ranges of Document Images

Rotating pages individually can be a hassle when an entire document came in sideways.  Move several at once by providing a range.

rotaterange

Each of these features is already available and active in your Nextpoint application instance.

Read Full Post »

One feature of our recent Review Metrics release is the ability to keep closer tabs on your review at the Reviewer level.  One (optional) tool in your set is the ability to track time for the purposes of calculating documents per hour reviewed.

A Reviewer may clock themselves in/out with the click of a button on their landing page.

clock in

 

If time was logged incorrectly, spent outside the system, or just plain forgotten: edits and full entries may be modified via the calendar interface (accessed via the “view” link in the screenshot above).

calendar

 

Advanced users may manage their own time entries or do the same for other users:

chgcaluser

 

The focus of Time Keeping is the documents-per-hour metric and does not aim to be a fully featured time management system.  In that name, the system is flexible and does not provide locking, security, and audits that might appear in a true time-tracking tool.  However, reports detailing the work done in a given day or month, by any given Reviewer, are available to advanced users — providing direct timestamps at which documents were reviewed.

tlog

 

We hope you’ll find this change and the wider release that it is part of helpful in gaining visibility into the status of your review.

Read Full Post »

We’re excited to bring a significant refresh to the Discovery Cloud experience.  The updates add clarity to your review at the Reviewer and Subreview levels and provide visibility into where progress is being made or where it may be lacking.  The ability to more clearly differentiate between documents that are not yet reviewed for privilege and those that have been positively identified as “not privileged” facilitates privilege review in a way that was previously inconvenient.

 

Subreview Metrics

Available to Advanced-level users, a tab under “Admin” brings you status and counts at the Subreview level.

substat

Subreview level statistics illustrate progress and may provide insight on what area of your review is producing the highest quantity of relevant/privileged/etc documents.  Many graphs may be clicked to gain an extra level of detail.

 

Reviewer Metrics

Available to Advanced-level users, a tab under “Admin” brings you status and counts at the Reviewer level.

reviewstat

Statistics for each Reviewer provide visibility on what sort of work is being accomplished.  If you elect to utilize the (new) Timekeeper functionality, a time metric is also available to give an indicator of review speed.  As with Subreview Metrics, many graphs may be clicked to gain an extra level of detail.

 

Reporting

Available via Settings -> Metrics Reports, users may opt-in to status emails.  A report will be generated and transmitted weekly, providing the recipient with the overall +/- subreview status of the review.  These emails do not need to be tied to a Nextpoint account, freeing you up to transmit them to addresses of those not necessarily involved in the day-to-day review.

reportsign

 

Independent Privilege and Relevancy Review

Previously known as “Review Status”, “Relevancy Status” is concentrated on the relevant/not portion of a review.  On the Privilege side, this enables differentiation between a document that is “not reviewed for privilege” and a document that has been reviewed for privilege and certified to truly be “not privileged”.

Existing documents with a “Not Privileged” status have been marked as “Not Reviewed” for privilege.  If you would prefer that those documents instead be “Not Privileged” – a simple bulk edit is all that is necessary to make that modification en masse.

 

So, when do I get it?

The update will be available to some users beginning Tuesday 3/19, with the remainder receiving the updates Thursday, 3/21.  As with all updates, no action is necessary on your end.

Read Full Post »

“Date” type Custom Fields have been added to DiscoveryCloud and TrialCloud, expanding on the set of field types already available:

date-cf

A helpful date-picker widget is made available when you need to edit values via the application:

click-for-widget

Values continue to be stored as alpha-numeric behind the scenes, but with the assistance of this tool: they are formatted in the easily searchable YYYY-MM-DD HH:MM:SS format.  This will alleviate current issues with searching when some date formats vary.

When populating the field via loadfile, values will be coerced into this format wherever possible (any valid date format).  Values that cannot be sorted out (ie. if “hello” was provided as a value) will be saved as is.

We hope you enjoy this new feature available immediately in DiscoveryCloud and TrialCloud.

Read Full Post »

Importing email from an external mail server saves you time normally spent creating, exporting, and uploading mailbox files.  Enter your email configuration and credentials (similar to any email client) and you’re on your way to importing all mail available in the mailbox.

mail-tight

Following authentication, all emails and attachments provided by the external server will be imported similar to normal “batch” processing.  Relationships between emails and attachments will be established and the documents will be imaged as normal.

This feature is immediately available to all users of Trial Cloud and Discovery Cloud.

Read Full Post »

The following features are available immediately in TrialCloud and DiscoveryCloud instances.

 

Image Placeholders

When producing files that are only available as natives, it is handy to have a placeholder — something that can be bates stamped or even just “holds a spot” in the stack of paper following printing.  To fill this need, we will now add a boilerplate image (at initial processing time) when we would otherwise not have anything to display/produce.

 

 

The placeholders will be inserted for new processing requests and are not available retroactively.  The keys are in your hands as far as keeping/removing these images after processing completes and documents that are in this boat may be located via a filter for “Unsupported Filetypes Only”.

 

Working with Processing Messages

Another feature now available is the ability to remove individual error/warning messages following batch processing.

 

 

This is in addition to the ability to resolve ALL messages in 1 motion.  Removing the messages is permanent and should only be done when you are sure that the issue has been resolved adequately.

We hope you enjoy these new features!

Read Full Post »

Nextpoint’s TrialCloud and DiscoveryCloud software now supports importing files directly from EnCase evidence files (E01) and Apple Disk Images (dmg) for all common disk formats — Windows XP, Windows 7, and Mac OS X.

On the import screen, you’ll now find a Disk Image import type, enabled when a valid disk image file has been selected from your S3 folder. These may be single files or multiple split-image files contained in a zip. When this option is used, the uploaded hard drive will be extracted in place and the files it contains will be imported directly from the image as though they’d been opened and imported separately.

Disk Image Upload

At import time, a specific set of files and directories to import may be defined in order to narrow the scope of the uploaded data and avoid processing large amounts of uninteresting documents. Additionally, for disk formats that support it, you may choose to include or exclude system files (those bundled with the operating system itself rather than created by a user, potentially uninteresting during review) and hidden files (most often application preferences and filesystem metadata).

These options, in combination with our DeNIST file filtering feature, allow you to focus in on the important documents from your collected evidence files quickly and easily.

Read Full Post »

Document search results are normally displayed by one of two means: (1) Relevance – The document matches your search criteria, but how does it “score” compared to other documents that match? (2) Order that you explicitly specified.  In many situations, this makes the most sense, but sometimes you want to view document families (i.e. email’s with their attachments) together.  One way that we provide this capability is via “Group document families” (on the “Documents” page for TrialCloud; “Review” page for DiscoveryCloud).  Selecting this option will group members of the same family together in the search results.

Central to understanding the feature is an understanding of how Nextpoint defines a “document family”.  While we believe that an email and it’s attachment are two separate but highly-related documents… we also believe that for features such as de-duplification it’s important to have knowledge of the context of an individual document.  Therefore, a document’s “family” is considered to be anything that would typically be expected to be transmitted in a “single package”.  For example, an email physically contains the bytes necessary to piece together an attached file — they’re “in a family”.  A zip file contains the bytes necessary to re-assemble it’s contents: they’re in a family.  A reply to an email does not contain all of the bytes necessary to recreate a true representation of the email it replies to: they’re not in a family.

Are two identical documents considered to be “in a family”?  Only if their entire family’s are identical.  This most frequently happens when the same document is uploaded multiple-times by-itself , although it will also occur when the exact same email file (with an attached document) is uploaded more than once.  Note: Each of these situations is blocked if deduplification is enabled.

The results of the search display document families grouped together and separated by white space.  In this example, 2 families are shown: each comprised of a single email and their single attachment.

This feature does not pull any documents into your results that did not match your query, but instead does exactly what is promised: group the results of your search.  For example, a hit in an attached Word document would not lead to the Email that attaches it being included in the set, unless the email itself also matched the search criteria.  Should you require the capability to pull in related (non-matching) documents, options are available via “Bulk Actions” to accomplish that goal.

Similar to any other sorting option with document search:  The order documents are displayed on screen may be relied on to be the same order than any Bulk Actions (including Bates Assignment, etc) will be carried out.

Read Full Post »

Older Posts »

Follow

Get every new post delivered to your Inbox.