6 10 162 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 am one of those teachers/adjuncts who benefited from Roy's ideas and imagination. CHNM materials were used in my classes and courses as soon as I heard about them! I remember a rickety av cart with about 15 wires, a discarded CPU and boat anchor monitor, an elderly projector and shaking internet that I wheeled into a classroom --the base reason was to get authentic and primary materials in front of my students and teach them what a wonderful set of tools they had - I firmly believe that he made a difference in how I was able to teach, and how my students were able to learn. How else was I going to find the resources to intrigue fashion design or athletic training majors in the required western civ course? Plus I was expanding my views of history and learning myself- When I met him for an interview in the first year of the new PhD program I was impressed with his ideas and goals- and still have a twinge of regret for not following that path- I am just now completing my PhD in Education and feel that his support for good teaching will be a part of what ever else I do. He was hospitable with the visitors I had occasion to bring over and never tired of talking about his work. Thank you Roy- you made a real difference to those of us on the base line as well as those at higher levels of the profession. mary 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 102 Title A name given to the resource Remembering Language A language of the resource eng Creator An entity primarily responsible for making the resource Mary Zamon Contributor An entity responsible for making contributions to the resource Mary Zamon Type The nature or genre of the resource Document teaching 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. Roy Rosenzweig was my colleague across town at the Center for History and New Media at George Mason. We saw each other at meetings and conferences four or five times a year; I had gotten to know him more personally when my partner worked at the Center for a while. He was warm and generous, obviously the kind of colleague and mentor we all want to have. Roy had an impressive career filled with distinguished accomplishments. In 2003 he was the second of only five recipients of the prestigious Lyman Award, for outstanding achievement in the field of digital humanities. Others can (and already have) spoken to what Roy did as a teacher, a historian, and as a friend. I want to talk about something he built, because even though I never spent much time at CHNM I do have some experience with running a center. Running a successful center is hard enough, but building one from the ground up is Herculean. And sometimes, it must seem, Sisyphean. Roy told me about CHNM’s history once, how it began in his office in the history department. And then moved to more palatial digs in a leaky trailer on the George Mason campus. Last year, however, the Center for History and New Media was given pride of place in the University’s new Research I building, a state of the art space that finally offered CHNM the facility it so richly deserved. The amount of invisible labor that goes in to something like that is vast, and not the kind of work that is rewarded (or usually even noticed) in the academy. There’s purchasing. For everything, from paper clips to computers to furniture. There’s hiring and personnel. There’s countless meetings with administrators and other stake-holders. There’s budget work. There’s payroll. There are fortuitous but mission-critical conversations with people in hallways. There’s strategic planning. And that’s before we even get to the Center’s research mission, but in order to pursue that mission there first must be funding. That’s where grant writing comes in. Roy wrote lots of grants and was remarkably successful; but grant writing is not glamorous work. Long, detailed narratives are the backbone of any proposal, and these must strike a pitch-perfect balance between precision and rigor and intellectual energy. Budgets have to be meticulous, laid out in advance literally to the last dollar. There’s all sorts of other documentation that must be prepared, collated, and formatted, all just so. I’m dwelling on these details because I imagine this was a large part of Roy’s days and nights: invisible, often painstaking but essential work whose rewards are apparent only years later, if at all. But here’s the thing: today CHNM has a staff of over forty populating that state of the art research space. Roy has had lots of help along the way, and the Center’s future leadership could not be in better hands, but if I had to say what Roy did in a sentence it would be this: he created a place where forty people now come to do things that are so exciting that I bet every single one of them has nights they can’t sleep because what they really want is to be back at the Center. This is the pay-off of all the budgets and forms, all the paperwork, all of the long, tedious hours of administrivia: you get to do things so exciting you can’t sleep. Roy created a space where those forty people, and many more in the years to come, will meet, talk, and build things together. Amazing and wonderful and important things. Thanks Roy, I’m only one of many who will miss you greatly. 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 31 Title A name given to the resource Who Built CHNM? 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 Matthew Kirschenbaum Contributor An entity responsible for making contributions to the resource Matthew Kirschenbaum Type The nature or genre of the resource Document chnm notSleeping roy 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 did not see Roy on a daily or even a monthly basis. Like everyone else, we were preoccupied with our own daily chores and routines. So, over the past 2 months it's been easier for me to busy myself with work and to pretend that Roy's still here, busily tending to his many projects and responsibilities over at the Center and beyond. Now that the semester's winding down and the season's first snow has arrived (at least here in northern Virginia), I'm might just be ready to stop and remember Roy instead of waiting to see him one more time--at one more faculty meeting, one more picnic, one more job candidate's dinner (coating a salad with salt). I relied upon Roy's presence (and am now feeling his absence) in so many ways, both spoken and unspoken. He was the soul of our department. During my first years on the job, Roy provided comfort and reassurance during moments of uncertainty and self-doubt. He was a much respected senior colleague, who listened like a trusted friend--a personal quality for which I will always be grateful and which I will never forget. Thank you, Roy, for everything--your humor, intelligence, creativity, integrity, dedication, and, most of all, your compassion and kindness. Peace. 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 124 Title A name given to the resource Two months out Language A language of the resource eng Creator An entity primarily responsible for making the resource Michael Chang Contributor An entity responsible for making contributions to the resource Michael Chang Type The nature or genre of the resource Document decency friend History Department kindness work https://www.thanksroy.org/files/original/aacbb7d45a33f79c45fa3ed48a4539e4.jpg 72fc8093775a390d18b6d2cacf798e21 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 480 Width 640 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 156 Title A name given to the resource Roy at the Crossroads 10th Anniversary Celebration 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 Here's a picture of Roy giving a short talk about the American Studies Crossroads Project and his work over the years with Randy Bass. Crossroads 10th Anniversary Celebration, American Studies Association Annual Meeting, November 11, 2004, Atlanta, GA Creator An entity primarily responsible for making the resource Michael Coventry Contributor An entity responsible for making contributions to the resource Michael Coventry Type The nature or genre of the resource Still Image Roy; Crossroads Project; 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. As a postdoc fellow last year at GMU, and a young historian just entering the field, I am deeply moved by all the stories and comments here, but they do not surprise me. I had already been deeply moved by Roy last year at GMU. I was a greenhorn in the department, just there for a year, and Roy took the time to meet with me about once a month, despite not only his busy schedule but the treatments for his illness. He was engaged, witty, thoughtful, and supportive. We bonded over being both Queens and Columbia boys, though we laughed at our different perspectives across the generations. And we had wonderful discussions about the state of American cultural history, the job market, book publishers, student culture at GMU, traffic in Northern Virginia, and digital history. I left meetings with Roy (always always over coffee) feeling energized and hopeful about being a historian. And I learned by his example how to be a dedicated colleague. I suspect that Roy's professional legacy will live on through these countless meetings he had with those around them: little bits of his tremendous energies are scattered about in all of us who were able to interact with him. Even with my brief time getting to know Roy just a little, I am so very sad about this loss. He was a very special scholar and person. I send my condolences to those who knew Roy well and I just wanted to add one more voice to the chorus of this celebration of his career and life. 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 97 Title A name given to the resource How To Be a Good Historian 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. Creator An entity primarily responsible for making the resource Michael Kramer Contributor An entity responsible for making contributions to the resource Michael Kramer Type The nature or genre of the resource Document Colleague Historian mentor Professional Legacy 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. This isn't a story exactly, it's some observations. There are lots of comments here about Roy's courtesy and thoughtfulness and kindness, his generosity. He had all those things to a really remarkable degree: that's all true. But he wasn't exactly self-effacing. Roy was relentless at getting what he wanted. He worked away and worked away on all fronts at once, and I realized early on that if Roy wanted something A: he was usually right about it, and B: he would not quit till it happened. He was mentally tough and tenacious, but he was also wise and smart and saw a couple moves ahead of most people, so there was almost always point C: it's going to benefit a lot of other people, you might as well get on board. That's not self-effacing, it's something more interesting and unique. Also although Roy was a very strategically patient at getting what he wanted he was basically an extremely impatient guy. He was pretty good at concealing it but he got impatient easily and he generally responded to impatience by multitasking. The laptop was practically invented for Roy, so he could do email when meetings got slow. He was scathingly funny when someone really irritated him. It was easy to get him mildly irritated, although his basic kindness mediated it. But when he got really bugged he was pretty funny about it. He was especially irritated by mindless adherence to procedure and by moments when stubborn tradition shut down ideas Roy had no taste at all for formality and he was never, ever, pompous or haughty. He was more likely to be distracted and slightly oblivious except when you had his full attention, in which case he was all the things people say he was. I remember telling my parents about Roy and saying that you'll ever know, when you meet him, what a big deal he is. There was no self-promotion. He promoted the work, and the work he did was almost always done in community with others He was extremely skeptical about the profession--about snobbery masquerading as standards, about the bubble reputation, about the ways the familiar often obscured the talent. Lot of people feel ambivalent about their profession, but Roy's skepticism never turned into alienation, and he never stopped working to improve custom he thought were useless and corrupt. That to me is the most admirable thing about Roy--not that he was some kind of saint, not his many gifts, but that although he was an impatient, often single minded and stubborn, driven guy, he learned how to blend those qualities and turn them into community, instead of selfishness. He was flawed like we all are but he was an unusually morally conscious man, and keenly aware of how to make his weaknesses useful to all those around him 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 69 Title A name given to the resource A complex guy 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. 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 Document impatient single-minded stubborn https://www.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 https://www.thanksroy.org/files/original/cb125756ad49f41cad4f33bfcee92e61.mp3 363cc1436ebe7a9186d4b17aa8d8f4de Sound A resource whose content is primarily intended to be rendered as audio. 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 36 Title A name given to the resource alt.blues.roy 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 A very rough first take--I'll probably polish it up when I get time. Although to be honest, writing a piece of music for Roy is sort of like painting a landscape for Ray Charles. Roy would appreciate the gesture, I'm sure. 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 Sound blues music roy https://www.thanksroy.org/files/original/a1b4f626d9303fac6c065e7ae7f39d29.jpg 70732bd393960d6fc574a297a17bb538 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 484 Width 443 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 20 Title A name given to the resource fashion sense 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 Roy liked not to have to think about clothes, and he was a man of habits. Left alone, he'd of worn nothing but jeans and red shirts 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 fashion redshirt roy style