1
10
6
-
https://thanksroy.org/files/original/4a2e6458cdaede391fd15ed237b85502.jpg
df378dc919789f7d4ea3fbdfba1c738e
Omeka Image File
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.
Bit Depth
8
Channels
3
Height
424
Width
600
Still Image
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.
Dublin Core
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/.
Identifier
An unambiguous reference to the resource within a given context
90
Title
A name given to the resource
Jackson Street Office
Language
A language of the resource
eng
Rights
Information about rights held in and over the resource
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.
Description
An account of the resource
In Roy's office in their house on Jackson street. The site of many collaborations for many people
Creator
An entity primarily responsible for making the resource
Mike O'Malley
Contributor
An entity responsible for making contributions to the resource
Mike O'Malley
Type
The nature or genre of the resource
Still Image
collaboration
jackson street
study
-
Document
A resource containing textual data. Note that facsimiles or images of texts are still of the genre text.
Text
Any textual data included in the document.
“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.
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.
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.
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.
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.”
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.
Thanks, Roy.
Dublin Core
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/.
Identifier
An unambiguous reference to the resource within a given context
258
Title
A name given to the resource
Morning Coffee with Roy, Roy as Radical Historian""
Rights
Information about rights held in and over the resource
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.
Creator
An entity primarily responsible for making the resource
Ellen Noonan
Contributor
An entity responsible for making contributions to the resource
Ellen Noonan
Type
The nature or genre of the resource
Document
collaboration
MARHO
OAH
radical
Radical History Review
-
Document
A resource containing textual data. Note that facsimiles or images of texts are still of the genre text.
Text
Any textual data included in the document.
I played comic second fiddle to Roy at George Mason for years. It was really obvious from the first time I met Roy that he was a really smart. You could see that right away. But a lot of academics are really smart—smart is sort of cheap in the way a beauty queen is beautiful—it’s look at me, and primping. And Roy wasn’t smart in that way; he was smart in a very unusual way. He was smart in the way he approached building community. George Mason was a wonderful place to work. Our Department was terrifically collegial and pleasant, and most of that was due to Roy. It was the way Roy worked. He had enormous respect for people in that department.
When I got there--George Mason is kind of a preposterous place in some ways. Well, all Universities are a little preposterous. But it reflected its origins as kind of a branch campus of UVA, and a lot of the faculty in that department had no pretensions to doing any research at all. They didn’t think of themselves as researchers, they were teachers primarily, and my training of course—I thought I was a hotshot academic—was to be contemptuous of that kind of thing. You now—that’s not what it’s about, it’s about the research. And Roy never reflected that attitude: although he himself was prodigious in his work he always treated all his colleagues at George Mason with enormous courtesy and respect he built a culture of mutual respect that was really striking. It wasn’t one of those two-tiered systems where one person gets all the influence…well actually it was: Roy got all the influence, but other than that it was pretty good!
But the way he got it is what’s interesting. I had come from a department where Jr. faculty were forced to enlist themselves in feuds that dated back to the Taft administration; their origins were lost in the mists of time: there was none of that at George Mason. None of that was enabled. And I think how did he do it?
We had department meetings about three times a semester and they were remarkably pleasant. They were usually funny they were usually short, but whenever things did get a little heated or a little tense, or there’d be a problem that’d be particularly knotty, everybody would start to look at Roy, who usually wasn’t saying much. My job was to make smart-ass comments; his job was to sit quietly, and then you’d see people start to look at Roy. “What’s Roy going to say?” “What’s Roy gonna say?” And then he would invariably say something that was extremely useful. Unlike most of us he didn’t take the opportunity to speak as a chance to lay waste to his opponents or settle old scores or denounce: he didn’t do any of that stuff; he would come up with some effective solution
But he would never say the solution: he would always say “well, you know, we could do this.” And people would say “hey, we could! That would be really good!” And pretty soon, that’s what we would be doing.
Now, I don’t want to make him sound like some kind of saint—he wasn’t some kind of some kind of namby pamby goody goody guy either: he had a scathing wit, as you all know. He was happy to settle grudges and lay waste to his opponents after the meeting was over, he was happy to do that sort of thing, and it was a lot of fun, actually, I loved those moments. But the thing that was most—as you now, he was a noodge, he never quit when he wanted to make something happen. He had no concept this thing you call the “weekend” or this thing you call “the holiday.” I once got a request from him to have a meeting—on Christmas day. And I said “Roy I’m gonna be in Philadelphia visiting my family on Christmas day” and he said, “well, could we do a phone conference?” No, we can’t do a phone conference.
The thing that was most annoying about Roy, which was, I think was the key to how he worked was he would never tell you what he wanted. I was happy—I realized early n that Roy was usually right. I had extravagant schemes, and elaborate interpretations that were beautiful castle sin the air, Roy had practical solutions, and he was almost always right and I figured that out fairly early and I’d want to say “Roy, look, just tell me what you want to do, and I‘ll go along; I’m happy to go along with you; just tell me what you want to do. And he never would, because he loved the idea of consensus, and he would move mountains to create the illusion that everybody agreed happily and spontaneously. This is sort of what he did; he would do everything to make that happen, He really believed in it.
It must have been very difficult in some way to be Roy: to know the right thing to do, and be surrounded by lunatics who had no idea what the right thing—imagine the burden that must be! But he would work patiently to bring about this consensus, and the way he did it was not, in the community of George Mason, making his own agenda or his own personal grievance the first order of business. And that’s why he would never tell me where he wanted to end up. Partly he didn’t always know, but partly he didn’t want to make his agenda the first order of business; he didn’t want to make denouncing his opponents the first order of business, he didn’t want to make posturing what it was all about.,
So he built this culture that was extraordinarily collegiate, extraordinarily pleasant, extraordinarily comfortable. He did the scut work that people of his stature typically didn’t do. You now, we had a picnic every year; Roy would stay after to clean up. He was humble in that way—he didn’t put on the airs that someone of his stature was entitled to. In that way too he didn’t put himself forward: he didn’t put his own agenda and his own opinions forward.
It was an extraordinary experience to be in a department with him: it was for e a completely new way of looking t how academics can conduct themselves, and how the life of a department can be conducted. It was extraordinary—I thought you had to be sort of bitter and infighting—I thought it was a requirement for the job! And it was a revelation to see otherwise. Every day at George Mason, every day, people walk around and say: “What would Roy do? What are we going to do with this problem? What would Roy do? How would Roy get to the answer?” It’s extremely difficult to do, but it’s a question we’ll never stop asking ourselves.
Dublin Core
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/.
Identifier
An unambiguous reference to the resource within a given context
257
Title
A name given to the resource
Coffee with Roy, Roy and George Mason University""
Rights
Information about rights held in and over the resource
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.
Creator
An entity primarily responsible for making the resource
Michael OMalley
Contributor
An entity responsible for making contributions to the resource
Michael OMalley
Type
The nature or genre of the resource
Document
Coffee with Roy
collaboration
community building
Department Meetings
George Mason University
History Department
Mediator
-
Document
A resource containing textual data. Note that facsimiles or images of texts are still of the genre text.
Text
Any textual data included in the document.
I can’t remember how or exactly when I met Roy. I imagine it was at the MARHO table at the AHA, sometime in the late 1970s when I was finishing my PhD. Sue Porter Benson might have introduced us, or perhaps I had just signed up to sit at the table the same time as he did. He seemed always to be at the MARHO table then, before he started serving on every committee in sight. In those days, there were a lot of leftist men who hadn’t quite gotten the gist of feminism, but Roy was a welcome exception. Just when I was about to utter some universal complaint about macho leftists or about one more session on labor history that failed to consider women or gender, Roy would pop into my head. Then I’d have to take a deep breath and realize that there were a few good men.
It wasn’t just that Roy acknowledged women’s history. He also embraced what I thought of as feminist process, though he didn’t articulate his style in those terms, or any terms--he just got things done in an incredibly collaborative and unassuming way. I remember especially a moment in 1991, when we served together on the OAH Program Committee. There were lots of proposals for complete sessions that year and a big stack of single paper proposals as well. Most of the committee was willing to focus on the complete sessions and only move to the single papers if we really needed to add speakers or sessions. But Roy cornered me at the first coffee break and said we should volunteer to go through all the single proposals and create sessions because otherwise lots of graduate students and young faculty who didn’t have the networks to produce full sessions would get lost. So we did just that—and it yielded some great sessions. On so many occasions like this one, Roy did the invisible work that makes such a difference and refused any special acknowledgement for his efforts. He was a mensch.
Around the same time, I was serving as an outside reviewer for The Park and the People. In that capacity, I discovered that Roy’s passion for collaboration was just as strong when it came to research. Roy (and his co-author, Betsy Blackmar) actually seemed excited to get suggestions for revisions. I think this was the first time that I let a press give out my name to the authors of a manuscript, and they were so appreciative of my comments that I foolishly thought their response was typical. (I soon learned otherwise, but I was forever grateful that they had taken my ideas seriously. It gave me greater faith in my critical abilities and served as a model for how to embrace criticisms and suggestions about my own work.)
In addition to Roy’s generosity and collaborative spirit, he was excellent at persuading people to take on extra work for a good cause since he was always doing more than his share. The point was reinforced over and over again as I crossed paths with Roy in MARHO, the OAH, the ASA, History Matters, and especially, the American Social History Project. When I was recruited to join the ASHP group revising Who Built America? in the mid-1990s, it was Roy who called. I was overwhelmed with commitments of various kinds at the time and would have turned anyone else down. But Roy always seemed to be juggling more obligations than anyone else and doing it so well. Plus, he was listened so carefully to my concerns and anxieties that by the end of the phone call, I’d said yes. I’m glad I did.
Joining the WBA? circle gave me the chance to collaborate with Roy—and Steve, Josh, Chris, Nelson, Susan, Ellen, and Pennee. This was a project that highlighted Roy’s intellectual and technological creativity and his amazing ability to find humor in the midst of crisis and chaos. As we await publication of the third edition, I still expect an email from Roy to pop up in my inbox. (I’ve studied the nineteenth-century “spiritual telegraph,” and if anyone can get it to work, it’s Roy.) Like so many of us, it’s hard for me to think about a world without Roy. But then we don’t quite have to since he’s still present in so many places—in books and websites and digital archives; in the ways we think about research, writing, and collaboration; in the tools we use to teach; in our commitments to history as politics; and of course, in our hearts.
Dublin Core
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/.
Identifier
An unambiguous reference to the resource within a given context
82
Title
A name given to the resource
A few good men(sches)
Rights
Information about rights held in and over the resource
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.
Creator
An entity primarily responsible for making the resource
Nancy Hewitt
Contributor
An entity responsible for making contributions to the resource
Nancy Hewitt
Type
The nature or genre of the resource
Document
collaboration
mensch
WBA?
-
Document
A resource containing textual data. Note that facsimiles or images of texts are still of the genre text.
Text
Any textual data included in the document.
Of all the amazing qualities Roy possessed -- intelligence, generosity, creativity, industry, wit, and so many more -- the one that always stood out for me was trust. Roy trusted in history. He trusted in hard work. He trusted in fairness. Most of all, he trusted in people.
Roy was a collaborator. He was brilliant on his own, but I think he was happiest and at his best when he was working with other people. And people flocked to him.
I think Roy was able to gather so many friends and colleagues around him because he trusted them, often without prior cause and always without prejudice, and so people trusted him back. Roy showed us that the way to gain trust is to give trust, which is the same thing as saying that the way to be loved is to love. It's the best work lesson and the best life lesson I have ever learned, and Roy was the best teacher.
I trust and love and miss him very much.
Dublin Core
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/.
Identifier
An unambiguous reference to the resource within a given context
44
Title
A name given to the resource
A Matter of Trust
Language
A language of the resource
eng
Rights
Information about rights held in and over the resource
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 <em>Thanks, Roy</em> in all media in perpetuity. If you have so indicated on the form, your material will be published on <em>Thanks, Roy</em> (with or without your name, depending on what you have indicated). Otherwise, your response will only be available to approved researchers using <em>Thanks, Roy</em>. 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.
Creator
An entity primarily responsible for making the resource
Tom Scheinfeldt
Contributor
An entity responsible for making contributions to the resource
Tom Scheinfeldt
Type
The nature or genre of the resource
Document
collaboration
roy
teacher
trust
-
Document
A resource containing textual data. Note that facsimiles or images of texts are still of the genre text.
Text
Any textual data included in the document.
Where to begin? It’s the only possible response when asked to remember Roy Rosenzweig. Academics are fortunate if they are able to become pioneers or innovators in a single field; Roy managed to found or advance at least three fields: social history, public history, and digital history. And we often suspect that pioneers and innovators have character flaws associated with the dogged pursuit of the cutting edge: narcissism, aggression, humorlessness. Yet everyone who knew Roy was amazed at his unparalleled combination of brilliance, insight, and incredible hard work with humility, generosity, and laugh-out-loud wit.
Eight years ago I received a call from Roy, who had heard through a mutual acquaintance that I had moved to Washington. I only vaguely knew of Roy, and had no idea why he should want to talk to me, but nevertheless agreed to meet him for lunch. I’m so profoundly thankful I answered his call.
Roy and I ate at a restaurant near his house and had some nice conversation. I thought little of our casual meeting until a year later, when Roy called me to say that he had just gotten a grant and had remembered a few points I had made over lunch and how relevant they were to the grant proposal. The only thing I could only remember from a year earlier was that Roy was bursting with energy and ideas and had consumed more coffee over lunch than I drink in a week. We met again for lunch and by the end of the meal he had convinced me to come work with him.
That’s how it began for me, and for countless others. Sitting on a panel with Roy at a conference, meeting randomly over coffee, receiving a congratulatory email from him about an article you had written. No matter how trivial the reason behind the first contact, Roy would remember you, and he would often move these minor encounters—the kind most of us have every day and think nothing of—onto a path toward collaboration and friendship.
I know of no one with as large an address book and as many friends as Roy. But he didn’t just collect these acquaintances superficially, for show or for his own career ends like so many people do on Facebook or LinkedIn. As his social histories of the United States also emphasize, he viewed every human being as a special resource who brings unique talents and ideas into the world, and he liked nothing more than to connect people with each other.
Almost every topic of conversation prompted a welcome referral from Roy: “You should talk to my friend so-and-so, who has done some really interesting work on that subject.” The history of family photos? “She wrote a great article on that.” Standards for library catalogs? “Met this guy at the Library of Congress.” Byzantine art? Documentary filmmaking? Preservation of eight-track tapes? Him, her, and you’re not going to believe this but here’s an email address for you. Now go contact them.
But Roy didn’t just bring his many acquaintances together. He reveled himself in collaborating with others. Roy found it deeply unfortunate that unlike in the sciences, the humanities suffered from a serious lack of collaboration. He scoffed at the mythical ideal of the intellectual toiling alone on the great book. Roy co-authored over a dozen major works, not to mention the scores of highly collaborative digital projects at the Center for History and New Media, which he founded at George Mason University in 1994.
A typical but still remarkable moment occurred when Roy received the Richard W. Lyman Award (presented by the National Humanities Center and the Rockefeller Foundation) in 2003 for “outstanding achievement in the use of information technology to advance scholarship and teaching in the humanities.” He got up on stage, used his computer to project a giant list of names onto a screen, and said, “These are all of the people I collaborated with on the projects that this award honors. These are the people that did the work, and I want to thank them.”
Of course, that was just Roy being his usual humble self. Roy’s collaborators will readily admit not only how wonderful but also how daunting it was to work with him. To paraphrase Paul Erdös, Roy was a machine for turning coffee into publications and websites. With his incredible mind and a large coffee nearly always by his side, he was able to produce such a wide and deep array of creative works. When we were writing a book together I would slowly plod along while insightful, beautiful prose seemed to pop off of his laptop at a disturbingly rapid pace. Working with him on a project forced you to elevate yourself, to do the best you could do.
Long before Roy became ill, the staff at the Center for History and New Media would ponder (when Roy was out of the room) what we would do decades hence, when we expected Roy would finally leave this world. In the spirit of Roy’s humor, some of us decided that we would simply have to preserve his brain in a giant vat of fresh-brewed coffee. Others took their cue from science fiction and thought we could transfer his mind onto silicon for the continued benefit of future generations.
If only we could have done so. But perhaps in a partial sense that is what has happened over the last decade. Roy’s thoughts and vision sit on the Center for History and New Media’s server, silently connecting with thousands of people every day, and his books and articles connect with thousands more.
If only those people could have met Roy Rosenzweig in person. He would have liked to have had coffee with them.
Dublin Core
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/.
Identifier
An unambiguous reference to the resource within a given context
15
Title
A name given to the resource
Remembering Roy Rosenzweig
Rights
Information about rights held in and over the resource
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 <em>Thanks, Roy</em> in all media in perpetuity. If you have so indicated on the form, your material will be published on <em>Thanks, Roy</em> (with or without your name, depending on what you have indicated). Otherwise, your response will only be available to approved researchers using <em>Thanks, Roy</em>. 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 <em>Thanks, Roy</em> you release, discharge, and agree to hold harmless <em>Thanks, Roy</em> 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 <em>Thanks, Roy</em>\'s use of the material, including, without limitation, claims for violation of privacy, defamation, or misrepresentation.
<em>Thanks, Roy</em> has no obligation to use your material.
You will be sent via email a copy of your contribution to <em>Thanks, Roy</em>. We cannot return any material you submit to us so be sure to keep a copy. <em>Thanks, Roy</em> will not share your email address or any other information with commercial vendors.
Creator
An entity primarily responsible for making the resource
Dan Cohen
Contributor
An entity responsible for making contributions to the resource
Dan Cohen
Type
The nature or genre of the resource
Document
chnm
coffee
collaboration
Digital History
personal recollection