<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Will Riley &#187; history</title>
	<atom:link href="http://www.willriley.net/tag/history/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.willriley.net</link>
	<description></description>
	<lastBuildDate>Sat, 21 Jan 2012 17:28:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Digital Archives as Deweyan Publics?</title>
		<link>http://www.willriley.net/democratic-media/digital-archives-as-deweyan-publics/</link>
		<comments>http://www.willriley.net/democratic-media/digital-archives-as-deweyan-publics/#comments</comments>
		<pubDate>Sun, 14 Mar 2010 21:57:01 +0000</pubDate>
		<dc:creator>Will Riley</dc:creator>
				<category><![CDATA[Democratic Media]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[dewey]]></category>
		<category><![CDATA[digital archive]]></category>
		<category><![CDATA[digital humanities]]></category>
		<category><![CDATA[disalvo]]></category>
		<category><![CDATA[history]]></category>
		<category><![CDATA[Omeka]]></category>
		<category><![CDATA[public sphere]]></category>

		<guid isPermaLink="false">http://www.willriley.net/?p=185</guid>
		<description><![CDATA[In his paper, Design and the Construction of Publics, Carl DiSalvo develops tactics for how designers could construct publics in accordance with John Dewey&#8217;s conception of a public. According to DiSalvo, the Deweyen public, as articulated in Dewey&#8217;s book,The Public and Its Problems, is not something that has been and always will be. It is [...]]]></description>
			<content:encoded><![CDATA[<p>In his paper, <a href="http://www.mitpressjournals.org/toc/desi/25/1">Design and the Construction of Publics</a>, Carl DiSalvo develops tactics for how designers could construct publics in accordance with John Dewey&#8217;s conception of a public.  According to DiSalvo, the Deweyen public, as articulated in Dewey&#8217;s book,<em>The Public and Its Problems</em>,  </p>
<blockquote><p>is not something that has been and always will be. It is neither universal nor an abstraction. Rather, for Dewey, the public is a specifiable and discernible entity that is inextricable from its conditions of origin. More precisely, for Dewey, the public is an entity brought into being through issues for the purpose of contending with these issues in their current state and in anticipation of the future consequences of these issues. (DiSalvo, p.49)</p></blockquote>
<p>DiSalvo emphasizes that Deweyan publics are &#8220;situated&#8221; around experienced issues, &#8220;multiple&#8221;, and &#8220;not exclusive to a particular class or social milieu&#8221; (DiSalvo, p.50)</p>
<p>He identifies two characteristic tactics for constructing a Deweyan public, namely tracing and projecting.<span id="more-185"></span> According to DiSalvo, tracing &#8220;is the activity of revealing, of exposing the underlying structures, arguments, and assumptions of an issue&#8221;  and involves making marks that &#8220;follow and record the presence and movement of an artifact, event, or idea&#8221; (DiSalvo, p.55). Projecting, on the other hand, &#8220;can be defined as the representation of a possible set of future consequences associated with an issue&#8221;, and involves making &#8220;apparent the possible consequences of an issue&#8221; (DiSalvo, p.52-53).  </p>
<p>DiSalvo stresses that the tactic of projection is predictive, but not prescriptive.  In this sense, projecting is about what will probably happen &#8211; not what should happen.  If this notion of projection as prediction-without-prescription aligns with Dewey&#8217;s construction of the public, it is somewhat misaligned with the rhetorical dimensions of predictions.  Rhetorically, predictions are all about prescriptions.  For example, weather reports are often used to suggest or prescribe behavior changes, such as stay off the icy roads.  Similarly, political election predictions, rhetorically serve as prescriptive voting signals (people don&#8217;t like to &#8220;waste&#8221; their votes on those predicted to lose).  So while I understand the apparent emphasis on prediction-as-description and not prediction-as-prescription, I think that our conceptualization of the tactic of projection should be widened to include prediction-as-prescription.</p>
<p>One of DiSalvo&#8217;s most useful interpretations of Deweyan publics, is how he teleologically relates tracing and projecting to history and forecasting.  According to DiSalvo, &#8220;tracing&#8221; and &#8220;projecting&#8221; are, in part, distinguished from &#8220;history&#8221; and &#8220;forecasting&#8221;,  on the grounds that tracing and projecting are oriented toward the present &#8211; they are in some sense for-the-present, whereas the purpose of history and forecasting is oriented for-the-past and for-the-future, respectively. (DiSalvo, p. 58)  So tracing is not just about digging up the past for a more comprehensive retrospective; it is an attempt to clarify the living present.  </p>
<p>Many historians, especially progressive ones, think that their work is relevant to present issues, that their pursuit for explanation illuminates the present, but I wonder if an intellectual bias for historical comprehension points away from present issues.  Tracing does not seem to share this intellectual bias for comprehension.  </p>
<p>In my view, tracing, unlike history, is intellectually biased for helping to address a present issue.  For example, a history about an issue would be bad if it did not mention any major event that helped cause that issue.  However, it is possible that a good trace of an issue does not mention any major event causing the issue, if what it does mention about the history of an issue proves useful to the public in dealing with that issue.  In this sense, the tactic of tracing is judged on the concrete utility of the information it provides in helping the public address the issue, and not judged on whether the information helps the public fully understand the progression of the issue.  In other words, knowing all the causes of an issue does not imply knowing how to address the causes in a useful way.  History is biased for a more comprehensive explanation, whereas tracing is biased for a more useful explanation.</p>
<p>DiSalvo&#8217;s tactics provide a useful conceptual framework  for designers in the digital humanities, especially those that deal with digital archives, to consider whether they are designing Deweyan publics or historical archives.</p>
<p>There is a definite tension with what a digital archive is &#8211; is it a public or private space, and if it is a public space, can it also be a Deweyan public?  In other words, can a digital archive, not only be a public place to store and organize historical references, but also be a place useful to and situated within personal political issues?  I tried to design the <a href="http://petitionarchives.org">Petition Archives</a> so that it was not just a public space for political history or a private place for prompting political results, but a public space situated in personal political issues.  </p>
<p>In my view, the politicization of the digital archive seems quite natural, since it is a form of socially networked digital media.  For many archivists, allowing the public to trace or project their issues into a digital archive is a dangerous proposition.  From this perspective, orienting the archive toward the present may disrupt or corrupt the interpretation of the past or the future.  For example, adding comments or public tags to a digital archive, while of serious interest to many curators, is also seen as a threat to the educational value of the archive.  Perhaps those comments will distract or misinterpret the artifact on display, or perhaps the user-contributed tags will overwhelm the archive with navigational noise.</p>
<p>Exhibits &#8211; not archives &#8211; are supposed to offer safe places for tracing and projecting.  The exhibit can take digital copies of items from the archive, and manipulate them without corrupting the archive.  From a data preservation perspective, one can build multiple exhibits around the same archival data without staining the past with the present.  However, from an educational perspective, exhibits with user generated content that attempt to trace the past or project the future still threaten to misinterpret the past, present, and future.  It is assumed that curators, historians, and archivists are somehow supposed to protect the public from misinterpreting the data.  They are supposed to filter out the non-sense, authorize the good stuff, and keep it around in case someone needs it.  However, protecting the public from the archive and the archive from the public is not solely motivated by an interest in preserving public education.  It is also motivated by a need to preserve and accrue political power.</p>
<p>The state has a tremendous political and economic interest in filtering the archive and its exhibits so that it can continue to promote and benefit from nationalism and patriotism.  Organs of the state often do this by sugar-coating the past and the future with curated propaganda.  For example, consider the Donald W. Reynolds Museum and Education Center at Mount Vernon, which spends much of its time propping up the image of the slave-owner George Washington as a &#8220;man of character&#8221;.  What would be the psychological and economic impacts if the majority of Americans stopped sucking on the sugar and started to seriously re-interpret our first president as a greedy slave-owner?  What would be the meaning of the dollar bill or the State of Washington or Washington D.C.  if the people of America suddenly believed that George Washington was not simply &#8220;a man of character&#8221; who <a href="http://www.mountvernon.org/learn/meet_george/index.cfm/ss/101/">privately despised slavery and then &#8220;lead by example&#8221; through the freeing of his slaves</a>, as Mount Vernon would have us believe, but that Washington was a cruel man who, for the vast majority of his life economically profited from slavery and who at the end of his life only freed some of his slaves to protect his posterity (Martha&#8217;s slaves were practically his slaves too).  What would happen if Americans began to believe that Washington was the politician who <a href="http://www.seacoastnh.com/blackhistory/ona.html#5">tried to bribe Joseph Whipple</a>, Portsmouth&#8217;s Custom&#8217;s Collector, to kidnap Ona Judge Staines, one of his wife&#8217;s former slaves who had escaped to New Hampshire, and ship her back to him.  The state would suffer if it helped the people trace the issue of slavery in the digital museum and archive space.</p>
<p>But tools like Omeka are beginning to challenge this notion that archives are just a place for history by offering some means for tracing and projection.  Firstly, Omeka is free and open to any public to create their own digital archives.  Individuals, and not just authorized cultural institutions, have access to Omeka.  People can start an Omeka archive, as I did with the Petition Archives, to trace or project political issues.</p>
<p>Secondly, Omeka has a plugin architecture which allows users to create social plugins based on external web services, such as IntenseDebate, which allow the public to discuss, rate, and review individual archive items. Omeka also offers a Contribution plugin, which allows users to contribute items to the archive, thereby helping to trace their own connection to politically charged historical events.</p>
<p>In conclusion, DiSalvo provides us with some of the theoretical framework to analyze digital humanities tools, such as Omeka.  Designers now have an opportunity to ask: How do digital humanities tools trace and project the past and the future?  How can we use the tactics of tracing and projecting to rethink, redesign, and reconstruct digital archives as Deweyan publics?  And we are left with bigger questions.  Are their other tactics for creating Deweyan publics?  Are there any general best practices or conventions for tracing and projecting?</p>
<p><strong>Sources:</strong></p>
<ul>
<li>&quot;<a href="http://www.mitpressjournals.org/toc/desi/25/1">Design and the Construction of Publics.</a>&quot; Design Issues Vol. 25, No 1., 2009: 48-63.</li>
<li>Omeka, <a href="http://omeka.org">http://omeka.org</a></li>
<li>The Petition Archives, <a href="http://petitionarchives.org">http://petitionarchives.org</a></li>
<li>Ona Judge Staines: Escape from Washington, Evelyn Gerson, <a href="http://www.seacoastnh.com/blackhistory/ona.html">http://www.seacoastnh.com/blackhistory/ona.html</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.willriley.net/democratic-media/digital-archives-as-deweyan-publics/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

