<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" 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://www.thanksroy.org/items/browse?output=omeka-xml&amp;sort_dir=d&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-04-16T21:14:52-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>1</pageNumber>
      <perPage>10</perPage>
      <totalResults>162</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="615" public="1" featured="0">
    <fileContainer>
      <file fileId="319">
        <src>https://www.thanksroy.org/files/original/ec612055de8e385e32166628259c04e7.jpg</src>
        <authentication>dc3b8d1ca4bfdee55b868f89fe0add48</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5086">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5087">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5090">
                    <text>2682</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="72">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5091">
                    <text>1728</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </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="5080">
                <text>41</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5081">
                <text>				&#13;
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 &lt;em&gt;Thanks, Roy&lt;/em&gt; in all media in perpetuity. If you have so indicated on the form, your material will be published on &lt;em&gt;Thanks, Roy&lt;/em&gt; (with or without your name, depending on what you have indicated). Otherwise, your response will only be available to approved researchers using &lt;em&gt;Thanks, Roy&lt;/em&gt;. 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 &lt;em&gt;Thanks, Roy&lt;/em&gt; you release, discharge, and agree to hold harmless &lt;em&gt;Thanks, Roy&lt;/em&gt; 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 &lt;em&gt;Thanks, Roy&lt;/em&gt;\'s use of the material, including, without limitation, claims for violation of privacy, defamation, or misrepresentation.&#13;
&#13;
&lt;em&gt;Thanks, Roy&lt;/em&gt; has no obligation to use your material.&#13;
&#13;
You will be sent via email a copy of your contribution to &lt;em&gt;Thanks, Roy&lt;/em&gt;. We cannot return any material you submit to us so be sure to keep a copy. &lt;em&gt;Thanks, Roy&lt;/em&gt; will not share your email address or any other information with commercial vendors.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5082">
                <text>Roy doing research on Central Park Conservatory</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5083">
                <text>Betsy Blackmar</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5084">
                <text>Betsy Blackmar</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5085">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="613" public="1" featured="0">
    <fileContainer>
      <file fileId="317">
        <src>https://www.thanksroy.org/files/original/44ce78a4e198587dfb79ebed830121d4.jpg</src>
        <authentication>aedead5f86435a9eca1c59470e656cb3</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5062">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5063">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5066">
                    <text>473</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="72">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5067">
                    <text>639</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </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="5056">
                <text>35</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5057">
                <text>				&#13;
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 &lt;em&gt;Thanks, Roy&lt;/em&gt; in all media in perpetuity. If you have so indicated on the form, your material will be published on &lt;em&gt;Thanks, Roy&lt;/em&gt; (with or without your name, depending on what you have indicated). Otherwise, your response will only be available to approved researchers using &lt;em&gt;Thanks, Roy&lt;/em&gt;. 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 &lt;em&gt;Thanks, Roy&lt;/em&gt; you release, discharge, and agree to hold harmless &lt;em&gt;Thanks, Roy&lt;/em&gt; 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 &lt;em&gt;Thanks, Roy&lt;/em&gt;\'s use of the material, including, without limitation, claims for violation of privacy, defamation, or misrepresentation.&#13;
&#13;
&lt;em&gt;Thanks, Roy&lt;/em&gt; has no obligation to use your material.&#13;
&#13;
You will be sent via email a copy of your contribution to &lt;em&gt;Thanks, Roy&lt;/em&gt;. We cannot return any material you submit to us so be sure to keep a copy. &lt;em&gt;Thanks, Roy&lt;/em&gt; will not share your email address or any other information with commercial vendors.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5058">
                <text>May 18, 2006</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5059">
                <text>Andrew Yarrow</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5060">
                <text>Andrew Yarrow</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5061">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="597" public="1" featured="0">
    <collection collectionId="2">
      <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="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5960">
                  <text>Celebration</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5961">
                  <text>Speeches from the Celebration of Roy's Life, December 9, 2007, George Mason University, Arlington campus, Arlington, VA.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="4898">
              <text>I am Betsy Blackmar, and I am one of the many people in this room who arrived in Cambridge, Massachusetts in the early 1970s very uncertain as to what exactly we were doing. Roy helped us figure that out. What do you do when you don’t know what you are doing? You organize a reading group; you form a collective to produce a journal, you make sure that all of your friends know each other—whether in person or as legends.  You give other people drafts of your work to read and read theirs and talk to them. Roy helped us all collectively to gain the confidence to do our creative work, and he helped many of us find jobs, housing, roommates, and life-long friends.  Given Roy’s faith in mutuality and reciprocity, it matters to me to think that I may have given him back one thing: he met Deborah at a party at my Cambridge apartment. (of course, given the principles of six degrees of separation on which he operated, they were destined to meet  one way or another). And Deborah gave Roy back to us all a hundred fold by sharing his hospitality and wit, and, over the years,—I think it took a long time-- helping him see that he could do even more if he didn’t stay up all night or live on chocolate donuts and Tab or drive himself to exhaustion; she even taught Roy to take vacations, which just seems like a miracle.&#13;
&#13;
Roy recruited me to help write a short screen play for a short documentary by Richard Broadman on Boston’s parks. Then, he suggested that we write a short book on Central Park. The thing is, the story was more complicated, there were more layers, we really needed to bring it up to the present, so more than six years and 600 pages later, we finished the Park and the People.  But we would not have been able to do this had Roy not figured out the magic key to grant writing: all of our proposals started with a Johnny Carson joke from the mid-1960s—“It was so quiet last night in Central Park, that you could have heard a knife drop.”  It was followed somewhere in the proposal by another one,  “Did you hear the Soviet ambassador was mugged in Central Park last night? The park commissioner said it was an exceptional case: ‘it’s the first time they got a Russian’.”  I never knew where Roy found these Johnny Carson jokes, but who else but Roy would recognize that someone sitting reading fifty pleas for money would be desperate for some comic relief? Of course, being Roy, he also compiled and analyzed all the crime statistics of the 1960s to prove that it was safer to be in the park than on the streets of New York. &#13;
&#13;
It was not always easy to collaborate with Roy.  It was not just the damn to-do lists and the feeling that you could never keep up with him.  It was Roy’s honesty: you just couldn’t tell Roy white lies about why you hadn’t done something you said you would do.  I don’t think Roy hated a lot of things, but I do think he really really disliked  cowardly self-serving white lies and excuses. He also didn’t have much use for pomposity, grandiosity, arrogance, or abuses of power.   &#13;
&#13;
There is only one time when I think Roy was actually relieved that I didn’t follow through on something: for his 40th birthday, just after we finished the park book, I gave him a trowel and the promise of 100 daffodil bulbs. I had arranged to have the bulbs shipped to my house in Carmel, but, as it turned out, I didn’t travel to Washington that Fall, so I ended up planting them in my yard: he never asked me what happed to his opportunity to become a gardener. &#13;
&#13;
When I think of Roy now, I think of that little crinkle and light in his eyes when he was telling or hearing a good story. I think of the pleasure of sharing Roy’s and Deborah’s stories of the Human Comedy. It is probably because he recognized and so readily forgave the foibles of his friends, his colleagues, his students, that Roy was able to help so many of us muddle through and collectively hold each other up through so many bad things, political and personal, of which surely one of the hardest is losing Roy himself. &#13;
&#13;
Okay: no tears, no hugging, but here’s a lesson Roy would have allowed: start your grant proposals with a joke.</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="4894">
                <text>155</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4895">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4896">
                <text>Betsy Blackmar</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4897">
                <text>Betsy Blackmar</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4899">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15">
        <name>central park</name>
      </tag>
      <tag tagId="13">
        <name>friends</name>
      </tag>
      <tag tagId="1">
        <name>roy</name>
      </tag>
      <tag tagId="14">
        <name>think</name>
      </tag>
      <tag tagId="16">
        <name>time</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="549" public="1" featured="0">
    <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>
  <item itemId="545" public="1" featured="0">
    <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="4607">
              <text>I was one of the lucky ones in the Master's program at GMU, because Roy was my advisor.  My academic career was checkered, at best.  I returned to college to finish my BA at age 35 and received my MA in 1992 at the age of 38. Between Roy and Josephine Pacheco, I made it.     Roy was such a help as an advisor - with the one exception of the night before my comprehensive examination, when at a reception for graduate students he approached me and told me that if I had time for a party that meant that I had, in fact, memorized all of the Secretarys of State - in order!   After almost fainting, he told me he was kidding and got me a much needed glass of wine!  &#13;
&#13;
I have fond memories of being in his home discussing books that he assigned for my Directed Reading course.  The list was endless, but 15 years later, I remember each one of them and make great use of them in my career as a community college instructor.  We e-mailed back and forth over the years, and he was always interested in what was going on with me.  When I learned of his death, I was saddened - my heart aches for his close friends, and especially for his family. My thoughts are with you, and please know that his impact on my life - as well as many others - has been enormous.  Thanks, Roy.</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="4603">
                <text>127</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4604">
                <text>		&#13;
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="4605">
                <text>Beverly Hudson Wirtz</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4606">
                <text>Beverly Hudson Wirtz</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4608">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="537" public="1" featured="0">
    <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="4551">
              <text>I earned my MA at GMU working with Roy.  He helped me understand history in new ways, and managed to help get me connected to the world of public history.  His help inspired me to go on and earn a PhD.  He will be missed.</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="4547">
                <text>105</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4548">
                <text>		&#13;
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="4549">
                <text>Greg Wilson</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4550">
                <text>Greg Wilson</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4552">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="530" public="1" featured="0">
    <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="4501">
              <text>I first met Roy in 1983, serving then as the liaison librarian to the history department.   I had gone up to his office on the fifth floor of the library and introduced myself--explaining that I was there to do whatever I could to better enable the library to support the history department.   We hit it off from the start since we were both interested in computers and neither of us was in a position to do much about it within our areas of responsibility. &#13;
&#13;
Roy was polite and listened to my library spiel for a few minutes without much reaction; that is, until I happened to mention the word dBASE.  He was suddenly very interested and in no time had me helping him figure out how to code a menuing system for a database he was using to store information about oral history interviews.   &#13;
&#13;
Once we finally got it working, I remember we both laughed over the idea that the university's computer center had just decreed that dBASE would not be supported and everyone should standardize on Condor 3. We both instantly agreed it was just better to go underground.</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="4497">
                <text>92</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4498">
                <text>		&#13;
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="4499">
                <text>Wally Grotophorst</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4500">
                <text>Wally Grotophorst</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4502">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="232">
        <name>Library dBASE</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="506" public="1" featured="0">
    <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="4331">
              <text>Roy was my master's thesis advisor during the late 1980s. He always made himself available to talk and answer questions. He served on several occasions as the outside reviewer of my professional accomplishments during the 1990s. I cannot thank him enough for his time and wisdom.&#13;
&#13;
Roy, you will be missed.</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="4328">
                <text>115</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4329">
                <text>Russell Lee</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4330">
                <text>Russell Lee</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4332">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="541" public="1" featured="0">
    <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="4582">
              <text>I am one of the fortunate ones who benefited in profound ways from knowing Roy even though I did not know him very well. Larry Levine, whom I got to know when he served on an advisory board of a film reference book project that I was involved in, encouraged me to enroll in Mason’s cultural studies program by talking up the history department he recently had joined. He suggested I look at Eight Hours for What We Will. That book, along with Larry’s Highbrow/Lowbrow, showed me what could be done with the study of popular culture when historians approached it from a broader perspective. I recently completed my dissertation, writing much of it after both Larry and Roy had become ill. I realize now that in a sense I was writing it for them to read, knowing that in some ways, both obvious and oblique, it was hugely informed by their work.</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="4576">
                <text>123</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4577">
                <text>Writing for Roy</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4578">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4579">
                <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.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4580">
                <text>Alan Gevinson</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4581">
                <text>Alan Gevinson</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4583">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="257">
        <name>Eight Hours for What We Live</name>
      </tag>
      <tag tagId="260">
        <name>influence</name>
      </tag>
      <tag tagId="258">
        <name>Larry Levine</name>
      </tag>
      <tag tagId="261">
        <name>popular culture</name>
      </tag>
      <tag tagId="259">
        <name>writing</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="548" public="1" featured="0">
    <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="4629">
              <text>What follows is a speech I wrote for the special AHA session in Roy’s memory on January 5, abridged to avoid duplicating my other post on this site.&#13;
&#13;
I worked with Roy at the Center for History and New Media for ten years, from 1995 to 2005, and he also was my thesis adviser form 1998 until I graduated in 2004. I will talk about what it was like to work with him at the Center and to have him as a mentor. And because my relationship with Roy was mediated by technology I’ll talk about Roy’s relationship with technology as well.&#13;
&#13;
Several times in conversations with Roy I heard him speculate why there are not more hit TV series and movies about historians. TV shows and films about doctors and cops are popular, he used to say, because they are always urgently needed to save lives somewhere. If only we could come up with an emergency that would urgently require an intervention by a historian, played perhaps by Nicholas Cage or Angelina Jolie, who could rush to the scene and save the day, the discipline would have much better representation in American popular culture. &#13;
&#13;
I think Roy was skeptical about this possibility. However, in some ways, working with Roy was like this imaginary action movie. It was exciting and it was full of emergencies. &#13;
&#13;
I began working at the Center as its only employee. The center was Roy, Mike O’Malley, and me, with a standard Mac desktop for a server, located in a closet in a former student dormitory, with only six web pages on it. Of course, now there are dozens of historical websites and tools produced at the Center, but for the first few years we only had two or three. Eventually, we could afford top-of-the-line equipment and put it in a secure facility with multiple backups, but for the first few years that wasn’t an option. Web servers crash. Roy however, refused to acknowledge that fact. Once on an anniversary of 9/11 Jim Sparrow and I accidentally unplugged the machine that was serving millions of connections to our September 11 Digital Archive, and could not restart it for several minutes because the database got corrupted. For Roy, who was pacing back and forth watching us trying to repair the damage, every second our historical data stayed offline was agony.&#13;
&#13;
There were times when Roy would drive in to GMU’s Fairfax campus himself on a snow day—a real emergency in Virginia—to restart a crashed server as soon as possible. Roy never asked me outright to drop everything and spend 5 to 10 hours trying to work out the problem but he had a way of pausing on the phone, or nervously walking around in person that conveyed the message very well.&#13;
&#13;
I can’t say I didn’t resent the havoc Roy’s work ethic did to my social life. If I had a dinner engagement, I cancelled it. If I was on vacation in San Francisco, I had to go into a closest café with wireless to solve problems remotely. Immediately after arriving to any city, I looked for Starbucks coffee shops (that were guaranteed to have wireless access), to be ready in case an emergency would occur. &#13;
&#13;
Once I was on the metro right before Ballston station on my way to work when I got a call from Roy. It turned out that Pennee Bender from the American Social History project was presenting on our History Matters site at a conference. Her presentation was to start in 5 minutes and she just discovered that the search page didn’t work. I had to get off the train, out of the Ballston station, into the Starbucks, and fix the search in 5 minutes—as always for Roy, failure wasn’t an option.&#13;
&#13;
At first I was surprised at how seriously Roy took every glitch, but then I realized that he did this because he had a strong sense of purpose and a clear idea of how to accomplish it. For him, history only made sense as a democratic project. He believed that digital media could democratize history, and to this end he produced historical websites, spoke at innumerable meetings, wrote grant proposals, and promoted collaborative and open source scholarship. Keeping the server always on was just a minor manifestation of his larger vision and his determination to accomplish it.&#13;
&#13;
Working with Roy as a student resembled an action film in a different way—the  emergencies where all mine and he was the one who saved the day. Quite simply, I would not be a historian today if it wasn’t for Roy. I’m Russian, and it would have been impossible for me to finish school if I didn’t have a job at CHNM at the same time. He had to fill out mounds of extra paperwork to hire me, and when my American visa got delayed for two months, Roy didn’t give up and kept the job open for me when he didn’t have to. &#13;
&#13;
Many students claim being close to their advisers—Roy was generous in ways that this common phrase doesn’t really describe. He would be always happy to meet with me, and always enthusiastic about my work, but when a conversation would approach a conclusion, he would just say “Ok” with a certain inflection, and I would know that I had to get out of the office so he could move on to other work. We communicated as much over email and instant messaging as in person. Roy once told me how he and Deborah, working on two separate floors of their house, simultaneously got emails with links to the YouTube video of Stephen Colbert mocking President Bush at the White House Correspondents’ Dinner. Only later did they realize that they were watching the video on different computers at the same time. One could imagine that Roy and Deborah sometimes communicated by email in the house as well. But in my case, the way Roy used email was much more valuable than any heart-to-heart conversations we didn’t have.&#13;
&#13;
It was remarkable enough that Roy could answer an email within seconds if it was about Center business, but what I appreciated even more was that when I asked him to help with my own work his responses were just as fast. During the celebration of Roy’s life in December, people were offering statistics on thousands of emails they got from Roy. Here are some statistics on how little time it took for Roy to get back to me over email about my research.&#13;
&#13;
Reading and commenting on my book prospectus: 17 hours&#13;
&#13;
Reading and commenting on reader reviews of my book manuscript: 9 hours&#13;
&#13;
Answering a question about my dissertation: 10 minutes&#13;
&#13;
Answering the last question I asked him, about a book we both had read, on September 26, 2007: 2 hours.&#13;
&#13;
How Roy found the time to reply this fast, I have no idea. He knew and communicated with so many people in the US and beyond—when I was about to move to Montreal to teach Roy sat down with me and gave names of a half a dozen digital humanities scholars he knew in Canada. In September 2005, over iChat, I asked Roy to read something of mine, and as always, he immediately agreed. Then he tried to figure out when he would actually do it. Here is what he wrote on IM:&#13;
&#13;
Roy Rosenzweig: maybe not this weekend&#13;
&#13;
Roy Rosenzweig: but monday&#13;
&#13;
Roy Rosenzweig: maybe&#13;
&#13;
Roy Rosenzweig: i have plane flight and hopefully could do then&#13;
&#13;
Roy Rosenzweig: i have picnic tomorrow and then antiwar march&#13;
&#13;
Roy Rosenzweig: and then various people are staying over&#13;
&#13;
Roy Rosenzweig: i have conferences all next week&#13;
&#13;
I know that what he had done for me he did for hundreds of other people. Thanksroy.org is full of testimonies of people he helped. I think he was such a perfect mentor precisely because one didn’t have to be his favorite student or colleague to count on his help and unwavering support. His commitment to social equality was not just academic, it encompassed everything he did—researching working-class culture, helping students, going to antiwar rallies, and lobbying for open source scholarship. Many brilliant historians exist but I haven’t met anyone as ethical and committed as Roy. He provided more than conventional history instruction; he taught by example.&#13;
&#13;
Roy was always there when one of his friends, colleagues, or students needed help yet anything more than a cursory expressions of gratitude made him uncomfortable. I got so desperate about this that when Roy asked me to write a letter in support of a grant the Center was applying for, I used the letter to thank him for many things he had done for me, and then asked him to proofread it to make sure that he actually looked at the words. Among other things, I wrote, “It would not be an exaggeration to say that my years at CHNM”—and as Roy’s student—“transformed my understanding of the purpose and practice history. I will always be grateful for this experience.” Thanks, Roy.</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="4623">
                <text>145</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4624">
                <text>Working with Roy</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4625">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4626">
                <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.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4627">
                <text>Elena Razlogova</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4628">
                <text>Elena Razlogova</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4630">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="199">
        <name>chnm</name>
      </tag>
      <tag tagId="181">
        <name>computer technology</name>
      </tag>
      <tag tagId="268">
        <name>generosity</name>
      </tag>
      <tag tagId="87">
        <name>kindness</name>
      </tag>
      <tag tagId="22">
        <name>mentor</name>
      </tag>
      <tag tagId="21">
        <name>teacher</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
