<?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;page=3&amp;sort_field=Dublin+Core%2CCreator" accessDate="2026-04-16T22:59:13-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>3</pageNumber>
      <perPage>10</perPage>
      <totalResults>162</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="528" 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="4488">
              <text>I arrived at George Mason University in July of 2005, a wet-behind-the-ears, just-graduated librarian stuck with the thankless task of running a new institutional repository.&#13;
&#13;
Even before I met him, his presence and CHNM's on campus gave me faith in what I was doing -- some faculty DID care! Not only that, they were writing books and building tools that would help me open the world!&#13;
&#13;
I did have the privilege of meeting Roy at last. The inevitable tall cup of coffee was involved! What struck me about him was his awareness; he really heard what was happening around him, and the complex machinations involved as he assimilated what he heard to what he already knew (and he knew a lot!) were practically visible.&#13;
&#13;
I congratulated him by email when he became a design element on the Create Change open-access website. I was so pleased and proud to be associated with him, even in such a tenuous fashion as working at the same campus in a roughly similar problem space.&#13;
&#13;
The open-access community is much, much the poorer for his loss. As I am.</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="4483">
                <text>89</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4484">
                <text>Living open access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4485">
                <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="4486">
                <text>Dorothea Salo</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4487">
                <text>Dorothea Salo</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4489">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="199">
        <name>chnm</name>
      </tag>
      <tag tagId="114">
        <name>gmu</name>
      </tag>
      <tag tagId="229">
        <name>open access</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="532" 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="4515">
              <text>When Roy took me on as a Ph.D. student in 1998, I've been through three American universities and several advisers. I was alone in the US--my entire family was back in Russia. I was also broke and ready to give up. If it wasn't for Roy I would probably be working in a bank in Moscow right now. Instead I teach history at a university in Montreal. I owe both my career as a historian and my urban bohemian lifestyle to Roy.&#13;
&#13;
Roy approached my education, as he did many things, as a collaborative project, and all of a sudden instead of no advisers, I had two great ones, Roy and Mike O'Malley. And he gave me a job at CHNM so I could earn enough money to survive in the US. Roy was a perfect adviser--he was always there when I needed help yet did not demand any adoration or flattery in return. In fact, he found any expression of gratitude annoying. I still have Roy’s comments on all of my chapters--he wrote pages of detailed suggestions for revision, complete with spelling and grammar corrections (particularly relevant in my case). I could always count on him to write a letter for me or to help with a grant, no matter how exasperated he was with a last-minute request. When I applied to the university where I'm teaching now, the committee unexpectedly requested a second long letter from Roy, to be emailed the same day, dealing specifically with my work in digital history. I went to his office, and he wrote it right then, in ten minutes, even though he was extremely busy. I wouldn't have gotten that job if he didn't take time to write that letter. Roy didn't just teach historiography and method--from him I learned why history only makes sense as a democratic project, by talking to him, reading his books and comments, working with him at the Center, and listening to his stories about his many friends who did history elsewhere.&#13;
&#13;
As others have pointed out here, Roy was generous to all of his students and junior colleagues. Many times, Roy would mention a manuscript he had read for a former student, or an outline for a book he had commented on for a former colleague, or a letter he had written for someone. When in 2007 Roy received a Distinguished Service Award from the OAH, the program included a short film by a high school student. The very first thing Roy did after the ceremony ended was to turn to the student and talk to her at length about her project. In one of his last published articles he made sure to emphasize the importance of a dissertation in progress by one of his students. &#13;
&#13;
I know what he did for me he would have done for anyone, but I needed it more. I miss him every day.</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="4509">
                <text>94</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4510">
                <text>Roy as teacher</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4511">
                <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="4512">
                <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="4513">
                <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="4514">
                <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="4516">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="199">
        <name>chnm</name>
      </tag>
      <tag tagId="26">
        <name>history</name>
      </tag>
      <tag tagId="87">
        <name>kindness</name>
      </tag>
      <tag tagId="22">
        <name>mentor</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>
  <item itemId="556" 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="5963">
              <text>I was Roy’s student and worked with him at the Center for History and New Media for ten years. Working with Roy gave me a skewed, somewhat utopian perspective of what academia was really like. He was always happy to meet with me. He read all of my chapters within a week. He was in the audience when I presented my first conference paper and many times when I presented afterward. His letters of recommendation were written well before the deadline and required no reminder. One would expect that it would be stressful to have an adviser who was also your boss. And yet looking back at emails from that period it seems that it was me who constantly complained about needing to prepare a job talk or a paper, and it was Roy who always patiently sacrificed deadlines to give me time off. In fact, his Center have provided, and still does, this kind of flexible support to dozens of graduate students who have worked there through the years. Roy even gave me rides from campus to the metro occasionally so I didn’t have to take a bus. I was completely spoiled. I actually thought it was a matter of course to expect all these things from your adviser until I talked to my friends and found out that theirs did nothing of the sort.&#13;
&#13;
Today, now that I know how rare that experience had been, I would like to mention some things that I learned from Roy.&#13;
&#13;
For example, Roy taught me some of my English, my second language. From him, I first heard words like “deep-six,” as it “to deep-six this unconvincing argument,” and academic stock phrases such as “a study that fills a much-needed gap.” I learned my email-speak from Roy—how to say “thanks!” constantly no matter how trivial the task done for you; how to send encouraging one-liners, “That’s great! Roy,” in response to emails most people would ignore; how to preface work assignments with “whenever you have time” and “no rush on this,” when you really mean “do it as soon as you can.”&#13;
&#13;
Roy taught me how to be a researcher. He researched everything. At the first memorial for Roy at George Mason University in Arlington, a friend of his described how Roy embarked on a research project to get a letter to the editor published in the &lt;em&gt;New York Times&lt;/em&gt;. He determined the published letters often started with “We are shocked and dismayed,” and used the phrase. The letter was published. Roy demanded the same dedication from his students and research assistants. I still remember how I spent hours going through the &lt;em&gt;Washington Post&lt;/em&gt; in search of a Doonesbury cartoon for him that gave the only two possible reasons for producing web sites as “fear and greed,” and then through the Hearst press from the 1940s in search of an anti-Sidney Hillman limerick, to include on the &lt;em&gt;Who Build America&lt;/em&gt; CD. The limerick was not printed when Steven Fraser’s book &lt;em&gt;Labor Will Rule&lt;/em&gt; claimed it would be, but several weeks later. None of his students could get away with close readings of a few texts—a method then popular in my field of historical cultural studies. I don’t need to refer to &lt;em&gt;The Chicago Manual of Style&lt;/em&gt; to format my book; I can refer to Roy’s and Elizabeth Blackmar’s &lt;em&gt;The Park and the People&lt;/em&gt;, a study that cites every possible kind of source, and has the most elaborate abbreviation system I have yet to encounter in a work of scholarship.&#13;
&#13;
Roy taught me how to comment on other people’s work. When he showed me how to rewrite completely one of my less successful drafts, in a 5-page single-spaced line-by-line commentary, he was quite direct and at times sarcastic. To one of my wilder propositions he responded, “I am prepared to believe that this is the case, but the claims here seem to rest on two anecdotes.” Yet he was also kind—he also used, quite without foundation, words “perceptive,” “well-written,” and “wonderful,” the latter three times. I’m not sure Roy was capable of writing comments that were not detailed—he gave such thorough responses not just to dissertation and book chapters but also to papers he assigned in his Clio Wired class (an introduction to digital history) that he invented and taught for years.&#13;
&#13;
Roy taught me how to be a radical historian. I read mounds of books that claimed to provide ever more radical readings of various practices and texts. In contrast, it was useful to encounter Roy’s less ostentatious, everyday brand of radicalism. At the first memorial for Roy at George Mason University in Arlington, Alison Landsberg, his friend, colleague, and neighbor, read an email from Roy and Deborah from 2003 where they invited friends to participate in an antiwar candlelight vigil in Arlington, Virginia. “If there is interest,” they wrote, “we would be happy to organize a group dinner of take out food at our house before hand (5:30?) or after.” At the time it seemed that mass demonstrations in DC, while inspiring to participants, changed neither gender policies nor war plans of the Bush Administration. Yet Roy never gave up. Every single one of his projects—from an antiwar vigil to his work at the &lt;em&gt;Radical History Review&lt;/em&gt; to convincing the AHA to make articles in the &lt;em&gt;American Historical Review&lt;/em&gt; available for free on the web—aimed at getting things done. The Center for History and New Media, which he founded to democratize history, is perhaps his most important work of radical scholarship.&#13;
&#13;
Most importantly, in doing all of the above, Roy taught me how to be a human being. He ignored no one—at every meeting or party, he would make sure to find the least important person in the room and strike up a conversation. Even after he became ill and was often tired he continued to help colleagues, advise students, direct the Center, and of course, answer his email. Many people had no idea how ill he was and where shocked by his passing because he never stopped being Roy, in any circumstances.&#13;
&#13;
I miss the sense of security Roy gave his students immensely and yet I will always have his sense of purpose in doing history. Most of all, I miss him. 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="4677">
                <text>261</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4678">
                <text>Morning Coffee with Roy, Roy as Mentor""</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4679">
                <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="4680">
                <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.  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.  Thanks, Roy has no obligation to use your material.  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="4681">
                <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="4682">
                <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="4683">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="199">
        <name>chnm</name>
      </tag>
      <tag tagId="81">
        <name>coffee</name>
      </tag>
      <tag tagId="134">
        <name>commitment</name>
      </tag>
      <tag tagId="87">
        <name>kindness</name>
      </tag>
      <tag tagId="22">
        <name>mentor</name>
      </tag>
      <tag tagId="280">
        <name>radical</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="517" 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="4411">
              <text>Like so many, I have tales to tell about Roy's generosity and intellect and unflagging, mind-boggling work ethic. I first met Roy at the beginning of my second year in graduate school; during my first year, two other students (Elena Razlogova and John Spencer) and I had developed rudimentary history cd-roms. Elena had gone on to study with Roy at GMU (and become CHNM's first employee), and as a result, John and I had been invited down to present our cd-roms at a brown bag lunch event at GMU's history department. Elena met us at the train station, and as we exited into the Washington sunlight, she led us toward a car driven by a slightly rumpled, distracted looking guy in a red button down shirt and black jeans. As the car pulled away from the curb, John and I realized that this was Roy Rosenzweig. *The* Roy Rosenzweig, respected scholar, one of the only people doing the kind of digital history to which we aspired. And he was picking up two unknown graduate students at the train station. It was an entirely appropriate way to begin; he exhibited particular generosity to those low on the academic food chain. I came to know Roy in more venues after that first day; through the &lt;i&gt;Radical History Review&lt;i&gt;, where I served as Managing Editor for two years, and through the American Social History Project, where I had the enormous privilege of working with him on a myriad of projects. While in no way officially connected with my doctoral education, Roy became a true mentor, introducing me to people I should know, and the first person I turned to for career advice. &#13;
&#13;
There is so much that I will remember about Roy: his keen editorial eye (the quickest way to improve every grant proposal I ever wrote for ASHP was to run a draft past Roy); his ability to move projects forward; his deep reservoir of odd historical facts, handy for historical timelines and puzzles; the certainty that an email message to him would be returned within a matter of hours; his endearingly awkward half hugs of greeting. I'm still only barely able to acknowledge that he isn't going to be around any more, that there won't be some new project or meeting or meal at a conference or email message passing along information about a project or person I should know about. I hope that Roy had some idea of how very many people admired and loved and valued him. I guess what we do now is carry on in his spirit, the only alternative we have to carrying on in his presence.&#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="4406">
                <text>56</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4407">
                <text>A Drive from Union Station</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4408">
                <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="4409">
                <text>Ellen Noonan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4410">
                <text>Ellen Noonan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4412">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="167">
        <name>American Social History Project</name>
      </tag>
      <tag tagId="166">
        <name>graduate students</name>
      </tag>
      <tag tagId="22">
        <name>mentor</name>
      </tag>
      <tag tagId="168">
        <name>Radical History Review</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="558" 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="4696">
              <text>“Radical historian” means different things to different people. There is certainly a generational divide in how most of us understand this label and its professional context. I am not of Roy’s generation, so I won’t pretend to understand what it meant to Roy to be a “radical historian” when, as a graduate student, he was among the founders of the MidAtlantic Radical Historians Organization, or MARHO. Intellectually, MARHO “sought to develop a critical history as a means of understanding capitalism as a mode of production and as a complex system of social relations.” Professionally, MARHO sponsored forums, conferences, a newsletter, and the Radical History Review, all designed to help put those politics into action by promoting teaching and public history to non-scholarly audiences at a time when the mainstream of the profession marginalized such activities. &#13;
&#13;
Unlike so many of the enthusiasms of youth, Roy never outgrew being a radical historian. He was at the founding MARHO meeting in 1973, a member of the Radical History Review Editorial Collective until 2000, and an Associate member of the journal until his death in October. He was the “Organizing Secretary” of the early MARHO Associates groups, charged with maintaining contact between far-flung outposts of radical historians and the mother-ship MARHO collectives in Boston, New Haven, and New York. Roy was one of the editors of the influential “public history” issue of RHR in 1981, the basis for the 1986 book Presenting the Past, which he edited with Susan Porter Benson and Steve Brier. Roy was heavily involved in the journal, but largely invisible when it came to bylines; beginning in the mid-1980s as half of the pseudonymous R. J. Lambrose, Roy was responsible for quite a bit of RHR’s wise-assery. &#13;
&#13;
If I don’t presume to understand Roy’s original embrace of the radical historian identity, I do know what being a radical historian meant to Roy in 2000, when the RHR organized a roundtable discussion on the occasion of the journal’s twenty-fifth anniversary. Roy and his original MARHO colleagues set out to establish an alternative to the OAH and the AHA, which in the early 1970s were resistant to change. But by the late 1990s, after the initial MARHO collectives had become a distant memory and a baffling acronym, the radical historians had also managed to influence, one might even say infiltrate, those existing organizations in significant ways. “To some degree, we’re running these things” Roy said, adding: “radical historians have had a profound impact on the shape of the historical profession in the United States. It’s easy to exaggerate this, but 2000 versus 1960—it’s an unbelievable change in the kinds of people who are in it, the kinds of issues that are being discussed, the whole set of things. Well, that’s a transformation we participated in.” Given that Roy was not inclined toward exaggeration or self-aggrandizement, we should take that assessment seriously.&#13;
&#13;
Since Roy tended not to toot his own horn, he did not talk on that day about his own institution building, which was an enduring part of his identity as a radical historian long after that intellectual designation had shifted its meaning. Roy understood that this was long haul, often tedious work, and he labored within universities and funding sources to nurture projects that were open and democratic, from putting archival resources on the Web for free to developing digital collecting projects and open source tools. Roy built “radical” institutions with people and funders who might be, at the least, nonplussed by that word.&#13;
&#13;
Roy’s scholarship, too, was collaborative and democratic in its outlook: he explored “who built America,” how New Yorkers used Central Park, and how Americans thought about history; he guided others in creating the kind of digital projects that he helped to pioneer. And his approach to the work mirrored its content: the only book that Roy authored by himself was his first. As a mentor and colleague, Roy was unparalleled in the history profession. The MARHO Associates were only the beginning: he nurtured a far-flung network of likeminded people throughout his career, and not for nothing did Dina Copelman dub him a “one man employment agency.”&#13;
&#13;
And so, “Roy as Radical Historian” encompasses virtually everything in Roy’s career: a lifelong commitment to connecting and collaborating, to working within the academy in order to expand historical scholarship beyond its borders, and to “writing” history in a myriad of ways that brought the experiences of ordinary Americans to the surface.&#13;
&#13;
Thanks, Roy. &#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="4691">
                <text>258</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4692">
                <text>Morning Coffee with Roy, Roy as Radical Historian""</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4693">
                <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="4694">
                <text>Ellen Noonan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4695">
                <text>Ellen Noonan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4697">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="80">
        <name>collaboration</name>
      </tag>
      <tag tagId="284">
        <name>MARHO</name>
      </tag>
      <tag tagId="233">
        <name>OAH</name>
      </tag>
      <tag tagId="280">
        <name>radical</name>
      </tag>
      <tag tagId="168">
        <name>Radical History Review</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="624" public="1" featured="0">
    <fileContainer>
      <file fileId="328">
        <src>https://www.thanksroy.org/files/original/b8d39d58f805182c782354308e5dee61.jpg</src>
        <authentication>a322f3201c3c9b982c76cd3c1d57e058</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="5207">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5208">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5211">
                    <text>1062</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="72">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="5212">
                    <text>1164</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="5201">
                <text>83</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5202">
                <text>Roy receiving the Lyman Award </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5203">
                <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="5204">
                <text>Eric Schkrutz</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5205">
                <text>Eric Schkrutz</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5206">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="220">
        <name>Lyman Award</name>
      </tag>
      <tag tagId="110">
        <name>red shirt</name>
      </tag>
    </tagContainer>
  </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>
  <item itemId="534" 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="4531">
              <text>Roy and I were accidental roommates at Columbia when we were freshmen, never having met though we grew up a few streets apart in Bayside.  We became fast friends, and eventually as juniors moved into an apartment on 112th St., just a few yards away from Tom's (later made famous by Seinfeld).  At some point, not long after we moved into our sublet (two bedrooms for about $100 a month, if that can be believed), we helped my girlfriend's family by taking one of a litter of kittens off their hands.  Roy suggested the name -- Rufus T. Firefly, after one of Groucho's characters -- and she (as we later discovered) was both the joy and bane of our bachelor life.  One night (very late, of course) Roy was writing a paper and crumpled up a sheet into a ball and threw it in the general direction of his wastepaper basket ... and a moment later Rufus was there with it in her mouth.  She had taught herself to fetch, and fetch she did, for as long as either of us had the patience to play the game.  We'd toss the paper ball, and she would tear off at the speed of light, grapple with the object, and then come loping back, ready for the next round.  She never tired of it -- though we certainly did.  Roy could not write a paper (and his were of legendary length) without starting and crumpling dozens of pages, and the mere sound of paper being balled up was enough to bring Rufus to plaintive, rapt vigilance at his feet.  I can't think of Roy to this day without thinking of Rufus fetching balls of paper in the wee hours of the morning.  I can't imagine Roy didn't think of this from time to time, just as I do ... though I wish we'd had the opportunity to reminisce and have a good laugh about it together.    </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="4525">
                <text>100</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4526">
                <text>Remembering Roy, c.1970</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4527">
                <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="4528">
                <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="4529">
                <text>Fred Schwarzbach</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4530">
                <text>Fred Schwarzbach</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4532">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="697" 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="11">
      <name>Hyperlink</name>
      <description>Title, URL, Description or annotation.</description>
      <elementContainer>
        <element elementId="28">
          <name>URL</name>
          <description/>
          <elementTextContainer>
            <elementText elementTextId="5957">
              <text>http://query.nytimes.com/gst/fullpage.html?res=9F04E3DB163AF936A25753C1A9619C8B63</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="5947">
                <text>80</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5948">
                <text>2nd Notice in New York Times</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5949">
                <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="5950">
                <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="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5951">
                <text>ROSENZWEIG--Roy . We mourn the untimely death of a warm friend, scholar, and Columbia '71 classmate. Paul Scham, Barry Leiwant, Bob Meyer, Ed Gartenberg</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="5952">
                <text>New York Times</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5953">
                <text>Friends</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="5954">
                <text>2007-10-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5955">
                <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="5956">
                <text>Hyperlink</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="196">
        <name>death</name>
      </tag>
      <tag tagId="6">
        <name>formal notices</name>
      </tag>
      <tag tagId="10">
        <name>Newyorktimes</name>
      </tag>
      <tag tagId="9">
        <name>notice</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
