Miami User Group. Threading Workflows and Discussion. kcura LLC. All rights reserved.

Size: px

Start display at page:

Dylan McCarthy
5 years ago
Views:

1 Miami User Group Threading Workflows and Discussion

2 Threading

3 Structured analytics set

4 Saved searches 1. Parent s in document set Parent s only From: is set AND Parent Doc ID: is not set 2. Document set to analyze Parent s and their attachments Document is in: Parent s Includes Family Exclude docs with more than 30 MB text

5 Fields for mapping

6 Analytics profile

7 header fields From To CC BCC Subject Date Sent Date and time

8 metadata fields Attachment name Only populate for attachments File name and extension of the document

9 metadata fields Conversation ID Microsoft Conversation index number Recommended to use if present Inaccurate data in this field will cause problems with results Group ID Used for the Threading Display field

10 metadata fields Parent Document ID Document identifier of parent Only needed for attachments

Email threading results Inclusive Email The indicator of whether this email is

11 threading results Inclusive The indicator of whether this is inclusive. Inclusive Reason This field lists the reason(s) that the message was marked inclusive.

12 Common inclusive reasons 1. The last in a thread 2. Attachments that are dropped 3. Change of text

13 threading results Thread Group The thread - all of the replies, forwards, and attachments following from an initial sent . Threading ID Indicates which conversation an belongs to, and where in that conversation it occurred.

14 threading results Duplicate Spare Identifies duplicative s and places into relational groups Considers: From, Subject, Sent Date, body, attachments Doesn t consider: To, CC, or BCC Duplicate ID

15 threading results Threading Display Visualization of action, indentation, author, subject Blue bubble indicates an is both inclusive and non-duplicative

16 A Note on Near Duplicate ID: Run with Threading When run WITH threading, s are not examined for near duplicate identification. Documents in Document Set to Analyze that are not in s in Document Set are analyzed. All Docs All s Standalone Docs + Attachments *

17 A Note on Near Duplicate ID: Run By Itself When run WITHOUT threading, all documents are examined for near duplicate identification. All documents in the Document Set to Analyze are analyzed. *

18 Threading Workflows

19 Threading Review Workflow 1. How do I read the results before setting up for review? 2. Mimic an client view 3. Group threads together 4. Find threads with missing s 5. Batch by threads 6. Cull non-inclusives and duplicates 7. Add additional documents later 8. Use threads for QC

20 How to read the results before setting up for review?

21 Mimic an client view - Outlook vs. Relativity

22 Group threads together

24 Find threads with missing s

25 Batch by Thread

26 Cull for Review Culling non-inclusives and duplicates

27 Add additional documents

28 Add additional documents Changes on existing documents: Duplicate ID Duplicate Spare Doesn t change on existing documents: Inclusiveness Thread Group Threading ID

29 Quality control

30 Threading Scenarios Let s share workflow ideas

31 Scenario #1: Productions threading has been run on data collected from several custodians. The case team has decided that they will only review inclusive, non-duplicate spare s. Questions: When the responsive documents are ready to be produced, should the case team produce only the inclusive s or the non-inclusive s as well? What other considerations should we bear in mind for this production scenario?

32 Scenario #2: Rolling Data Loads threading has been run on data collected from several custodians. The case team is in the process of reviewing documents. New data is to be received on a rolling basis. This data will need to be threaded together with existing data in the workspace. Questions: Should a Full or Incremental Analysis be run on the new data? What are the implications for each?

33 Scenario #3: Propagation threading has been run on data collected from several custodians. The case team has decided that they will only review inclusive, non-duplicate spare s. They would like to know what field or fields can propagation be turned on in order to speed up the review process. Questions: What are some of the questions you should ask the case team to determine the end goal they are attempting to accomplish by using propagation? Should propagation be turned on for the Group Identifier field or the Thread Group? What are the implications of turning on propagation for Thread Group?

BOSTON USER GROUP. Workflows for Threading. kcura LLC. All rights reserved.

BOSTON USER GROUP. Workflows for Threading. kcura LLC. All rights reserved. BOSTON USER GROUP Workflows for Email Threading Jacob Cross Overview The objective of today s session is to give you some ideas that will hopefully increase your knowledge of how email threading works