Archive for the ‘Cloud’ Category

At Nextpoint, we understand that it is crucial for eDiscovery and litigation tools to be as fast and cost-effective as possible. To that end, we periodically introduce a major enhancements, like our review metrics designed to help you track and monitor the progress of your review. But we are also continually tweaking our interface in response to customer requests to make sure it works the way they do.

Today, we’re proud to introduce a new and improved Grid View, our streamlined interface for browsing your documents. We have already introduced a number of new features in Gridview making it more customizable. Now we have even more resizing options, including a new feature to save the custom views for individual reviewers.

In the past, a reviewer might resize their grid view to allow them to quickly scan the information most important to them. Now, those changes are automatically saved, so that each reviewer can preserve their custom column widths and other choices as they move through their review. It’s just one small way we’re trying to help reviewers quickly scan and precess information they need for a case.

For example, in the Grid View layout above, users can choose to change, resize and manipulate any of the columns, a process which is now smoother than ever. In addition, all of our Nextpoint applications will remember those choices and display the same column widths and layout on every page of search results that reviewer looks at. As always, comments and feedback are highly welcomed and encouraged. Feel free to email us at thelab atsymbol nextpoint dot com.

Sometimes long bits of text are annoying – you want them stored but you don’t want them taking up valuable screen space… but sometimes those long bits of text are important and justify expanding the view to make them always viewable in their entirety. For the second scenario, we’ve recently introduced the “paragraph” custom field type.

With “Paragraph” the input blank expands as you type, exposing any text that you’re entering automatically.

The text will display, in it’s entirety, when other users/reviewers visit as well, providing a way to share notes or longer values that justify the real estate without the need to scroll +/- copy/paste.

Since the launching of “Gridview”, it has quickly become the most popular format for viewing documents in Trial Cloud and Discover Cloud. Shortly thereafter, we started offering some customization which also became quite popular and is leveraged in almost every Trial Cloud and Discovery Cloud instance.

Another enhancement has now been introduced, allowing you to view values that are a bit too long for the standard column widths. Here a portion of the “Author” field is not viewable by default:

Dragging to extend the column, we can now see the full value:

A simple change to make things a bit easier when sorting through the list of values brought back from a search. Enjoy!

LinkedIn has recently made modifications to their authentication system requiring users to re-authenticate every 60 days. Expiring access in this way is generally done to circumvent situations where a 3rd party was granted permission long ago and you haven’t gotten around to barring them access to your data.

To re-authenticate, click “Settings” on your LinkedIn feed, then select your authentication method as pictured here. (the email option is typically intended be used only for getting a link to someone who does not have access to CloudPreservation)

As the feed’s owner, you will be notified again when the authorization period is expiring. Failure to (re)grant that permission will result in CloudPreservation no longer being able to obtain/capture your data from LinkedIn. As always, the actual authentication involves CloudPreservation sending you to a LinkedIn server to provide your credentials and grant the permission. CloudPreservation will never obtain or store your personal LinkedIn password.

As an instance admin for CP, keeping track of your user’s crawl authorization statuses can be tricky. Notifications are sent to the user to let them know the social media site requires them to provide re-authorization, but if they don’t take action… you need to know to get on their case! In order to alleviate this issue we have added a new field to CP cases:

A look at the new changes in the CP tab under account management

This field is available under the CP tab in “Manage account”. The list takes a group of comma separated emails of whom you want to be notified whenever authorizations or reauthorizations are needed. This makes the process more visible and you won’t have to mentally remember to remind Bob down the hall he needs to reauthorize his twitter crawl. The field can be either set at the same time the instance is made or later modified at any time from the CP tab using the “Modify Repository” utility.

The BCC field can be changed at any time from the Modify Repository tool.

The other new CC function is small, but helpful. When either uploading a new file or a new version of a file in TC you can now CC yourself alongside the users you want to notify. This will help you better keep up on TC file changes. The recipient list will be included in the message delivered to each user, allowing an easier audit of who received the notification.

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.

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.

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.

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:

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

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.