1. Beyond Conflicting Portrayals to Facts in Time and Space Robert Haug, Ann Larimore, and Sandra Arlinghaus University of Michigan SSHA Conference, Nov. 13, 2003

2. Purposes ► Provide a web-based methodology for moving beyond impasses in conflicts. ► Analyze the dynamics of a developing conflict. ► Quickly access significant information through linkages between source documents. ► Ascertain communalities and differences in stakeholder groups’ accounts, as well as gaps, discrepancies, ambiguities, and uncertainties in the data. ► Provide the framework of a digital archiving program. ► Automation of existing “pen and paper” methodology. ► Can be applied to numerous case studies.

3. DocuMap ► Allow users to search a digital collection of primary source documents through events, players, time, and location. ► Create a web-like network around each document based on each set of attributes. ► Search across multiple scales of both time and space.

4. Purchase of 30 gallons of wine and 6 iron bound kegs, Meriwether Lewis and David Jackson, June 1, 1803, Philadelphia, PA. Document taken from U.S. National Archives and Records Administration Web Site.

5. Design ► Three major interlinked components:  A database storing scans of primary source documents and attributes of the documents  An interactive GIS of locations and areas related to the documents  A calibrated time-line visible at multiple scales ► A fourth component derived from the other three:  A master narrative drawn from the primary source documents and organized around attribute data.

6. Design, cont.: ► Interface residing on a public web site. ► The general public can search the archives, view documents, and perform analysis on the documents. ► Users may be granted permission to upload documents with the necessary metadata and attribute data. ► Initially focused on handling a single case study. ► Ability to link between documents within case study also gives ability to link between seemingly unrelated documents from numerous case studies.

7. Difficulties in Implementing ► Permanency: Potential to be in a constant state of change. ► Monitoring the potentially constant upload of data.  Protection against the insertion of faulty or falsified documents.  Protection against the insertion of faulty or falsified metadata or attribute data.  Hackers looking to sabotage the project.  Parties with a politically/emotionally motivated plan to distort the narrative. ► Displaying documents without any kind of historical context.

8. Possible Solutions for Case Study Use ► Maintain the format of the shell. ► Alter the user privileges. ► Search and basic analysis functions open to the public. ► Data entry performed quarterly by small (5-7 person) collaborative case study teams.

9. Three Month Iterations ► First Month: Data collection, case study team brings forward any documents they would like to include. ► Second Month: The insertion of all metadata and attribute data into the master database and the creation of accompanying base maps for the GIS component and calibrated time-lines. ► Third Month: Case study team collaborates in writing a master narrative.

10. Stipulations for Contributors ► Provide primary source documents ready to be scanned into a digital format. ► Documentation for each document, both metadata and attribute data about events, players, time, and location related to the document. ► Provide a paragraph or two describing each document, including an explanation of the author, the conditions under which the document was produced, its audience, and the reason for its creation. ► Participate in the writing of the master narrative for their case study.

11. Stipulations for Case Study Teams ► Host case study web site linked to central DocuMap repository including:  Searchable repository of documents used in specific case study.  Interactive GIS of case study area.  Calibrated time-lines.  Master narrative.