September 27, 2019 Release: New Australian production options, easy access to training, and more

Expected US release: 27 September 2019

Expected AU, CA, EU, and UK release: 4 October 2019

 

This release includes a major update to our production workflow for our Australian users, who will be able to package productions in accordance with Australian federal standards. We’ve also streamlined the production process of document families with privileged or redacted attachments for all users. Additionally, we’ve added to the list of file formats that can be uploaded to Everlaw and made scheduling a training with Everlaw staff easier than ever. Read on to find out about the new features included in this update!

 

Withholding native files for document families with redacted or privileged children

This release also includes an update to production behaviors on Everlaw. With this release, when a privileged or redacted attachment and its container or parent document are both produced, the native file of any parent documents will be automatically withheld, and only image files will be produced for these documents. This prevents the exposure of privileged or confidential information when a parent or container document is produced as a native file. (Please note that this update will only apply to documents that were processed by Everlaw.) 

To learn more about producing privileged or redacted documents in Everlaw, see this article.

 

[Everlaw Australia only] Australian production formats

We’ve simplified the production process for Australian users, who can now use the production wizard to create productions in the standard format for Australian federal court proceedings. This packaging consists of document descriptions, known as metadata in Everlaw, provided in four Microsoft Access database tables. The tables include the following: 

  • An Export table, with main document information
  • A Parties table, with people and organization information for each document
  • A Pages table, with a listing of electronic image filenames for each document
  • An Export_Extras table, with additional configurable metadata fields for each document

49_Release_Notes.gif

Files will be stored in a leveled format ([prefix > box > folder]) rather than the standard Everlaw format, in which files are divided into native, image, and text file subfolders. This format is listed as “Leveled” in the final step of the production wizard, and is set by default. You can change the format by clicking on the View/Edit button under Packaging.

This article contains additional information on Australian production formats.

 

Support for DBF files

Everlaw can now ingest dBase (.dbf) database files and display them in the Native viewer.

Check out our list of supported file types in this help article.

 

Faster overall task completion

With this release, we’ve implemented a new system to prioritize user-initiated tasks that need to happen immediately, over bigger tasks that can take more time. This update will raise overall task speed.

 

Easy training scheduling

Scheduling a free training with the Everlaw team is now easier than ever! Simply click on your homepage help icon and select “Schedule training” to be taken to our Calendly training scheduling site. This button will be visible to all users on projects not supported by an Everlaw service partner.

calendly_scheduling.gif

Annotation Data export field 

With this release, the content of your exports has been made even clearer. When exporting documents to a CSV, or when exporting to a ZIP and including document review work product, users were previously able to include a field called “Note Detail” to include information about highlights, notes, and redactions. This field has now been renamed to “Annotation Data”; while the field’s function remains unchanged, the new name reflects that the field’s content can encompass all types of document annotations. 

This article contains additional information on exporting in Everlaw.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.