Setup

IN THIS ARTICLE:

Determine non-email values, field mapping configurations, column order and precedence, and the layout options of your Privilege log for production.

Considerations

At the outset of a privilege log review, Lighthouse installs the PrivLog application in the target workspace, working with outside counsel and the review team to configure the following features:

Non-email normalization

This feature determines whether the authors of non-email documents are made available for names normalization. By default, they are not and the Author value is simply passed directly to the draft log. If Include Non-email Documents is selected, the Author values are directed into the Names Normalization queue along with the email From/To/CC/BCC values.

Note: Author names are not automatically included in Names Normalization because the Author value does not always represent the actual author (in contrast to the email "From" value). For example, the Author value may be "Printer123" for a number of documents. If a user were to look at the first document, an attachment to a non-privileged email, and normalize the "Printer123" value to "Ms. Not Attorney", this new value would be applied across other documents, some of which could be attached to privileged emails. As a result, it is recommended that the decision whether to normalize Author values be considered in the context of each case.

Author and date mapping

By default, the PLOG Author (for non-email documents) and PLOG Date fields are populated using the values present in the metadata fields "Author" and "DocDate". These defaults can be changed to any other field or to multiple fields. If multiple fields are mapped to one PLOG field, they will be applied in a trumping order. For example, value of Field1; if none, then value of Field2.

Nightly auto-refresh

This feature is on by default. When on, it automatically refreshes the draft log and adds any newly identified documents to the draft log overnight. Leaving this feature on is recommended for most cases. Note that this process does not take effect unless a draft privilege log is present in the Draft Log tab.

Please contact Lighthouse support if you have a specific situation that may require turning off this feature.

Seattle/NY Pods
SFO Pods

Privilege log settings

Select these options to enable Thread Participants and Non-Email Documents in the names normalization process.

Thread participants

Check this box to include thread participants. This will enable PrivLog to scan extracted text from documents in the log and identify headers from prior messages in the body of the message. Email addresses are then extracted for inclusion in the names normalization process. These names appear in the PLOG Thread Participants field in the final log.

Note: Once you turn on this feature, you cannot turn it off.

Click Yes to proceed.

Non-email documents

Check this box to include authors of non-email documents in names normalization.

Note: Once you turn on this feature, you cannot turn it off.

Click Yes to proceed.

Field mapping

Change the field mapping configuration of the PLOG Author or PLOG Date.

Map Relativity field(s) to Privilege log field

Select a privilege log field from the dropdown menu.

Click one more Relativity fields from the list provided and click Add Field.

Drag and drop the fields to set your preferred trumping order for non-email documents. PLOG Author is then populated with the first available value from these fields.

Click Save Configuration.

Clear mapping

Click the minus sign to clear mapping on selected fields.

Click Yes to proceed.

Click Save Configuration.

Privilege description

The Privilege Description is compiled using the fields from the layout and category chosen in the tab below.

Select layout

Choose a layout from the dropdown menu.

Select category

Choose a category from the dropdown menu.

Click Save Configuration.

Click Yes to proceed.

Order and precedence

Set the order of each Document Field Name to determine the Privilege Description configuration. You may create field groupings by entering the same Order value for two or more fields. For these groupings, define the trumping order using the Precedence value. PrivLog uses the first available value from grouped fields in order of Precedence.

Click in the cell to change the value.

Click Save Configuration.

Click Yes to proceed.

Click Current Description Components to view new or changed fields currently in Relativity. You may choose to update your Privilege Description using this configuration, making to sure to set your order and precedence before clicking save.

If you view a different layout / category, you can always click Saved Description Components to return to your last saved configuration.

Privilege log fields

Add, remove, edit, and change the column order of fields in your draft and final logs.

Add or remove fields

Select one or more Relativity fields to include in the log in addition to the default fields.

Click Add Field.

Check Include in Final Log to include this column in the Final Log or choose to remove a field from the log completely.

Column order

Drag and drop field rows to change the column order of the Privilege log.

Edit final log titles

Click in the cell of added fields to edit the Final Log Title.

Click Save Configuration.

Click Yes to proceed.

Production setup

Enter your main title, header title, subtitle, and footer for your final produced log. Set the Bates Prefix and number padding prior to the first production. You can preview these settings from the Draft Log screen.

Enter Title, Bates Prefix, Headers, and Footer

Production Title Editable free text field.
Privilege Bates Prefix* Pre-populated. Editable free text field.
Privilege Bates Number Padding* Use the dropdown to change the padding. Default value is 7.
Header Text - Title Pre-populated. Editable free text field.
Header Text - Subtitle Optional free text field.
Footer Optional free text field. Centered in footer.

*Bates Prefix and Number Padding cannot be edited after producing your first log.

Click Save Configuration.

Click Yes to proceed.

Back to top
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.