Tag Archives: group project updates

ReadingRebus Group: Final Project Report

ReadingRebus: Performance Report/White Paper

Created collectively by Patricia Belen, Bianca F.-C. Calabresi, Rachel M. L. Dixon, Matt, Ostap Kin

https://readingrebus.com/

I. Group Members: 

Patricia Belen: Project Concept / Designer / Developer

Patricia is the creator of ReadingRebus and is the project’s designer/developer. She is responsible for the website design, layout, coding, content planning, content creation and UI/UX – helping to create new ways of exploring historical rebuses.  Patricia created our social media accounts and helps maintain them by posting content and tangling with Twitter.  Patricia also contributed an essay and found much of our initial rebus sources and open-access collections.

Bianca F.-C. Calabresi: Project Manager / Editor

As Project Manager for ReadingRebus, Bianca designed and managed our workflow chart, posted most of the weekly group blog content, and supervised written submissions by the group.  On an ongoing basis, Bianca provides material for social media outreach and reviews all content for typographical errors, factual inconsistencies, and infelicities of style both before and after postings, maintaining a running list of corrections and emendations.  She contributed two essays on rebuses and located most of the rebuses and reference materials hidden behind paywalls or in limited-access research collections.

Rachel M.L. Dixon: Multilingual Puzzle Researcher / Developer

Rachel joins ReadingRebus as a multilingual puzzle researcher, a project that merges many of her research foci in one delightful place.  Rachel is the public face of the project, presenting our materials in class and at DH events. Along with her other contributions, Rachel handles outreach to the puzzle community, manages our group Zotero and collection scoring spreadsheet, and makes corrections directly on the website.  Rachel contributed our central explanatory essay and the vast majority of our French and Spanish rebuses, which she also translated.

Matt: Researcher / Analyst

For the ReadingRebus project, Matt’s role primarily covers seeking out rebuses of note and information on rebuses and their interpretation. Their primary contributions to the final product consist of writing in the form of reference tables, interpretation guides, and analyses.  Matt contributed two essays and a long catalogue entry, two more on heraldry and coats of arms, for which they are exclusively responsible, as well as a guide to symbols in heraldry and rebuses at large.

Ostap Kin: Researcher / Institutional Outreach

Ostap contributed essays on the trajectory of rebuses and digital online collection of rebuses, and organized and edited the bibliography of suggested primary and secondary sources for users’ future research.  As director of institutional outreach for ReadingRebus he located and approached archives with unpublished rebuses, which we hope to pursue further as institutions open up.

II. Project Narrative:

Overview

The ubiquity of emojis in our digital chat conversations invites interrogation into rebus writing as a predecessor to the emoji and an interdisciplinary area of study, intersecting many aspects of digital humanities. By definition, an emoji is a pictogram representing an object; an ideogram representing an abstract concept; or an emoticon representing human emotion. Pre-dating emojis, a rebus uses a symbol to represent a sound, syllable, part of a word, or whole word, regardless of its meaning. Rebus writing combines visual elements with letters, words, and phonics to create puzzles which need to be deciphered and translated in order to understand their meaning. Coinciding with France’s invasion of Egypt and subsequent discovery of the Rosetta Stone in 1799, rebus writing enjoyed a resurgence as a form of playful and satirical expression in late-18th– early-19th-century Europe and America. Circulating in printed broadsides, advertisements, letters, reading exercises, bibles, picture puzzles, and newspaper games, rebus writing became distinct from its ancient origins and early modern functions, entering more expansively into the daily lives of children and adults as visual vernacular.

ReadingRebus (RR) is an online, visual archive of primarily late-18th– early-19th-century European and American rebus ephemera, that includes research into their history and cultural uses.  While focusing predominantly on this period, the project leaves open possibilities to expand its temporal and geographical scope through additional visual artifacts, historical research, and multilingual examples, some of which we have already begun to provide. The project aims to make a core group of historical rebus ephemera accessible in an engaging, collaborative, and interactive format to scholars in diverse fields as well as to members of the general public – opening up new possibilities for discovering how we see and interpret visual information. Each rebus puzzle is treated as an interface of inquiry to conduct close reading experimentations, translations, and ambiguous interpretations by audience participants. RR challenges the notion of traditional texts by using humanistic qualitative analysis, while also contributing to the history of language, visual literacy, and visual communication, connecting cuneiform and hieroglyphs to contemporary, digital emojis.

Equivalent online rebus sites

While we looked at many digital resources while working on the project, we found that discussions of rebuses online are infrequent.  Primarily appearing in blogs, they tend to present a single rebus or two and their specific histories rather than an investigation of rebuses more broadly or deeply.  While the sites often provide written solutions to the puzzles, the inclusion of guides to solving rebuses are rare and always static, unlike our site, which focuses on the ability to compare rebuses, by genre, by subject, by chronological or geographical similarities, and to acquire a rebus “vocabulary” through interactive experimentation and play, thanks to the use of hotspot areas for each rebus in an artifact.

Some rebus sites focused more fully on rebus construction or creation, and were somewhat removed from any historical context, such as the rebus-o-matic site additionally listed in our bibliography. In addition to blogs and other resources, there are instances of rebus-solving communities found on social posting sites such as Reddit and Stack Overflow.

In short, our project does fill a number of niches. Firstly, it is a site that focuses on rebuses, and a site that focuses on rebuses for the sake of rebuses, rather than a site with a focus on some other topic that brings rebuses briefly into conversation with that topic. Secondly, our project grants users a place to engage with rebuses in manners that other places where they are located don’t necessarily offer at all. Finally, our project offers a decent volume of scholarly content related to rebuses, along with metadata on the rebuses present on the site.

Critical material on rebuses

Recognizing the long history of writing on rebuses and their relation to semiotics, we provide a bibliography that extends back to the 16th century, tailored both for a general public and for audiences interested in a particular era or type of rebus as well.  We posted several research essays (500-1500 words) that provide an overview of rebuses, their history, materiality, and function. Several of our research pieces analyze rebuses as a whole in a more critical or deconstructive manner. These pieces examine where rebuses stand as analyzable works, the way one must consider a rebus in order to critically analyze a rebus, the unique qualities and challenges of analyzing rebuses specifically, and the interactions between author or creator and rebus. While “what is a rebus?” is a question they don’t quite pose verbatim, they are meant to serve as something of an aid to those who ask those questions, in addition to those curious about the theory behind rebus analysis. We also present essays which address particular aspects of rebuses (i.e. rebuses in and as heraldry, code as a form of rebus writing).  In addition, we chose to highlight Rauchenberg’s Rebus in relation to traditional rebuses and, to include an essay on a neglected set of verbal rebuses by the 18th-century poet Phillis Wheatley Peters placing her work in the context of  popular acrostic rebuses published widely in Britain and its American colonies in that period. Thus our critical interventions into this field aim both to broaden the appeal and understanding of rebuses to a wider audience and to demonstrate how the rebus form may intersect with and impact current and emergent scholarly fields, like Africana and American studies and print history. Finally, our bibliography offers a number of resources which pay special attention to rebuses: including rare books which featured rebuses a few centuries ago as well as different blogs which use rebuses now; in order to help users to see a trajectory of rebuses and their presentations in published materials.

III. Audience:

Many people have found the rebus project of value given the rebus’s several overlapping qualities (play, poetics, aesthetics, materiality, among others), as well as its long existence spanning several cultures. ReadingRebus will be of particular interest to scholars in fields as diverse as linguistics, history, folklore, game studies, education, communications, design studies, and visual arts, as well as to members of the general public interested in puzzles, puzzle-solving, emojis, and crafts.

Moreover, as happens with all sorts of riddles, rebuses may attract the attention of virtually everyone, because rebuses often contain all necessary ingredients to do so. First, one deals with words and meanings which are coded, hidden; second, often when one deals with rebuses one encounters singularly  aesthetically pleasing and simply beautiful works. Third, looking at rebuses often means looking at a certain epoch and allows one to notice how that epoch might be reflected in its rebuses.

After exploring the project website, users will ideally become more familiar with and more knowledgeable about rebuses, their history, and the distinctive aspects of their existence. There is also of course the goal of keeping the site both intellectually stimulating and enjoyable in terms of entertainment for users. The fact that users can contribute their own translations, comments, and thoughts grants them a chance to feel personally involved with and attached to the project and what it is trying to accomplish.

IV. Project Activities:

ReadingRebus Workflow spreadsheet for February to May

Initial Goals  (https://dhpraxis21.commons.gc.cuny.edu/reading-rebus-work-plan/)

Outcome 1: Establish and start Social Media Accounts: Twitter, Instagram (possibly Tumblr): Weekly postings to be determined on Sundays and uploaded.  Rachel & Matt to maintain. by March 8

Outcome 2a.  Corpus of 15-20 18th-&-19th-century rebuses with permissions to reproduce: Ostap to contact archives & special collections and oversee permissions.  Rachel to explore French collections.  Bianca to explore Italian & Spanish supplementary material. by March 29

Outcome 2b: 2-4 essay-length general analyses of rebuses history, theory, material production, and relation to other visual culture (heraldry eg).  Matt, Rachel, Ostap, Bianca to provide. by April 12

Outcome 2c: specific short pieces (“wall labels”) for each featured rebus, with links to further information.  Matt, Rachel, Ostap, Bianca to provide. by April 19

Outcome 3: design and upload the following web pages: Patricia to design & develop with content providers:

About/intro: Rachel  by May 3

Contact: Bianca & Patricia by April 26

How-to-rebus & interactive tutorial: Matt & Patricia by April 12

Object pages: Rachel, Ostap, Bianca by April 19

Further Reference & Bibliography: Ostap, Rachel, Matt, Bianca by April 26

Outcome 4: circulate, revise, edit, submit group project report: Bianca by May 17

Research

Our research was mostly conducted individually based on our specific interests in heraldry, poetry, multi-lingual examples, archives, materials, art and design, puzzles, and more. We spent the first weeks of the project reaching out to special collections in hopes of finding unique examples that could be digitized for the website. Unfortunately, the situation with Covid left most of our emails unanswered. One institution, the Connecticut Historical Society, did supply a rebus but it lacked context and information so did not end up on our website. However, conducting searches through museum websites, and public collections such as the DPLA, Library of Congress, NYPL, HathiTrust, Europeana, and the Internet Archive resulted in an abundance of rebuses and resources.

As a group, we gathered examples, some were saved in our shared Google folder, others were saved privately on Zotero, our personal computers, spreadsheets, docs, lists, etc. We shared our findings during our bi-weekly meetings. In March, a decision was made to narrow down our findings and finalize the information needed for the website. We settled on a group of metadata for each rebus sample. We tried documents for each rebus but after finding that too timely and cumbersome, we decided a single spreadsheet would be easier to manage. The spreadsheet allowed us to place the rebus link, metadata and rating system all in one system.

For each rebus on the spreadsheet, each member of the group examined and rated the item in question’s quality on a numerical scale, with higher numbers indicating the best quality. Generally, an item with a score of 3 was one that the group member rating it considered to be of significant enough quality to include. Thus, for the sake of feasibility, we only included items that had an average score (that is, the mean value of each group member’s score) of 3 or greater.

Going into more detail, quality within the context of this rating system was based on content, image resolution and clarity, the amount of available data on the item, and a small degree of personal opinion. With regards to the lattermost of these, as well as the relative subjectivity of this system and the existence of human error, the choice to average the scores was made. In addition to taking each group member’s rating into account equally, by averaging the scores together, we were able to choose rebuses that the majority of us considered good.

Of course, if the threshold was set very much below 3, there would have been no way to include each and every item we found. In fact, early on in the project before our scope was more refined, there was a period where we discussed adding all sorts of content, such as rebus-like items and numerical wordplay in alphabets other than the Latin alphabet (such as Hebrew gematriot).

With regards to our research infrastructure, it was fairly freeform, especially at first. We mostly sought out varied content in our respective areas of interest and expertise, recorded it, and made the rest of the group aware of our findings. In doing so, we were not only able to keep our fellow group members in the loop about our current business, but we were also created a situation where the exploits and methods of one of us could prompt or otherwise inspire another one of us to try new avenues of research or explore new sources.

However, some of our research did not bear fruit. Certain sources were barren of usable content, or presented problems in terms of accessibility or usability. For instance, one group member attempted to mine Luigi Serafini’s Codex Seraphinianus for the purposes of uncovering rebus-like content in a language that exists only in a single place – in this case, the book in question. Unfortunately, there simply wasn’t all that much to be found.

On the other hand, other sources were extremely helpful and provided an abundance of rebuses and information on them. The Bodleian Library’s John Johnson Collection contained a very solid collection of Valentine’s-Day-themed rebuses, for instance, and Arthur Charles Fox-Davies’ A Complete Guide to Heraldry contained not only a wealth of information on heraldry as a whole, but roughly 30 coats of arms and images of other heraldic items, such as tabards and crowns that were considered at some point for use on the site.

Ultimately, while we only followed our work plan loosely and in some cases produced material a week or two after our self-imposed deadline, having the work plan provided a useful reference point in our discord and email conversations and our extra-curricular Sunday-evening reviews.  The group was remarkably diligent in showing up to those standing meetings, which meant that we knew no one could get too lost or far behind without the offer of support and that we could discuss and reassign tasks in real time as needed.

V. Accomplishments:

The ReadingRebus website is built on the WordPress platform. WordPress is an ideal choice for a content management system because it has built-in database capabilities, flexibility of design through theme customization, ease of use for team members to enter information through its interface, and a community of users and plugin developers devoted to its open-source format.

Prior to developing the website, we created an animated logo to post on social media to create excitement in anticipation of the website. The animation replaced parts of “Reading Rebus” with visual symbols to inform viewers what a rebus is and how it is used.

ReadingRebus logo: girl reading and Re+a bus

We developed a custom WordPress theme, created to fit the rebus content we needed, rather than forcing the rebus content to fit within an existing theme. The aesthetic of the website was designed to be whimsical and playful, yet informative and easy to use. The interactive features envisioned in our original proposal to create a “digital playground” were successfully added.

ReadingRebus Home pageThe homepage highlights, through text and visual examples, what a rebus is. Using contemporary icons in place of words, the viewer can hover over the icons to reveal their verbal equivalents and gain an understanding of how rebuses work. In addition, we include the dictionary definition of “rebus” from the OED and a prominent link to the essay “What We’re Talking about When We’re Talking about Rebuses” which introduces how and why rebuses came to be. The homepage also features rebuses culled from our curated collection and links to our research essays. Each time a viewer revisits the homepage, they are presented with a different group of rebuses and essays.

ReadingRebus Rebus collection pageThe Rebus Collection featured 37 rebuses, grouped in nine categories to start, arranged in a grid format with thumbnail image preview and title of the rebus. Categories were established based on the physical and generic characteristics of the rebuses, but also what we felt were good points of entry for the audience. A viewer can click on “advertisements” or “letters” to see only those rebuses. We have also included “unsolved” as a category to prompt those who are interested to solve rebuses on their own. Through our research, we have discovered many rebuses not translated which we offer as a way for the audience to become involved in the project. As more rebuses are added to the collection, categories may also be added.

Clicking on a rebus will bring the viewer to the detail page of that rebus that features a larger image, title, and metadata (Author/Artist, Publisher, Date, Description, Language, Repository). The viewer can interact with the large image and hover over the images and symbols to reveal hints that help solve the rebus. Alternatively, the viewer can expand the area to the right of the image to reveal the entire translation if available. If the viewer has their own translation or comments about this rebus, they are encouraged to “contribute a translation” by filling out the form at the bottom of the page.

ReadingRebus Farmer's Love Letter with Fruit and Vegetable RebusesIn addition to categories, we have implemented a tagging system for the rebus collection. Tags are more informal and may represent aspects such as time period (“19th century”), place (“American”), subject (“women”), or concept (“love”). The tags offer yet another point of entry for a user to discover rebuses; clicking on the “politics” tag will show all rebuses pertaining to this subject. Since our audience may not be familiar with all the types, materials, places, and genres of rebuses, discoverability was an important consideration of the website design.

The Research section currently features nine essays authored by the team on rebus history, cultural uses, and new discoveries. Our varied, individual interests take precedent here with writings on heraldry, material history, poetry, archives, and technology. To encourage further  research, we have included a Bibliography page of primary and secondary resources. The area of rebus study has not been catalogued thoroughly or received its scholarly due so an introductory  bibliography will aid  those seeking to learn more. Primary sources include books that feature rebuses while the secondary sources contain information about and critical discussions of rebuses.

Future additions to the website may include an interactive map to show the breadth of where rebuses were used, along with more rebuses added to the collection and additional research essays.

The site is hosted at Reclaim Hosting through a free student account offered by CUNY Graduate Center. This hosting platform conducts daily, offsite backups. In the event the website needs to move, migration tools are available from WordPress and Reclaim Hosting.

While somewhat superficial as a measure, perhaps, for some time our project proposal on the CUNY Commons was near the top, if not at the top, of the search engine Ecosia’s results for the search “19th century rebus collection,” and other, similar enough searches. Although this only questionably speaks to the project’s success, especially due to the occurance’s ephemerality, it’s still at least somewhat notable as a metric.

VI. Evaluation:

Feedback from meeting with Micki Kaufman, Advisor to the Master of Arts in Digital Humanities Program, April 1, 2021

We set up a meeting with Micki for the Thursday class time during Spring Break, as we were all available then.  We were still very much at the planning stages of the project; however Micki was able to get a sense of the different directions in which we might head and as a result gave very useful suggestions.  She suggested we explore how ALT text on our site might interact with the concept of rebuses and lead to further theoretical understanding of the genre.  She also encouraged us to bring more Digital into the Digital Humanities dimension of the project: for example, proposing that we use Text Analysis on the verbal rebuses we were finding, and on the Wheatley Peters’ poems in particular to see what we might uncover.  Likewise, she liked very much the idea of a map that represented the range of geo-locations for the rebuses, not only where they were produced or are now housed, but also the spatial imaginaries that the rebuses evoked, for example, Quebec or Senegambia in their content or their historical circumstances.  While we weren’t able to do enough work of this sort to incorporate these modes of inquiry into the website at its launching, those of us who plan to continue with the project do intend to apply these ideas to develop its impact and interactivity further.

Peer review and instructor feedback

While our followers on social media are few, for the moment, many of them are classmates in the DH program and so we have gotten a good sense of that community’s positive responses to the project, which rebuses were easy or more difficult to solve, and what captured our peers’ attention. The dress rehearsal brought home to us how the strengths of the project lay in its visual richness and variety and that we should emphasize those aspects when publicizing the site.

Instructor feedback throughout the semester encouraged us to embrace the playful as well as the aesthetic dimensions of rebuses and translated them into UX encounters and viewer experiences.  Editorial suggestions also helped improve the clarity and precision of our theoretical conclusions on rebuses and their histories.

Based on the feedback we received, there is a desire to see more ludic elements added to the website. While it wasn’t quite possible to implement more of these elements before the semester’s end, in the future, these additions could be made real. They would most likely in part take a similar form to the site’s homepage’s interactive elements in order to compliment what the site already offers.

External review

In addition to peer review, we will be seeking feedback from staff members of Emojipedia and the New York Times puzzles team. Thanks to a group member’s contacts, we have already shared the site with Robert Vinluan and Sam Ezersky of that team. Their experience with visual symbols and puzzle-solving activities will bring a wealth of knowledge to the Reading Rebus website. In addition, their unfamiliarity with the website and its functions may give us ideas on how to improve the user experience.

Also, we look forward to receiving feedback from users surfing our website. There is enough content (in terms of rebuses) on our website so that users can start sharing their opinions. In addition to that, since we always thought of our resources as an interactive space, as we increase their number,  the unsolved rebuses available on our website could be translated and these translations could be sent to us via email.

Weaknesses and Strengths

Notably, our Twitter and IG postings received by far the most views when they included animation, regardless of whether we were posting in response to a specific event (i.e. Mother’s Day etc.).  This suggests that we should focus on drawing people to the site through digital models of how rebuses work rather than posting static images however apropos or historically compelling.

As our instructor hinted, not having a specific group member responsible for Outreach beyond Archival Institutions, probably diminished our ability to generate enthusiasm for the site.  We found it a struggle to keep up with postings collectively, nor were we able to plan ahead for what content we would share and assign the week’s outreach to different members proportionally.  While the freedom group members had to pursue the aspects of ReadingRebus that interested them the most probably led to a richer website as a result, it also at times seemed to prioritize research over audience: an imbalance that the group should address as the site grows.

ReadingRebus IG siteReadingRebus Twitter shot

VII. Continuation/Future of the Project/Sustainability:

Future of the Project

In June, 2021, the website will be featured in an online exhibition at the Fordham University Gallery (https://fordhamuniversitygalleries.com/home.html). Now that the first iteration of the website is complete, we will also be reaching out to various colleagues to expand its range and influence. There is interest among some members of the group to continue working on the website although we have not formalized a plan and for now have ceased standing meetings.. We have many more rebuses to be added to the collection and, perhaps, this work can be done over time by 1-2 team members. At least one member will maintain the hosting and WordPress platforms to keep them up-to-date.  Another member plans to hone their WordPress skills by uploading additional images and content in the next few months and to update their scholarly essays as new material emerges. Lastly, there may be grant and funding opportunities that team members may want to apply for in order to expand the scholarly findings uncovered in the process of creating ReadingRebus.

VIII. Long Term Impact:

The Reading Rebus project will continue to be used in presentations such as the aforementioned online exhibit at Fordham. Additionally, the active community of puzzle creators and enthusiasts have begun to take notice and will likely contribute more interpretations and translations as the collection grows. Some rebus artifacts that were discovered in this process have led to additional research and academic projects by members of the team, such as the ongoing discovery into the rebus writing of Phillis Wheatley Peters, and mapping the historical rise of the rebus as it crosses imperialist routes over time. As scholarship about the rebus in English is scarce, ReadingRebus shall continue to be a resource and hub for puzzle lovers and curious scholars. As creators, the group has found that rebuses now pop into view consistently in our quotidian experience and add to our understanding of this visual-verbal genre.  We hope that our site will have a similar effect on its viewers who, in turn, will expand the discussion and accumulation of rebuses as the ReadingRebus project has aimed and continues to aim to do.

https://readingrebus.com/

 

Last Group ReadingRebus Project Report: thyme to go

Thursday’s meeting was our most candid and productive yet.  By Sunday, we seemed to have grown fully into our roles and responsibilities and delivered what we need for the presentation.  We still have fantastical dreams for the site, but voting collectively using the 0-3 rating system made our core-rebus-artifact group and their relevant categories for tags and metadata emerge clearly.  We took many of the class responses to heart and decided to embrace the visual delights of the project enthusiastically.

At the same time, getting the essay drafts was like a birthday party for me: I hadn’t realized my co-workers had been thinking such interesting thoughts throughout the semester.  Of course, I’d caught glimpses: however, the different minds, personalities, and sources of pleasure that we each bring to the project can best be seen in those individual explorations and explanations.

Hence, the project embodies what the early moderns called a “Raccolta” or a “gathering”: a synonym for the English “anthology” but one that resembles a harvest rather than a single-minded collection.  Or, to borrow a Renaissance trope used by Montaigne (and StarTrek, Seneca, et al), our results are the workings of a sort of hive-mind: individually “[t]he bees plunder the flowers here and there, but afterward they make of them honey, which is all theirs; it is no longer thyme or marjoram” [“On the Education of Children”].

In sum, I need not have worried about scarcity or drones; we have 30 + rebuses that received a top ranking from all members.  If we eventually add the ones that got a single good (2), not great (3), among the highest marks, we will have 80+.  All this inspires us to keep feeding  the project collaboratively over the summer, from our various fields: seeing if we can attract more social media attention now that Twitter has allowed us to post again, and developing more sub-themes and ludic experiences for our audiences—and ourselves.

https://collation.folger.edu/wp-content/uploads/2014/04/AlvearieTitlePage.jpg

Reading Rebus: Group Project Update Week 12

With 13 days to go until the Gran’ Prova, I’m feeling as jittery as a soprano making her debut at La Scala.  While I can see how we can and will be ready, we don’t feel ready to me.  There is so much to do, or still to decide not to do.  That’s what weekends are for, no?

On the plus side: We have more than 100 rebus examples to choose from, in multiple media and languages.  Our final template for proper crediting is in place and beginning to be put to use; the essay responsibilities assigned and word count has been reduced to a manageable amount for producer and user alike.  Information for our rebus map has been entered into our spread sheet in general.  Our rating system is in place and hence our rebuses should be selected and ready to upload by end of Sunday, for the most part. Our social media links have been given to Bret.  The response to our visuals in the 4/23 presentation was extremely positive and we got lots of useful feedback.

On the minus side: We are charitably one to two weeks behind on our work plan time line, primarily regarding the generating and copy-editing of text.  The essays are not written.  We are just starting to add proper metadata & crediting. Our final rebuses are not on the website, aside from what Patricia has uploaded and worked with.  I suspect we will need to provide more individual and specific geolocations so that Rachel can create her map.  Moreover, outreach has flagged: we haven’t posted on social media in over a week and our initial attempts to select and caption posts in advance hasn’t come through, although a spread sheet has been created.  Personal posting and contacting seem to have slowed as well.

Tentative triage plan proposed by PM (dates subject to group approval):

  • Social Media posts on Sunday 4/25 morning and Sunday 5/2 morning.
  • Final rebuses will be chosen by Thursday 4/29 and uploaded by Friday 4/30.
  • Essays will be shared, in whatever state, for first review by Saturday 5/1.
  • Credits & metadata for each uploaded rebus will be completed & shared with Patricia by  Monday 5/3
  • Talking points for each slide by Tuesday 5/4
  • Map in rough form completed by Wednesday 5/5
  • Final essays for proof-reading by Saturday 5/8

Promiscuous tags etc. (ReadingRebus Group Post II)

Hey Fans of ReadingRebus: Did you do Saturday’s Crossword in the Times?  Check out 26 Down!

ReadingRebus met once, rather than twice, over Spring “break” and didn’t post on social media during the vacay: that constituted relaxation for us.  With May in sight, Project Manager Bianca’s watchword is “Organization”!  The group is refining its categories for the rebuses we will be posting on the site; rethinking the group writing tasks for the remainder of the semester; and testing beta versions of cataloging templates and tagging, to see what will best communicate to and involve our users in the fascinating play of rebuses.

Patricia has been hard at work on gorgeous v.3.0 (to which only the team has access–for now).  She has designed the site navigation and laid out all the pages. She also has coded the interactive functions for the rebuses and started us off with a set of categories (beta—mentioned above) that may change as we start adding the examples. She’s currently working on adding metadata to the rebus examples and a tagging system, along with design improvements.

Rachel is wrapping up her French rebus research and translation (Merci, Rachel’s maman!) and starting writing up her priority essays. She’s discovered some extraordinary Mexican-American sewn rebuses that are expanding our notions of how community and media intersect in transmitting rebus puzzles

Bianca has finished her PWP and verbal rebus research and is writing that up this week.  She is expanding her Anglo-American and early modern material history essay to the French publishers and designers that Rachel has uncovered.  She is also proofreading v.3.0 as it emerges.

Matt is selecting a microcollection of heraldic rebuses and posting them, as well as expanding his primary and secondary heraldry bibliography for his essay on heraldry and rebuses.

Ostap as head archivist will be reflecting on Patricia’s cataloguing template and providing the final version in the next few days (Tuesday) so that we can begin to establish our anti-penultimate archive of rebuses.  Stay tuned for his Group Blog next week and for our next social media posts on Twitter and Instagram (@readingrebus) coming soon!

 

Mapping Cemeteries: Enjoying the Process

We’ve all made the most of our time this week since spring break. Nadia has made extensive updates to our site on GitHub (check us out!) and has been working hard to put our dreams into code. Our horizontal timeline is meant to place users within New York City history (at least the time points we’ve deemed relevant to our research), and the vertical timeline will highlight our research on our select locations. And now they are speaking to one another (the circles at the bottom of the horizontal timeline link to each pinned item on the vertical timeline; click around, and you’ll see what we mean). These timelines are built with different tools based on different code, so it took Nadia some time to bring them together, but she was determined to make it work, and we’re so thrilled.

As we’re building up the site, and as we’re getting further along in our research, we’ve found that aspects of our data management sheet weren’t working how we wanted them to. We’ve been reviewing this sheet in every meeting, and we’re adjusting along the way. Lisa and Nadia have very helpfully included a tab for each page of our site, and the first tab in the spreadsheet is for instructions on how each column of the spreadsheet is meant to be used. When a change is proposed, we discuss the pros and cons from the perspective of the researcher inputting the data and also Nadia’s perspective as the developer–is adding our data intuitive, and are we adding it in a way that makes it easier for Nadia’s codes to automate updates as much as possible?

Asma met with her metaphysics professor this week to discuss how we can ethically share images and data from our research. She’s also been hard at work drafting a plan for our forthcoming audio episodes, and her professor has agreed to join us for the first one. Stay tuned!

We’re so thrilled with our definitions of the project, and lane has worked to put them into image/text boxes that he will be debuting in our first posts on Instagram and Facebook–so be on the lookout. We love them so much we’re going to find ways to integrate them into our Commons site homepage and our GitHub About page.

I, Bri, love our project definitions so much that, inspired by Bret’s recent word cloud post, I went ahead and made a Voyant Tools word cloud from them.

Mapping Cemeteries project definition word cloud

Word cloud created from Mapping Cemeteries project definitions written by each team member.

Looking back there are many little things here and there that we’ve changed along the way since February, and we’re always adapting to make sure everyone on the team is being cared for and checking that our expectations and deliverables are realistic. We spoke briefly about our decision to include ourselves as our primary audience, as well as our class. At the time it felt like maybe we wouldn’t be doing enough work, or our work might be too self-centered. But we’re feeling strongly this was the best decision for our group. It’s allowed us to appreciate how much of our project building is about the building and the process. “Done” is going to happen because we will run out of time in the semester, but we’re confident that the state of our project will be something we’re all so proud to share when we get there.

*Posted by Nadia, Lisa, Asma, lane, and Bri.

Mapping Cemeteries: Project Updates

We’ve really gotten a lot done this week, and (as many others have commented in their blogs already) it’s really feeling real now. It was especially wonderful having so much of our class time devoted to group work this week.

Site Updates

We have a lot of great data already in our shared data management sheet, and Nadia will be working over the next week to get it up on our site so we can better see how our pages are working together.

And I’ve made our site on the Commons live and publicly available now too. Check us out at https://mappingcemeteries.commons.gc.cuny.edu/. Still a lot of work to be done here, but we’ve at least defined how each of our pages will be used and how they will serve our audiences, and we’re very excited to start building it out more.

We’re trying to stay focused on our research as much as possible until April 15, at which point we will focus our energies more on design and how we can use imagery and branding across our two sites, and our social media posts, to create a cohesive overall experience.

What’s Changed Along the Way?

We’re all trying to be mindful of our workloads and accepting that all of what we thought could be accomplished back in February is just not possible. And that’s OK! We’re taking the proverbial “less is more” approach. We initially envisioned each of us being responsible for researching a cemetery or memorial location, but Nadia is already tackling so much as our development lead, so we’ve moved that area of inquiry to our wish list. If we find time, great. But a proof of concept built around four locations will be just as great; maybe more so as we can spend more time on the site and user experience of it.

In my original proposal I was so focused on the spaces for the dead that had been obliterated that I never even stopped to think about the spaces for the dead that have never been officially recognized and respected as such to begin with. We’re all so grateful to Asma for helping us think about this and challenge our map to allow for what has previously been (and may continue to be) unmappable. And it also brings us very thoughtfully back to our original question: Who gets to be remembered?

Mapping Cemeteries: Site Preview

We (namely, Nadia) are building our project in GitHub Pages, and have yet to publish the site so far. But here are some screenshots to show everyone of the direction we’re heading in.

Splash Page

The first page you see is a map of New York City. We will have an interactive pin for each of our locations. Locations may be a combination of actual and imagined geographical coordinates. Some of what we wish to map–in this phase and beyond–may be unmappable. For example, exact locations are no longer known, we want to be respectful and not draw unwanted attention to closed sacred spaces, or the spaces simply resist the limits imposed by a map–or some combination thereof. Hovering over a pin will show you an image and let you click through to the location’s page.

 

Screenshot from the wireframe of the Mapping Cemeteries project for the "Splash" (or Mapping) page.

The “Splash” page is a map of NYC and has interactive pins for each cemetery.

Timeline Page

We are experimenting with both horizontal and vertical timelines. The horizontal timeline will help position our research and locations within the broader context of New York City history. It will include dates and very short blurbs pertaining to infrastructural milestones (e.g., Croton Aqueduct), legislation (e.g., burial bans), epidemics (e.g., yellow fever), and times of significant population growth (e.g., key Census count years). The vertical timeline will focus on our specific locations. We envision it as a conversation between our locations/us, tied to specific years, that explores the connections we discover between them. Each of our locations will be represented by a category tag and gravatar. Clicking “Read More” from a pin in the horizontal timeline will direct the user to the full location page.

Screenshot from the wireframe of the Mapping Cemeteries project for the Timeline page.

The timeline page has a horizontal interactive that gives broad historical information about the NYC deathscape. The vertical contains our discreet scholarship. Both are interactive.

Location Page

Each location will have its own page. These pages will feature a combination of historical and present-day images (when possible), and the content will take essay form as we explore each location in depth.

Screenshot from the wireframe of the Mapping Cemeteries project for the War Memorial Cemetery page.

Each of our cemeteries will have their own page. The bulk of our scholarship will be contained within these five pages.

About Page

Our about page will highlight key information about the project and about us, as well as ways to contact us.

Screenshot from the wireframe of the Mapping Cemeteries project for the "About" page.

The “About” page has information about the project and its participants.

Commons Companion Site

We are very intrigued by Bret’s suggestion to build a site on the Commons after our discussions last night–as a full group and in our breakout room. We are already using a Commons group as the primary means of communicating and sharing files. We (namely Bri) will start building a public-facing Commons site tied to our private group page. We envision this site as a “behind the scenes” or “making of” view of the project. We can use much of the content we’ve already blogged for class. We can also include a more in-depth analysis of our philosophical approach and fully address blockers we encounter while building the project. We will enable comments on our blog posts, and we will also provide a “What We’re Reading” type page with links to articles shared via Hypothesis to engage our audience in building a collective understanding of key articles shaping our theories. We may even enable Hypothesis across the whole site so our audience could engage with any content they find interesting or have more questions about. As such this site would fulfill much toward our pedagogical aims and also serve as a means of audience outreach beyond the limited scope of social media platforms. We will link to the Commons site from our project site About page, and our Commons site will link to the project on GitHub pages. Depending on the social media post, we can drive traffic to one or both of these sites.

Social Media Links

Here are links to three of our social media accounts. Please follow us.

Instagram: https://www.instagram.com/mappingcemeteries/

Facebook: https://www.facebook.com/mappingcemeteriesnyc

TikTok: https://www.tiktok.com/@mappingcemeteries?lang=en

 

*posted by Lisa, Nadia, Asma, lane, and Bri.*

Lisa’s Public Journal – Week Seven — Research

This week I have spent most of my time researching William Jenkins Worth.  I was able to find only one biography of him, “General William Jenkins Worth: Monterey’s Forgotten Hero” published in 1953, which is now out-of-print.  Instead, I’ve been reading contemporary accounts of his life and death.

The New York Times ran several articles about the festivities surrounding Worth’s interment in the monument at 25th and Broadway.  The account from 26 November 1857 is profound in its detail; an entire broadsheet, devoted to the minutia of the day.  From the number of horses that drew the casket up Broadway (“sixteen gray horses with black plumes fasten above their heads”) to the impressive number of documents that were included with the casket (I need to understand why Comptroller Flagg’s Report for 1854 was deemed as necessary for the General’s afterlife as a bible) to the many dignitaries who spoke, to the dramatic masonic rituals.

The challenge is to share enough of his biography to explain why he received the honors that he did … only one of two people to be given a public reliquary in NYC, President Grant is the other … and put this tribute in a greater context.  Why does society choose to exalt some and neglect others? The reporter who penned the story explained their reverence thusly:

“There was no spot, honorable to the wealth and magnificence of this emporium or worthy of the public services which he had rendered … But, from this day forward, the pilgrim of his genius and patriotism may here kneel in thankfulness, reverence, and admiration, at his shrine.  The youth of our counter, passing and repassing this monument, will hereafter pause to peruse the record engraved thereon, of the virtue, service, and fame, of a man whose life presents a beautiful illustration of the institutions of our country, having raised himself from civil life to the highest rank know in the army; and every gradation in the chain of his elevation having been due to the fidelity of his adherence to professional duty.”

I sat across the street from that monument for several hours last week.  The city felt almost normal, what with the hint of Spring and warming weather.  Some hundred souls passed the obelisk and not one paid it any mind.  I was reminded that even the most famous among us can be forgotten.

Worth Memorial March 2021

Worth Square, as seen from Madison Park


“THE Obsequies of General WORTH.; Address of Mayor Wood. Dedication of the WORTH Monument. Imposing Procession.” 26 Nov. 1857. Web. 17 Mar. 2021. Link: https://nyti.ms/30RaW9e

Map of Lower Manhattan from 1797

Mapping Cemeteries: Outreach and Publicity Plan

Our team is prioritizing pedagogy and the overall reproducibility of Mapping Cemeteries in our Outreach and Publicity Plan. While several social media platforms and web tools provide wide opportunities for distribution, not all–or even most–are conducive to teaching the Digital Humanities (DH) skills and topic of Mapping Cemeteries. 

We understand that our primary and secondary audiences value research, user design, user experience, and project design according to our analysis of their DH backgrounds and interests.  Based on this, we determined a six-week campaign across Instagram, Facebook, SoundCloud, and TikTok were the best options for the priorities of our audience and reproducibility of Mapping Cemeteries following our review of popular and obscure digital platforms and tools. Outlined below are key areas of outreach that include milestones and protocols to be executed during our intended window of interaction with our audience.

Staff Responsible

lane v., Outreach Lead

Asma N., Audiovisual Modulation Lead, Outreach Support

Platforms

  • Instagram 
  • Facebook
  • SoundCloud
  • TikTok  

Timeline

Our Outreach team will run a six-week campaign on the reproducibility and awareness of Mapping Cemeteries’ humanistic investigations. The timeline for outreach was designed around the time constraints of the Spring 2021 semester and the time required to execute phase 1 during this 13-15 week window. The six-week window is imagined as an opportunity for a specific and targeted approach to our outreach milestones. 

Protocol

  • Accessibility: The entire time will have access to all platforms, although Asma will be taking the lead on SoundCloud and Facebook content. Both login and passwords for the accounts will be stored in a team document.
  • Responses: Anyone on the team can respond to comments or converse in comment sections, but lane will take primary responsibility for ensuring comments are responded to within 24 hours of the comment being posted. If a comment pertains to a subject that another team member has specific knowledge or insight in, they may be requested to aid in the response.  
  • Troll Comments: With any social media presence, there is always a chance of being targeted by trolls or bots. If an inappropriate comment that has no relevance to the project is left under one of our posts, it will be flagged and removed by one of the team members.  
  • Tone: To best appeal to our intended audience of classmates and fellow academics, our social media presence will take a pedagogical approach with its posts. We do want to keep in mind the seriousness of our project’s subject matter, so the overall tone of our social media presence will be an intentional balance of educational and levitous.

Instagram and Facebook

For Instagram and Facebook we are focused on six weeks of posts starting on Week 7 of class (Spring Break):

  • At least one Instagram post with photos and relevant information on each cemetery our project is focusing on:  
    • a historical cemetery that still exists as such 
    • a cemetery that was established/other 
    • a cemetery that was repurposed as a public park 
    • a cemetery that was repurposed and later rediscovered and exists again as such 
    • a war memorial 
  • At least one post advertising each of the three episodes of our project’s podcast 
  • Other posts may include TikTok videos, excerpts from articles, or other relevant information intended to encourage interaction or draw the attention of our audience.

Audio Roundtable, SoundCloud  

Mapping Cemeteries will produce a limited, three-part audio series on phase 1 of the project hosted on SoundCloud. The first episode will introduce the team of DHers working on Mapping Cemeteries; episode two will introduce each of the five necropolitical investigations of Mapping Cemeteries; and the final episode will bring the team and listeners to an audio roundtable to disseminate Mapping Cemeteries and its overall intervention. 

Mapping Cemeteries is built with accessibility in mind; we understand access is a broad category that centers ability and learning styles alike, among other important considerations. We care about this scope, especially as it concerns the twofold pedagogical and reproduction priority of our project. We recognize audio as an opportunity to address an area of design; or to capture and playback the bits–for example a DH tip for troubleshooting–that interest our audience in another useful format for learning. We also recognize audio as an opportunity to reach our audience with known and unknown visual impairments–and varying accesses to supportive resources–through our project’s outreach. 

SoundCloud was selected as a primary hub for storing and manipulating audio data, and disseminating Mapping Cemeteries due to its reputation in audio hosting (storage), Rich Site Syndication (RSS) feed module, and playback features that do not require credentials (user registration) for our audience without an account.

Though this limited audio series will capture fragments of our project, it provides sentimental and intellectual insights to our process and relationship to our humanistic topic that would not be otherwise known, or pertinent to the key user-facing aspects of Mapping Cemeteries. 

TikTok 

The team is extremely interested in utilizing TikTok to attract the attention of our audience. Surprisingly, there is a significant amount of TikTok videos about digital humanities–most of them are in German. Before final dissemination, the goal is to post at least one to two videos discussing Mapping Cemeteries and the DH skills we’re using to build the project.  

Expected Outcomes

Our primary goal is twofold: we want to prioritize the reproduction and pedagogical elements of Mapping Cemeteries for our audience. Our expectation is that they will be able to implement at least one key DH skill outlined in our outreach content; and to reproduce an element of Mapping Cemeteries that concerns user experience and/or project design. 

For example, embedding audio is a DH skill that encompasses user experience and design and audiovisual modulation considerations. Our campaign could feature a three-part TikTok video series to teach this DH skill, informed by our Audiovisual Modulation, and User Experience and Design Leads, respectively, on how to accomplish (or to otherwise think about) this task.

  • The first video can introduce the skill, its importance, and how it can be used for a key task of our project (to reproduce).
  • Our Audiovisual Modulation Lead, Asma N., can develop instructions on how to record, edit, export, and upload an audio file to an audio source to generate an embedded code for the second video.
  • Our User Experience and Design Leads, Lisa K. and Nadia E. can show how to embed the code on the backend of a website, or platform, relevant to Mapping Cemeteries to conclude the series.

Our Outreach Team and Lead, lane v., will ultimately review the content (with project management input) and modify the pedagogy for each task in an accessible and creative manner for our audience.

If our audience can learn one of our DH skills, the hope is for them to then implement it–or conceptualize how–to reproduce an element of our project in one of the aforementioned topic areas (user experience, project design, etc.). Get the skill, use it for a task.

Measure of Effectiveness

Our Leads, Asma N. and lane v. will develop a survey to measure the execution of our expected outcomes. We want to know if and how our audience’s interests were reflected in our overall project and how our choices facilitated our goals for expected outcomes. 

Analytics

In addition to a survey, most of our intended platforms allow for analytics, or have DH tools that compensate. For instance, Mapping Cemeteries will need to establish an Instagram/Facebook business account to access its analytic feature, Instagram Insights. An alternative is Iconosquare, a free analytics tool designed to capture engagement data from Instagram and its parent company, Facebook. This digital tool, which can be discerned as one for DH in the case of Mapping Cemeteries, offers machine-learned, generated tips on how to improve our engagement. This tool generates analytics every 30 days, which means we’ll have access to two sets of analytic data within our 6-week window, should we use it.

*Map of Manhattan from 1797; image from the New York Public Library digital archives.

*posted by lane, Asma, Nadia, Lisa, and Bri

Mapping Cemeteries: Data Management Plan

1. What are the types of data that may be produced as part of this project?

Our project will generate data specific to five cemeteries, as well as data for the timeline visuals which will combine all five cemeteries data into one. We expect to have both primary (generated by team members) and secondary data (found by team members).

  • How will data be collected (e.g., instrumentation, observation, survey, etc.)?
      • We are gathering data between February and Mid-April, 2021, based primarily on research from digital archives, journal articles, and digital sources we have access to (either through our CUNY affiliations or are freely available to the public).
  • Is it possible to regenerate the data? What are the implications for your research if the data are lost or became unusable later?
      • Yes, our data (e.g., dates and locations) will be reproducible, though we may come to slightly different conclusions about it if our supporting text is also lost.
  • What types of data will be produced?
      • images: historical images (based on licensing availability) and present-day images taken by our team members at the selected locations
      • videos: taken by our team members at the selected locations
      • audio: to increase accessibility to our text, interviews with funerary experts, and accompanying podcast documenting our process of building this project
      • text: descriptions and narratives produced by our research
      • location data: longitude and latitude of cemeteries to produce map pins
      • code: to build our website
      • metadata: for each page of our site, as well as each media item that appears on it to ensure searchability and accessibility
  • What are the tools or software you will be using to create/process/analyze/visualize the data?
      • Google sheets, Google docs, Mapbox, timeline tools like TimeLineJS or Vuetify
  • What are your access, storage, and backup strategies?
    • All primary digital assets (images, videos, and audio) will be stored on Wikimedia commons. Our main tool for storing data will be a spreadsheet. Each sheet will be filled out by all team members as they do their research.The spreadsheet will include multiple sheets:  
      • general/map
      • horizontal timeline
      • vertical timeline
      • historical cemetery
      • cemetery repurposed as park
      • cemetery war memorial
      • cemetery rediscovered
      • established/other cemetery

2. What standards will you be using for data collection, documentation, description, and metadata?

The spreadsheet will reside on Bri’s google drive, GitHub repository (in a csv format, as well as a link to the google drive in the Read.me file), team members’ local machines. Version control is built into the Google spreadsheet so we can see how/when the data is updated, and changes to our website code will also be versioned and saved within GitHub. And we are documenting our weekly contributions to the project via individual diary-like updates in our Mapping Cemeteries Commons group.

  • How do you document data collection procedures?
      • We are noting all of our data collection via our shared Google sheet. Each sheet will include the following list of columns that is subject to expand:
        • name
        • custodian
        • caption
        • description
        • data type
        • purpose
        • tag
        • source link
        • citation
        • Institution
  • How will you ensure good project and data documentation? Who is responsible for implementing this data management plan?
      • All team members are responsible for implementing this data management plan; our names will be next to all data we enter onto the sheet.
  • What directory and file naming conventions will you be using?
      • We will follow Tidy data and other best practices. All file names will use underscores (_) instead of spaces, and they will include dates to aid in version control. Information about our files will be included in a Read.me file with a data abstract, as well as a data dictionary as needed.
  • What project and data identifiers will be assigned?
      • Data will be organized via cemetery/memorial location. Historical data we include in our vertical timeline will be organized separately.
  • Will you use disciplinary or community standards for data formatting, description, interoperability, or sharing for any of the data you collect?
    • We will follow all disciplinary standards, and customize to our project needs as necessary.

3. What steps will you take to protect your or your participant’s security, privacy/confidentiality, intellectual property, or other rights? (Check current university policies for requirements.)

  • Who controls the data (e.g., PI, student, lab, University, funder), and at what level?
      • Team members control the data.
      • Google docs reside under Bri’s account as she may be using this for future phases/capstone project.
  • Any special privacy or security requirements (e.g., personal data, high-security data)?
      • We will make sure to use up-to-date software and upgrade as necessary to avoid any vulnerabilities. Additionally, no personal information will be stored on our site.
  • Do you have any embargo periods to uphold?
    • No

4. If you allow others to reuse your data, how will the data be accessed and shared? What are the data sharing requirements your work is subject to (e.g., funder, journal)?

  • Who is your possible audience? Who may use the data now, or later?
      • We are planning an initial “soft launch,” so our initial primary audiences are our classmates and attendees at the GC Digital Showcase.
      • Going forward we expect our audience to include:
        • New York City historians, especially those interested in the macabre, necropolitics, and lesser-known or “forgotten” histories
        • Scholars and members of the public studying cemeteries and memory studies
        • People offering and interested in taking walking tours and practicing alternative forms of tourism
      • Bri may expand on this project for future phases and/or for her capstone project.
  • When will you publish the data and where?
      • We will share all of our data on GitHub, and media we create will be shared on Wikimedia. We will publish our data on our website, and we will also share our findings in Clio as a potential walking tour, with links back to our website.
  • What tools/software are required to access your data?
    • Users will access our data via our public-facing website, social media posts, and Clio.

5. How will the data be archived for preservation and long-term access?

  • How long should the data be retained (e.g., 3-5 years, 10-20 years, permanently)?
      • Our data will be retained for 3-5 years, at which point this DMP will be re-reviewed to determine whether longer-term access is required.
  • What file formats will you be using, or converting to? Are they sustainably accessible?
      • Our data spreadsheet will be saved in csv format, and a link to the Google docs will be included in the Read.me file stored on GitHub. Text will live in Word and Google docs, and be backed up in rich text non-proprietary formats. Images, video, and audio files will be saved as JGP or PNG, MP4, and FLAC files (or other non-proprietary format), respectively. The non-proprietary formats will live in GitHub, and both proprietary and non-proprietary formats will be stored in our Mapping Cemeteries Common group library.
  • Who will maintain my data for the long-term?
      • Bri
  • Which data archives are your data appropriate for (subject-based? institutional)?
    • Our data archives can be appropriate for New York City history, New York–related migration studies, and Digital Humanities archives

*Posted by Nadia, Lisa, Asma, lane, and Bri*