1 / 14

Top-Down/Bottom-Up Analysis Workshop

Top-Down/Bottom-Up Analysis Workshop. Simon Attfield. Sensemaking in e-discovery. The challenge When conduct of a company is brought into question... Investigation - regulatory or prelude to litigation Lawyers search, review, sort and re-represent data A high-recall problem

juan
Télécharger la présentation

Top-Down/Bottom-Up Analysis Workshop

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Top-Down/Bottom-Up AnalysisWorkshop Simon Attfield

  2. Sensemaking in e-discovery • The challenge • When conduct of a company is brought into question... • Investigation - regulatoryor prelude to litigation • Lawyers search, review, sort and re-represent data • A high-recall problem • Construct the narratives that matter from unstructured info. • ... a collaborative sensemaking problem

  3. The problem of manual review • The problem of ‘information inflation’ – a ‘pulse’ in the history of information [Paul & Baron, 2007] • A challenge to effectively identifying the evidentiary record within reasonable constraints of time and cost.

  4. ‘Information inflation’ - challenges tractability • Jeane Thomas, Crowell & Moring • (Keynote at DESI II, 2008) • Mergers and Acquisitions for AT&T • Document requests from US Department of Justice • 1996 – 12 to 15 lawyers – 300 boxes of paper • 2004 – 125 contract lawyers – reviewed 30 million pages and produced 12 million relevant documents • 2005 – 600 lawyers – reviewed 112 million pages and produced 17 million relevant pages

  5. Case studies of regulatory investigations at a London law firm.

  6. ThreadsVI • The construction of narrative is important. • Emails are units of communication. Email threads are higher order-units of communication. • Investigations are people-centric • Wanted... • Visualisation that supported visual indexing by people, emails and threads. • Visualisation that showed thread overlap – i.e. faithful to chronology.

  7. The Enron collection • In October 2003, US Federal Energy Regulatory Commission placed collection of Enron's internal emails from 1999-2002 into the public domain as part of its ongoing investigations. • ~ 500,000 messages belonging to 158 users - mostly senior management. • ~250,000 unique messages. • One of the few or only substantial set of emails available. • Much research has been done with the collection.

  8. Help users shape the flow of information they receive [McNee & Arnette, 2008] • Provide an overview of what’s underneath

  9. Update the dataset and get ThreadsVI going • Downloadhttp://www.eis.mdx.ac.uk/vass/simondatafiles.zip • Save zip file to Desktop/visualindexesdemo/OUT/ • Unzip in that folder (overwrite) • Change the screen resolution to 1152 x 864 • Go to Desktop\VASS\visualindexesdemo • Right click vi-threads.ss • Open with Firefox

  10. Task Context • Facts • Enron filed for bankruptcy in late 2001 • Largest bankruptcy in history • Many debts and losses were not reported • Imaginary Scenario • Enron was funding research at Poppleton University. The money didn’t appear on the books. • You are investigating debts that weren’t declared.

  11. Task • Investigation questions • Did Enron give money to Poppleton? If so what/when? • Who might be responsible for the accounting decisions? What is your evidence for oragainst? • Who would you like to interview and why? • Meta-questions • Record your thinking. What hypotheses did you have? Were they challenged? • What representations did you create? • What additional tools/functionality would you add?

More Related