<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="549" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://thanksroy.org/items/show/549?output=omeka-xml" accessDate="2026-04-14T12:53:30-04:00">
  <itemType itemTypeId="1">
    <name>Document</name>
    <description>A resource containing textual data.  Note that facsimiles or images of texts are still of the genre text.</description>
    <elementContainer>
      <element elementId="1">
        <name>Text</name>
        <description>Any textual data included in the document.</description>
        <elementTextContainer>
          <elementText elementTextId="4635">
            <text>I first met Roy Rosenzweig at a 1999 conference sponsored by the Alfred P. Sloan Foundation at Stanford University organized by David Kirsch and Timothy Lenoir about use of websites to capture recent history of science and technology.  I believe the link was James T. Sparrow, who pioneered websites on the New York City blackouts of 1965 and 1977 while still a history graduate student at Brown University (http://sloan.stanford.edu/InfoBlackout.htm; http://blackout.gmu.edu/).  Roy recruited Jim to the Center for History and the New Media about that time.  David had developed a site about the history of electric vehicles ( http://sloan.stanford.edu/InfoEV.htm), while Tim had a site about the history of the computer mouse (http://sloan.stanford.edu/InfoMouse.htm).  Only eight years ago creating history on the web was radical and indeed very hard, as such early sites show.  The breadth and depth of Roy’s vision for history and the new media elevated the Stanford conference, which assembled scattered, lonely and even clandestine practitioners.  Roy saw that new kinds of history could be created and communicated, and that some strong institutions were needed to improve and spread the practice and to spur preservation and access.  After the conference, Sloan invited a proposal from George Mason to expand CHNM’s work into history of science and technology.  Roy submitted a characteristically first-class proposal, which won support within only a couple of months of submission.  Roy, always expanding, assimilated historian of science Daniel Cohen and the Exploring and Collecting History Online (ECHO http://echo.gmu.edu/) project – Science, Technology, and Industry took off.  &#13;
	&#13;
A few days after 9/11 Sloan Foundation staff members were considering ways that Sloan-supported activities might help improve matters in New York and Washington DC.  I contacted Roy, and before September was over he visited the Foundation offices in Rockefeller Center together with GMU colleagues and also counterparts from City University of New York.  Roy appreciated instantly that the software and techniques developed for ECHO might apply to 9/11 and its aftermath.  Within weeks, sites were established to collect, preserve, and present the history of 9/11 (http://911digitalarchive.org/).  While already building the sites and collecting materials, Roy prepared another first-class proposal, which the Sloan Foundation trustees immediately supported.  Less than two years later, in September 2003, the Library of Congress would accept the 9/11 Digital Archive into its collections, an event that both ensured the Archive's long-term preservation and marked the Library's first major digital acquisition.  The Sloan story repeated in 2005 after Katrina and Rita with the creation of the Hurricane Digital Memory Bank (http://www.hurricanearchive.org/).  Meanwhile, Roy had further built the CHNM team with Tom Scheinfeldt, Josh Greenberg, and other excellent recruits. &#13;
&#13;
During the eight years or so that I knew Roy, he expanded, with excellence, in all directions: into history of science and technology, into contemporary history, into new technologies, into the heart of the historical profession, out to the expert amateurs and enthusiasts, into the Library of Congress, Internet Archive, and other archives, into bookstores, and onto desktops, within George Mason University and in networks covering the USA.  Helping provide support was a pleasure, and my main concern was to minimize his chores with regard to funding, so he and his colleagues could get on with their very worthy work.  Fast, smart growth of imaginative historical practice is what I will always associate with Roy.&#13;
&#13;
Jesse Ausubel, program director, Alfred P. Sloan Foundation</text>
          </elementText>
        </elementTextContainer>
      </element>
    </elementContainer>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="4631">
              <text>148</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="4632">
              <text>You must be 13 years of age or older to submit material to us. Your submission of material constitutes your permission for, and consent to, its dissemination and use in connection with Thanks, Roy in all media in perpetuity. If you have so indicated on the form, your material will be published on Thanks, Roy (with or without your name, depending on what you have indicated). Otherwise, your response will only be available to approved researchers using Thanks, Roy. The material you submit must have been created by you, wholly original, and shall not be copied from or based, in whole or in part, upon any other photographic, literary, or other material, except to the extent that such material is in the public domain. Further, submitted material must not violate any confidentiality, privacy, security or other laws.&#13;
&#13;
By submitting material to Thanks, Roy you release, discharge, and agree to hold harmless Thanks, Roy and persons acting under its permission or authority, including a public library or archive to which the collection might be donated for purposes of long-term preservation, from any claims or liability arising out the Thanks, Roy's use of the material, including, without limitation, claims for violation of privacy, defamation, or misrepresentation.&#13;
&#13;
Thanks, Roy has no obligation to use your material.&#13;
&#13;
You will be sent via email a copy of your contribution to Thanks, Roy. We cannot return any material you submit to us so be sure to keep a copy. Thanks, Roy will not share your email address or any other information with commercial vendors.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="4633">
              <text>Jesse Ausubel</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="37">
          <name>Contributor</name>
          <description>An entity responsible for making contributions to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="4634">
              <text>Jesse Ausubel</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="4636">
              <text>Document</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
