<?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?output=omeka-xml&amp;page=15&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-04-18T13:08:05-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>15</pageNumber>
      <perPage>10</perPage>
      <totalResults>162</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="649" public="1" featured="0">
    <fileContainer>
      <file fileId="351">
        <src>https://www.thanksroy.org/files/original/1f5d18cbea94f2fa6f596815ee0c1fc0.jpg</src>
        <authentication>c1c0ddbdff4e682b5fc6760ec9716abd</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="5474">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5475">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5478">
                    <text>1152</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="72">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5479">
                    <text>1724</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <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="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="5470">
                <text>191</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5471">
                <text>Tony Rosenzweig Speaking at Roy's Celebration</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5472">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5473">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="682" public="1" featured="0">
    <fileContainer>
      <file fileId="384">
        <src>https://www.thanksroy.org/files/original/e72655e805c2cbc46e09380f0eb13e3a.jpg</src>
        <authentication>b98ddb38690cebd65a974543eb865fc1</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="5804">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5805">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5808">
                    <text>2298</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="72">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5809">
                    <text>3456</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <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="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="5800">
                <text>241</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5801">
                <text>Tony Rosenzweig Speaking at Roy's Celebration</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5802">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5803">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="600" 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="4922">
              <text>Good afternoon.&#13;
&#13;
I’m Kathi Brown, a former student of Roy’s...as well as former neighbor...and also a friend. I met Roy more than 20 years ago when I first entered the evening Masters program in History at GMU. I also had the privilege of being one of Roy’s research assistants on the opus that he and Betsy Blackmar crafted on the history of Central Park.&#13;
&#13;
When Roy’s wife Deborah e-mailed me a month ago to invite me to say a few words today, it took me approximately a nanosecond to reply with an enthusiastic “Yes!....Please!....Thank you!”&#13;
&#13;
No sooner did I hit SEND to respond to Deborah’s invitation than I burst out laughing. &#13;
&#13;
I pictured Roy, wide-eyed and astonished over the speed with which I had accepted an invitation to speak in public. &#13;
&#13;
He knew first-hand how much I loathe standing up in front of an audience. In fact, it was an ongoing joke between us. After I graduated with my Masters degree and started my historical consulting business back in the late 1980s, Roy used to ask me once a year to come back to campus to talk to graduate students about my career. Each year, like clockwork, I would listen to his invitation...hoot with delighted laughter...look him straight in the eye and reply: “Love you...would do almost anything in the world for you...EXCEPT this...NO!” &#13;
&#13;
After a few of these comically predictable annual exchanges, Roy conceded defeat and presumably found others who were less stubborn and more willing to say yes.&#13;
&#13;
Today, of course, is the exception that proves the rule. I could not in my wildest dreams imagine turning down Deborah’s invitation.&#13;
&#13;
Which brings to mind what I think is probably my all-time favorite quality in Roy. &#13;
&#13;
Roy, as we all well know, was brilliant...funny....eloquent...&#13;
inspiring...and blessed with the kind of giant mind, gentle spirit and generous heart that are rarely found cobbled together in one human being. &#13;
&#13;
But the trait I probably cherished most in Roy was something in which he was abysmally, magnificently lacking: &#13;
&#13;
Roy possessed a complete and utter inability to say NO. &#13;
&#13;
Need to borrow a book? Sure! No problem! Come on over to the Kaplan-Rosenzweig Lending Library anytime! Conveniently open from dawn to midnight. No lines, no limits, no late fines or fees............I loved it! And benefited from it, in part because I lived only four blocks away from Roy and Deborah for ten years...Believe me, I wore a trough in the sidewalk between their house and mine.&#13;
&#13;
Looking for a level-headed analysis of an existential crisis? Roy was my go-to guy. I could always count on him for a no-nonsense, if somewhat bemused interpretation of life’s quandaries. Mostly because I gave the poor man absolutely no choice, Roy shepherded me gently from my mid-20s “What should I do with my life?” to my current late-40s, middle-aged “OKayyyyyyyy, that was great! NOW what?”  If he had stayed with us for another couple of decades, I have no doubt that he would have had wise words and entertaining advice to offer me on everything from menopause to choosing a retirement community.&#13;
&#13;
Yet another area in which Roy could never manage to say NO was in the realm of computers. I can’t think of anyone who had more technology per square inch stuffed into a home office than Roy. Whenever I walked in the door at his Jackson Street house, I felt like I was boarding the Starship Enterprise.&#13;
&#13;
Roy’s affinity for the latest in high-tech toys proved his undoing. At least where I was concerned. Knowing that I had an expert living mere blocks away prompted me more than once to throw myself on Roy’s mercy when contemplating a computer purchase. &#13;
&#13;
Even now, a full 20 years later, I’m still half-ashamed of myself for the time I successfully pestered Roy into driving around Arlington with me one afternoon to three or four computer stores to protect me from fast-talking, geek-speaking salesmen. He did all the talking, while I more or less hid behind him, checkbook in hand, ready to close the deal whenever he gave me the signal!&#13;
&#13;
The next time around I was just as bad. When the time arrived to upgrade again, I actually made Roy call J&amp;R Music and Computer World, a big electronics discounter in New York, pick out a computer and negotiate a mail order sale for me.&#13;
&#13;
Later that day I got a call from him. &#13;
&#13;
“Kathi? Roy. OK, here’s what you do. Get out your wallet. Call 1-800-806-1115. Ask for extension 352. A very nice, non-threatening guy named Ed is standing by to take your credit card number....”  &#13;
&#13;
I kid you not!&#13;
&#13;
Perhaps even worse than begging for help with my computer purchases were the COUNTLESS times I dragged Roy away from the comfort of his home office to rescue me from some computer-related snafu of my own clumsy-fingered making. &#13;
&#13;
Just one example. I will never forget the time I managed to wipe out an entire book manuscript with just a few keystrokes. How I accomplished this incredible feat, to this day, I have no idea. All I know is that I sat dumbstruck at my computer for a few seconds and then did the ONLY logical thing....&#13;
&#13;
“Roy?” I cried tearfully into the phone. “My computer just ate my book!!!! Help!!!!”...There was a moment of silence...Then the voice on the other end replied calmly: “OK, put down the phone, raise your hands and slowly baccccckkkk awaaaaay from the desk. Don’t touch anything!! I’ll be right over!”&#13;
&#13;
Sure enough, Roy popped up on my doorstep five minutes later and spent at least THREE hours picking through my hard drive, scooping up shards of prose and reassembling as much of my opus as he could find. All the while, trying to comfort me. All I could do was sit next to him, doing a fine impression of Edvard Munch’s “The Scream,” staring helplessly at the screen, and humbly thanking him every five minutes for rescuing my baby from oblivion. &#13;
&#13;
And, naturally, Roy being Roy, as he was leaving, he extracted from me a solemn promise to learn to BACK UP MY COMPUTER, LOL!&#13;
&#13;
How can you not love a friend like that????&#13;
&#13;
I’m sure there were times when Roy might have preferred to Control-Alt-Delete me AND my computer problems right out of his life, but fortunately for me, he was too loyal and too kindhearted to say NO, no matter how ludicrous or ill-conceived my request......My comfort lies in the hope that along the way I provided him with sufficient entertainment—and friendship—to make it worth his while to keep me around!&#13;
&#13;
I’m just about out of time, but before I turn things over to the next speaker, I have just a little more to add, on a more serious note.&#13;
 &#13;
Roy was my hero. &#13;
&#13;
Plain and simple. &#13;
&#13;
When I first walked into Roy’s classroom on a September evening more than twenty years ago, I had no inkling that the mustached man with the shy smile and twinkling eyes at the head of the room was about to forever change the way I see the world. &#13;
&#13;
Not by hammering me over the head with the kind of ear-splitting, in-your-face, see-it-my-way-or-hit-the-highway blustering that dominates our public discourse today.&#13;
&#13;
Instead, he did it quietly. &#13;
&#13;
By putting the right books in my hands...&#13;
&#13;
By taking me on as a research assistant so I could learn the incomparable pleasures of historical detective work...&#13;
&#13;
He did it by listening...REALLY listening...never once in more than 20 years giving me the feeling that any question, any opinion, any idea I had was not worthy of serious consideration and a serious response.&#13;
&#13;
Above all, Roy did it by teaching me to ask the right questions.&#13;
&#13;
Not just in the classroom...&#13;
&#13;
Not just in my consulting work...&#13;
&#13;
And not merely questions about the past...&#13;
&#13;
Instead, he taught me to ask questions on a bigger, broader scale...about the way the world really works...or, often, doesn’t work. &#13;
&#13;
Questions I’ll be asking today...tomorrow...and for the rest of my life.&#13;
&#13;
The ability to shape someone’s mind for the better is a gift...the value of which is not to be underestimated. &#13;
&#13;
Fortunately, for those of us who were his students, Roy possessed that gift, in spades. &#13;
&#13;
So, whenever it was, 30 or more years ago, that Roy was presented with the opportunity to choose teaching as a career, rather than find something else to do with that magnificent mind of his.... &#13;
&#13;
I, for one, will always be grateful..........that he didn’t say NO.&#13;
&#13;
Thank you.&#13;
</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="4916">
                <text>129</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4917">
                <text>Tribute to Roy: Kathi Brown's Remarks from December 9, 2007 Celebration in Arlington, Virginia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4918">
                <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="4919">
                <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="4920">
                <text>Kathi Brown</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4921">
                <text>Kathi Brown</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4923">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="96">
        <name>computers</name>
      </tag>
      <tag tagId="24">
        <name>hero</name>
      </tag>
      <tag tagId="22">
        <name>mentor</name>
      </tag>
      <tag tagId="23">
        <name>neighbor</name>
      </tag>
      <tag tagId="20">
        <name>student</name>
      </tag>
      <tag tagId="21">
        <name>teacher</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="514" 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="4389">
              <text>Note: Prodded by the Digital Campus broadcasts, I had finally set up a blog on wordpress when I learned of Roy's death.  This was my first post.&#13;
&#13;
Roy Rosenzweig, Mark and Barbara Fried Professor of History and New Media at George Mason University, was a mentor and generous friend to those at a distance as well as to his many colleagues, collaborators, and students at George Mason University. We were saddened to hear of his death this past week.&#13;
&#13;
I have long counted myself lucky to have invited Roy to come to Miami University almost a decade ago. I had read his work in labor history and followed the development of the American Social History Project and Center for History and New Media initiatives. Teaching at Miami University’s regional campus in Middletown, Ohio, I worked with area teachers and coordinated the local National History Day competition. With generous support from both the Ohio Humanities Council and Miami University, I was able to invite Roy through the OAH Distinguished Lectureship Program, to spend two days in Ohio. He presented a workshop and discussion for local social studies teachers in Middletown and a lecture on history and new media on the Oxford campus. My great good fortune was to spend the two days with Roy, introducing him to colleagues, learning about the Center for History and New Media initiatives, discussing his book, with David Thelen, The Presence of the Past: Popular Uses of History in American Life, and talking over my own research and interests in digital media projects. We rambled around the Oxford campus, stopping to talk with faculty at Miami’s former College of Interdisciplinary Studies and then having lunch with Juan Gilbert, a professor in computer sciences who is now at Auburn University. I felt a bit like an outsider looking in on their conversation but I enjoyed every minute. Roy was an exciting speaker and a generous listener and mentor.&#13;
&#13;
Following his visit, Randy Bass came to the Middletown campus and the conversations that I had with both Roy and Randy inspired much of my subsequent work both directing a graduate program in public history at Wright State University and collaborating with educators on TAH grants. They helped me to see both my profession and the scholarship of history in a new way.&#13;
&#13;
Roy was a pioneer; he embraced the enduring value of the paperback book while moving beyond the narrower confines of print scholarship. And Roy always carried others forward with him. The ubiquitous red Z for Zotero in Firefox will remind many of us of Roy’s impact, through the Center for History and New Media, on our work. This June, not knowing that Roy was ill, I asked him to meet with my husband Gary Greenberg about a public television project. Once again, he gave generously of his time and his insights. Roy Rosenzweig has cast a wide net through his influential writing and the enduring value of the Center for History and New Media resources as well as through all of the colleagues he has listened to and inspired.</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="4383">
                <text>45</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4384">
                <text>Turning Point</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4385">
                <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="4386">
                <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 &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.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4387">
                <text>Marjorie McLellan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4388">
                <text>Marjorie McLellan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4390">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="147">
        <name>blog</name>
      </tag>
      <tag tagId="146">
        <name>National History Day</name>
      </tag>
      <tag tagId="208">
        <name>OAH Distinguished Lectureship</name>
      </tag>
      <tag tagId="148">
        <name>Randy Bass</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="524" 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="4460">
              <text>Roy was my friend for nigh on two decades. I first came across him through his work. Eight Hours is a marvelous book. For mine, it was one of the key books that helped make labor history interesting, that showed that the term could encompass rather more than all those tedious, although no doubt virtuous, histories of trade unions. The book had nothing in particular to do with what I was writing my dissertation on but it was one of the most influential forces in shaping what I put down on the page. Reading it I was constantly jotting down ideas that Roy’s prose had triggered—sly little asides, sharp observations, nice turns of phrase, all were grist for my mill. &#13;
&#13;
Our other “pre-contact” was over a piece I wrote that was solicited by the RHR and then rejected. My letter back to the RHR pointing out some of the journal’s shortcomings—in those days, one read RHR for the interviews with historians, Josh Brown’s stuff and, of course, R.J. Lambrose, but the quality of many of the articles was not exactly overwhelming-- gave me no little satisfaction. Roy and I derived a fair bit of amusement over the years out of that letter and what I had surmised about what had gone on even though I was a graduate student 10,000 miles distant—I mentioned some of this in the memorial site for Larry and Roy told me a couple of times that he was pleased to see a version out there.&#13;
&#13;
I met Roy at an OAH but really got to know him when I organized for him to come to Sydney to give the keynote to the Australian and New Zealand American Studies Association meeting in Sydney in 1990. Roy gave a wonderful talk on Central Park. Roy and I got on just great—I think we both believed in the virtue of gossip and of course Roy knew all these historians and I had spent a total of 6 weeks of my life in America and knew about two people who had written a book on American history. I can still hear Deborah’s voice as I was driving them both around to some site or other—“OK, you two, that’s enough.” &#13;
&#13;
From that time on I saw Roy once or twice a year, either at the OAH or when I went to Washington. He used to joke that he probably spent more time with me than with friends who lived in DC or NY. At first I used to stay with Roy because I was scrimping and scraping to afford to be in America but I carried on staying over on Jackson street even when I could charge a hotel bill up to a research grant. The reason was simple—the best way to talk to Roy was to be there at breakfast (tho I must confess jet lag meant I usually emerged from my room rather later than Roy and Deborah) or in odd minutes here and there during the day. And we talked, and drank coffee, and talked some more. &#13;
&#13;
When I think of Roy a whole series of images come to mind. The slightly awkward hug when we met. I was glad to see someone else mention this—I had always assumed it was just me not coping that well with the rather more touchy-feely American culture. Roy was incapable of just doing one thing at once—when a call came in that was going to take some time he’d often keep on tapping away on the computer but I also loved watching him “multitask” by unloading the dishwasher or in a slightly maniacal fashion grab some cleaning materials and scrub the coffee table or some other flat surface that could use a burnish. And I also still derive amusement from thinking about the moderately comical fights we would have about who was paying for dinner—there are some things I don’t lose and I soon worked out that the pre-emptive strike of paying on the way back from the bathroom was the best way to resolve that one. &#13;
&#13;
I remember what now seems a rather weird conversation from the early 1990s when Roy was trying to convince me of the virtues of email and how useful it would be for someone in my position (ie geographically challenged by the lights of many on the east coast of  America). And what’s more, hardly anyone was using it and it would be good to have email exchanges. I also remember from way back then talking to Roy, horrified, as he put together a new apple computer for some of the Voyager stuff without even opening the instruction manual. Last time I stayed with Roy he also gave me hours of talk and demonstrations on the virtues of zotero. Roy was slightly bemused by friends who were hardly computer-ept but he did tolerate us ! &#13;
&#13;
I can’t help but think back a couple of years to the San Jose OAH. I flew into San Francisco and Larry Levine and Roy were there to pick me up. We went back to Berkeley and had dinner and then the next day Cornelia joined us and we drove down to the conference. It was a terrific time. And then within weeks Larry found out he had cancer and died in what seemed a very quick fashion and then Roy too was diagnosed with the disease and died in even quicker time. Roy’s illness was one of the things that most troubled Larry as the end approached—they used to have long phone conversations as Roy trooped around getting medical treatment. &#13;
&#13;
Roy was probably the most generous person I have ever met, certainly by a considerable distance the most generous academic or historian. He was also very principled, perhaps ethical is the right word. When Roy spoke at the memorial for Larry Levine he quoted from me about Larry’s aggressive egalitarianism. I’d use the same words for Roy although in tone and manner the two were rather different. I’d also add that Roy was very sharp—I loved talkingt o hima bout books or articles we had just read. It was getting to know people such as Roy and Larry Levine that showed me the possibility of an egalitarian, inquiring and open-minded academe creating exciting history, a vision that I immediately contrasted with the dead hand of Oxbridge—crabbed, close-minded and wearing tweed jackets with leather patches—that held such sway in Australia for so long. Roy and Larry were very large factors in my embrace of many things American.&#13;
&#13;
And yet even if Roy was closer to sanctification than most of us, he was, thank god, no saint. Indeed, I found him even more endearing when some of those rough edges were, usually privately, displayed. Roy could be funny and savage at someone’s grandstanding; Roy heaped thoroughly deserved harsh words on the (absent) heads of people who let him down and had left him to do all the work even when he was very sick; and I remember him being almost speechless and not very happy on hearing some material of his being used by someone else and not particularly well either.&#13;
&#13;
For all that, he really was such a decent and self-effacing guy. I can remember how embarrassed he got when he asked me to write a reference for him for the Virginia award he got, offering me at least 20 ways out. The last time I saw Roy was at the OAH in Minneapolis earlier this year. “Treatment” had taken its toll and the trademark moustache as well as his hair had gone. Jon Wiener and I joked with him that if he could just dress a bit more snappily he would be the spitting image of Foucault. Everyone knew Roy but as he walked around the convention people he’d known for decades simply did not recognize him; many, he thought, were probably wondering who this weird guy was who was smiling at them and saying “Hi.” He also knew that if he went up and said “Hi, I’m Roy” these people would be mortified. That was Roy—always worried about the other person. &#13;
&#13;
It is still very hard to believe that he’s gone. For me at least, going to the OAH next year without either Larry or Roy is going to make it all seem very strange.      &#13;
&#13;
 &#13;
&#13;
   &#13;
</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="4455">
                <text>77</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4456">
                <text>Two decades of friendship</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4457">
                <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="4458">
                <text>Shane White</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4459">
                <text>Shane  White</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4461">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="200">
        <name>Australia</name>
      </tag>
      <tag tagId="98">
        <name>friendship</name>
      </tag>
      <tag tagId="216">
        <name>Levine</name>
      </tag>
      <tag tagId="217">
        <name>multitasking</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="542" 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="4589">
              <text>I did not see Roy on a daily or even a monthly basis.  Like everyone else, we were preoccupied with our own daily chores and routines.  So, over the past 2 months it's been easier for me to busy myself with work and to pretend that Roy's still here, busily tending to his many projects and responsibilities over at the Center and beyond. &#13;
&#13;
Now that the semester's winding down and the season's first snow has arrived (at least here in northern Virginia), I'm might just be ready to stop and remember Roy instead of waiting to see him one more time--at one more faculty meeting, one more picnic, one more job candidate's dinner (coating a salad with salt).  &#13;
&#13;
I relied upon Roy's presence (and am now feeling his absence) in so many ways, both spoken and unspoken.  He was the soul of our department.  &#13;
&#13;
During my first years on the job, Roy provided comfort and reassurance during moments of uncertainty and self-doubt. He was a much respected senior colleague, who listened like a trusted friend--a personal quality for which I will always be grateful and which I will never forget.&#13;
&#13;
Thank you, Roy, for everything--your humor, intelligence, creativity, integrity, dedication, and, most of all, your compassion and kindness.  Peace.</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="4584">
                <text>124</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4585">
                <text>Two months out</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4586">
                <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="4587">
                <text>Michael Chang</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4588">
                <text>Michael Chang</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4590">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="86">
        <name>decency</name>
      </tag>
      <tag tagId="209">
        <name>friend</name>
      </tag>
      <tag tagId="108">
        <name>History Department</name>
      </tag>
      <tag tagId="87">
        <name>kindness</name>
      </tag>
      <tag tagId="97">
        <name>work</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="502" 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="4305">
              <text>This is a message not only from myself but from the many researchers and activists working in applied and public history across Australia. Over the years we have all been excited and stimulated by Roy's wonderful, varied work.&#13;
&#13;
We have been deeply saddened by the news of Roy's death and we are all grieving for the loss of such an extraordinarily generous and creative colleague. Our sympathies and warmest thoughts go to Roy's family and his wider family of colleagues in and out of history. &#13;
&#13;
Roy's work in digital history meant he was an extraordinary communicator across vast distances both in kilometers and cultures.  So even from halfway round the world, we found his work a great inspiration. It has encouraged many of us not only in academic history research but much more importantly in the work of democratising history and using new media to do it.&#13;
&#13;
His work will keep doing that and it is great to be able to share in its celebration here! </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="4300">
                <text>23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4301">
                <text>Warm memories and thanks from Australia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4302">
                <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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4303">
                <text>Heather  Goodall</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4304">
                <text>Heather  Goodall</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4306">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="104">
        <name>applied history</name>
      </tag>
      <tag tagId="200">
        <name>Australia</name>
      </tag>
      <tag tagId="105">
        <name>democratising</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="596" public="1" featured="0">
    <collection collectionId="1">
      <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="5958">
                  <text>Formal Notices</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5959">
                  <text>Obituaries and paid death notices.</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="4892">
              <text>Digital Historian Roy A. Rosenzweig&#13;
&#13;
By Adam Bernstein&#13;
Washington Post Staff Writer&#13;
Saturday, October 13, 2007; Page B06&#13;
&#13;
Roy A. Rosenzweig, 57, a social and cultural historian at George Mason University who became a prominent advocate for  digital history,  a field combining historical scholarship with digital media's broad reach and interactive possibilities, died Oct. 11 at Virginia Hospital Center in Arlington County. He had lung cancer.&#13;
&#13;
Dr. Rosenzweig, who taught history at GMU for the past 26 years, founded the university's Center for History and New Media in 1994. As its director, he oversaw the creation of online history projects aimed mostly at high school and college students, including Web sites about U.S. history, the French Revolution and the history of science and technology.&#13;
	&#13;
&#13;
At GMU's Center for History and New Media, Roy A. Rosenzweig oversaw the creation of online history projects.&#13;
At GMU's Center for History and New Media, Roy A. Rosenzweig oversaw the creation of online history projects. &#13;
&#13;
Perhaps its most visible project was the September 11 Digital Archive, a collection of 150,000 items -- including e-mails, digital voice mails, BlackBerry communications and video clips -- made by average citizens at the time of the 2001 terrorist attacks. The center gave the materials to the Library of Congress in September 2003.&#13;
&#13;
The center, part of GMU's Department of History and Art History, has more than 40 full- and part-time staff members.&#13;
&#13;
Dr. Rosenzweig was an author, filmmaker and documenter of oral histories. His books, including a social history of New York's Central Park and the labor movement's struggle in the 19th century for a shorter workday, underscored his interest in presenting what he called  perspectives of ordinary men and women  over the wealthy and powerful.&#13;
&#13;
In the early 1990s, he helped create an award-winning U.S. history survey presented on CD-ROM. He then started the Center for History and New Media, which stemmed from his wish  to democratize the study of the past -- both by incorporating forgotten voices and by presenting the fullest possible story of the past to diverse audiences. &#13;
&#13;
Edward L. Ayers, president of the University of Richmond, who conducted early digital history projects as a University of Virginia history professor, said Dr. Rosenzweig  was the real pioneer in this. &#13;
&#13;
Ayers said that Dr. Rosenzweig's CD-ROM  Who Built America?  (1994), created with the help of two other historians,  first showed the possibilities of digital history  and that he remained important as an advocate by writing articles and reviews of Web sites for professional journals, through which he was a  facilitator and translator of digital history. &#13;
&#13;
Roy Alan Rosenzweig was born Aug. 6, 1950, in New York and was raised in the Bayside neighborhood of Queens. He graduated magna cum laude from Columbia University in 1971.&#13;
&#13;
He received a fellowship to study history at St. John's College at Cambridge University and received a doctorate in history from Harvard University in 1978.&#13;
&#13;
He joined GMU's history faculty in 1981 and became a full professor in 1992. His best-known early book,  Eight Hours for What We Will  (1983), was about the labor movement's demand for an eight-hour workday and the subsequent rise in more urban leisure spaces such as public parks and movie theaters.&#13;
&#13;
Dr. Rosenzweig wrote often in journals for historians about what he once called the  fragility of evidence in the digital era  because of e-mail documentation that is too easily deleted.&#13;
&#13;
He was a former vice president for research at the American Historical Association and formerly chaired the Organization of American Historians technology committee. Among his honors was the 2003 Lyman Award presented by the National Humanities Center for innovative use of information technology in the humanities. It carried a purse of $25,000.&#13;
&#13;
His marriage to Beth Bernick Rosenzweig ended in divorce.&#13;
&#13;
Survivors include his wife of 26 years, Deborah Kaplan of Arlington; his mother, Mae Rosenzweig of Coconut Creek, Fla.; and a sister.&#13;
&#13;
</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="4886">
                <text>73</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4887">
                <text>Washington Post</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4888">
                <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="4889">
                <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="4890">
                <text>washington post</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4891">
                <text>mike  o'malley</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4893">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="6">
        <name>formal notices</name>
      </tag>
      <tag tagId="194">
        <name>obituary</name>
      </tag>
      <tag tagId="5">
        <name>WashingtonPost</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="602" 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="4938">
              <text>	Welcome friends, family, colleagues. Thanks to all of you for being here today, and a very special thanks to the many people who worked so hard to put this event together, especially Amy Noecker of the College of Humanities and Social Science Dean's office, who really did most of the heavy lifting.  I'd also like to thank George Mason University President Alan Merten, who has done so much to support Roy's work at the Center for History and New Media over the years and to Provost Peter Stearns and Dean Jack Censer, who provided the financial means for today's events.&#13;
&#13;
	My name is Tom Scheinfeldt, and I worked with Roy at the Center for History and New Media for just over five years.  &#13;
&#13;
	We are gathered here today to honor, remember, but especially to celebrate Roy's life. &#13;
&#13;
	I can't begin to put into words what the loss of Roy means to his friends and family, to the historical profession, to digital scholarship, to George Mason University, and to me personally, so I'm not even going to try.&#13;
&#13;
	I don't think Roy would have wanted me to try. I think he would have wanted us to concentrate on moving forward, on what still is to be gained rather than on what has been lost. Mostly I think Roy would have wanted us to enjoy ourselves today, to take this opportunity of being together to forge new collaborations and renew old friendships. &#13;
&#13;
	Roy was a deeply emotional and extraordinarily caring person, but he wasn't overly sentimental. In that spirit, those of us on stage today are going to do our best to keep things honest but upbeat, heartfelt but light. For such a distinguished scholar, one of Roy's abiding charms was his gleeful love of TV sitcoms. He was particularly fond of Seinfeld and its writers' maxim that the show contain  no hugging, no crying, no lessons learned.  We should do our best today to take Jerry Seinfeld and Larry David's advice ourselves. That means you should feel free to enjoy yourself. You should feel free to laugh. You should feel to speak unselfconsciously during the open mic portion of the program. You should feel free to get up and go to the bathroom.&#13;
&#13;
	For my part I'm going to do what Roy always did when we bade farewell to a staff member at CHNM who was leaving for graduate school or some other opportunity. Roy always started with history, by reading the first email he received from the person. The date of Roy's first email to me is May 10, 2002, during my first week at CHNM. Roy was finishing his sabbatical at Harvard, and aside from a brief meeting during my interview at OAH a few weeks earlier, I hadn't spent any time at all with Roy. Nevertheless, Roy was about to become my most frequent and voluminous correspondent. It's a lengthy email, stuffed with attachments. It begins:  Tom -- This is probably more than you want to read.  Over the next five years, I received nearly 10,000 emails from Roy, an average of more than five per day. Sometimes there were more than I wanted to read.&#13;
&#13;
	That first email ends:  Many thanks for coming into things with so much energy; it sounds like you have already made a terrific start. Take care, Roy.  I was a brand new hire, still ABD, and Roy hardly knew me. But no matter how many emails he sent, no matter how long, and no matter to whom they were addressed, Roy always ended with a word of encouragement or praise. I had a mostly working relationship with Roy, but all work with Roy was close work. That made me a very lucky guy.&#13;
&#13;
	You will hear a lot more today about the work Roy did while he was still alive. In many ways, however, the work Roy left undone is as important as the work he did himself. Roy left not only a legacy, but also a to-do list (Roy was very fond of to-do's). Just this week we were provided with two examples of how we will continue to benefit from Roy's hard work and generosity long into the future, and of just how much of that work remains to be done. &#13;
&#13;
	Today, I am very pleased to announce that CHNM has been awarded two major grants from NEH, both of them written largely by Roy just this summer. The first is for a major study of current digital research practices in the profession and to further push the bounds of digital historical research.&#13;
&#13;
	The second grant targets CHNM as a center of excellence and will endow it with an Infrastructure and Innovation Sustaining Fund through a challenge grant of $750,000. What this incredible opportunity means is that donations made to CHNM in Roy's name will help us meet the full NEH challenge of $2.25 million, part of which will endow a prize in Roy's name. Styled  The Roy Rosenzweig Prize in History and New Media  this award will be presented annually by CHNM and the American Historical Association for an innovative and freely available new media project that reflects thoughtful, critical, and rigorous engagement with technology and the practice of history. We have already raised $30,000 towards this prize and we hope to raise enough funds this year to begin awarding it in 2009.&#13;
&#13;
	Some of you have already made donations to CHNM in Roy's name. Thank you. Those donations may be applied to the challenge, and we will be back in touch shortly with information on how to do that. Those of you who have not already made a donation—or those who have but would like to make another gift towards the prize fund—will find a card in your program with additional details. You should also feel free to contact me or Dean Censer directly if you would like to discuss your donation. I know Roy was very grateful for your support of his work and his Center through the years, and on behalf of everyone at CHNM, I would like to thank you very much for your continued friendship.&#13;
&#13;
	Roy was a business-first kind of guy, so now that we have the business out of the way, we can turn to something more personal. For the next 50 minutes or so, we will hear from a wide assortment of Roy's family, friends, and colleagues.  After that, around four, we will turn it over to all of you for your stories and reflections. About five we will adjourn to the Law School atrium across the parking lot for drinks and Chinese appetizers.  After that, we will venture out to enjoy ourselves in smaller groups at some of Roy's favorite neighborhood restaurants, which you will find at the back of your program.&#13;
&#13;
	Thank you all again.  Let’s get started.&#13;
&#13;
</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="4932">
                <text>131</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4933">
                <text>Welcome to Celebration of Roy's Life</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4934">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4935">
                <text>Tom Scheinfeldt's speech welcoming everyone to the Celebration of Roy's Life, December 9, 2007.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4936">
                <text>Tom Scheinfeldt</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4937">
                <text>2007-12-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4939">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="521" 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="4437">
              <text>This is my October 21, 1007 column for The Examiner newspaper.&#13;
&#13;
Being a teacher is as schizophrenic as being a student. There’s class, and there’s life, and “never the twain shall meet.” Students pretend to focus on schoolwork between the hours of 7:20 a.m. and 2:05 p.m., but who are they kidding? Certainly not their teachers, who remember what it was like to be constrained emotionally and intellectually by schoolroom rules.&#13;
&#13;
	As a teacher, I expect of myself more focus and less distraction, yet sometimes life insinuates itself into my lessons.  While my students have been distracted by homecoming, I have been thinking about a distinguished George Mason University colleague who recently died of cancer at the age of 57. &#13;
&#13;
	Hundreds of Mason students and teachers are mourning his untimely death, but my high school students know nothing of Roy Rosenzweig’s digital histories or of his many contributions to GMU and his Center for History and New Media, and so I keep my sense of loss private.&#13;
&#13;
	While talking about literature in the classroom, I have been composing in my mind an email to his wife, whom I have known for over 30 years. How can I show her compassion when I have not suffered the loss of a husband? What comfort can I offer when I don’t really understand the devastating effect of that loss? &#13;
&#13;
	Oddly, I found the answer to that question grading papers. School and life merged the moment I read my classes’ essays on “Their Eyes Were Watching God,” which focused on the heroine, Janie’s, response to Teacake’s untimely death. What comfort did Janie find for the loss of her companion and the love of her life?	&#13;
&#13;
	Student after student wrote that to Janie, Teacake still “lived” since his effect on her remained. She mentally projects her memories—“pictures of love and light”—against the wall of her home. She gathers up those memories and lifelong dreams and calls in her soul “to come and see.” Teacake “could never be dead until she herself finished feeling and thinking.”&#13;
&#13;
	Zora Neale Hurston’s words are Janie’s comfort, and were precisely the words I needed for Roy’s wife, Deborah. Roy’s books, teachings, and digital texts remain, and the memories of those who knew him are the “pictures of love and light.” &#13;
&#13;
	What also remain are the ways Roy changed others. Like Teacake, Roy treated people respectfully and graciously. His friends and colleagues have created a website (http://thanksroy.org) that reflects myriad instances when his personality and intellectual strengths made others wiser and stronger--“pictures” preserved.  &#13;
&#13;
	Of course no website, no matter how moving or comprehensive, can begin to compensate for the loss of a husband or friend, a death that came decades too soon. But reading my students’ commentaries helped me see that books are often relevant to life outside the classroom, and that Hurston’s words have a function beyond my English curriculum.&#13;
&#13;
	Perhaps at a distant point in the future, some of my students will remember that a person’s “love and light” cannot die as long as they themselves have “feeling and thinking.” At that moment, they might realize that sometimes what we learn in the classroom can teach us about life. Sometimes “the twain” does meet.&#13;
&#13;
</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="4432">
                <text>63</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4433">
                <text>When Life and the Classroom Meet</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4434">
                <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="4435">
                <text>Erica Jacobs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4436">
                <text>Erica Jacobs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4438">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="173">
        <name>Deborah</name>
      </tag>
      <tag tagId="175">
        <name>legacy</name>
      </tag>
      <tag tagId="174">
        <name>pictures</name>
      </tag>
      <tag tagId="1">
        <name>roy</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
