In search of meaning and significance

With only a few weeks left before our final presentation, the task is underway to best capture and more deeply articulate the significance of Corona Chronicles.  One area of indirect significance relating to the impact of the pandemic on younger generations comes through in the research on the long-term effects of in utero influenza exposure during the 1918 influenza pandemic.  In a study published in 2006, Dr. Douglas Almond, an economist at Columbia University, concluded that “cohorts in utero during the pandemic displayed reduced educational attainment, increased rates of physical disability, lower income, lower socioeconomic status, and higher transfer payments compared with other birth cohorts.”  Almond’s study leverages vital statistics available during the 1918 pandemic and census data for 1960, 1970, and 1980.  As the following graphs taken from Almond’s report illustrate, significant variances occurred for individuals born during or shortly after the 1918 pandemic.

 

Graph of average years of schooling of men and women born during the 1918 pandemic.

1960 average years of schooling: men and women born in the United States. source: Almond, Douglas. 2006. “Is the 1918 Influenza Pandemic Over? Long‐Term Effects of In Utero Influenza Exposure in the Post‐1940 U.S. Population.” Journal of Political Economy.

Graph of High School Graduation by Year of Birth in 1970

1970 High School Graduation: by year of birth. source: Almond, Douglas. 2006. “Is the 1918 Influenza Pandemic Over? Long‐Term Effects of In Utero Influenza Exposure in the Post‐1940 U.S. Population.” Journal of Political Economy.

Graph of Male Disability Rate in 1980: Physical Disability Limits Work

1980 male disability rate: physical disability limits work. source: Almond, Douglas. 2006. “Is the 1918 Influenza Pandemic Over? Long‐Term Effects of In Utero Influenza Exposure in the Post‐1940 U.S. Population.” Journal of Political Economy.

Almond also mentions research suggesting links between the 1918 pandemic and possible increases in the occurrence of schizophrenia, diabetes, and stroke (Almond 2006, 680).

In another more recent study published in 2017, researchers at the North Carolina Research Triangle Park, Brown University, and Duke University concluded that “[i]n utero exposure to the influenza pandemic increased functional limitations and hospitalization rates in old age” (Acquah, Dahal, and Sloan 2017, 1477)

Given these data and conclusions, which persuasively argue for the development of public health policies that support prenatal health centered around the needs and wellbeing of mothers, a host of related questions might be raised concerning the impact of pandemics on children’s health.  What long-term impact did the 1918 pandemic have on parenting and child care?  What were the differential long-term outcomes between families stricken by the 1918 pandemic and families which were less seriously affected?  What long-term impact did the closure of schools during the 1918 pandemic have on students?

An area of more direct significance pertains to the understanding and treatment of childhood trauma.  Within the context of epigenetic, developmental, and traditionally understood childhood trauma, the role of art as a creative expression of subjectivity offers the possibility for therapeutic spaces for healing.  Of the many definitions of trauma, the notion of trauma as any unmanageable, often dysphoric, unresolved autonomic nervous system response (Levine 1997) that is disassociated from its healing environment might consider art therapy as part of a fundamentally somatic resolution.  Beyond the healing that can result from the doing of art lies the healing resulting from having one’s own trauma recognized.  Art as a shared experience therapeutically presents the possibility for a supportive environment that can help re-associate and reintegrate fragmented and unresolved psychological and emotional wounds.  As was recently noted by Dr. Shirley Sharon-Zisser in an essay applying Lacanian theory to art therapy:

“The distinction Lacan makes in his twenty-fourth seminar (1976–1977) between full speech (speech that is full of meaning) and empty speech (speech voided of sense and reduced to its real value),…as well as the increasing emphasis in Lacan’s late teaching (as of the twentieth seminar of 1972–1973…) on nonsensical speech voided of sense, indicate the necessity to draw a distinction between the clinical role of artistic modalities which engage language’s semantic dimension (story-telling, image dialoguing, psychodrama) and artistic modalities which can work towards the reduction of the phantasm to its material, non-signifying components, traumatic residues of an enjoyment beyond sense” (Sharon-Zisser 2018, 7).

References

Acquah, J. K., Roshani Dahal, and Frank A. Sloan. 2017. “1918 Influenza Pandemic: In Utero Exposure in the United States and Long-Term Impact on Hospitalizations.” American journal of public health 107 no. 9 (September 2017): 1477–1483. https://doi.org/10.2105/AJPH.2017.303887

Almond, Douglas. 2006. “Is the 1918 Influenza Pandemic Over? Long‐Term Effects of In Utero Influenza Exposure in the Post‐1940 U.S. Population.” Journal of Political Economy 114 no. 4 (August 2006): 672-712. dio:10.1086/507154

Levine, Peter A. 1997. Waking the Tiger: Healing Trauma. Berkeley, CA: North Atlantic Books.

Sharon-Zisser, Shirley. 2018. “Art as Subjective Solution: A Lacanian Theory of Art Therapy.” International Journal of Art Therapy: Inscape 23 (1): 2–13. doi:10.1080/17454832.2017.1324884.

Personal Blog: Taking Inventory

I found myself feeling overwhelmed again this week, between unpacking and leading two projects between my classes. But I sat with that feeling for a while, and then I started a plan to make these next two weeks more manageable.

In our group meeting tonight I had the idea for us to take an inventory of our GitHub site and determine what the minimum viable product was before the Digital Showcase. And we went through each and every page and listed out everything we’d like to see. And we categorized them by what we knew we could deliver, and what we’d like to deliver if possible (or what we might be interested in delivering after the Digital Showcase).

We agreed to do the same for our Commons site, though asynchronously via our group forum.

And I have to say, it was a great exercise. We were able to acknowledge all of the amazing work all of us have been doing, especially Nadia with the development of the site. And we struck a balance between excitement and exploration while also trying to remain considerate of all of our time.

And I’m feeling so much better for it. Thanks team!

thinking about DH lessons

These posts have proven hard for me to write each week – not for lack of something worthwhile to share from our group work – but because of how all of our work this semester has been running parallel to and embedded in a constant series of world events that are both hard to ignore and hard to appropriately connect in a manner that does not feel trite or disregarding. I have felt the heaviness of the wider world hang over trying to compose each of these.

I realized this week that I am looking forward to the summer for rest, clearly, but also to have time to reflect on what the next phase of this project will look like with less rushed consideration of some of our choices, particularly around outreach. I am not sure I will know everything I’ve learned this year until I am no longer consciously thinking about it and the lessons have time to settle and find their own rearticulating.

Prizing a fast pace has been a benefit at many stages but has also been something I’ve questioned. In the process, I have come to wonder about DH theories on pacing and structure of planning projects in the field. I am thinking of the intentionality of process in design thinking models. Or inquiry-driven teaching models with their four phases (Interaction, Clarification, Questioning, and Design). And at the end, reflection is critical before engaging in the next phase or iteration. Of course, we have in many ways followed this sort of model with the balance of our time spent on Design so it may just be that reflection is what’s called for and right on schedule.

The idea of failing quickly and often, and expecting to do so, and not just recovering, but rather building joyfully out of failure is one of those DH themes that has been on my mind a lot. So too are questions of voice, access, inclusion, representation, and absence. Few of these things are served by haste, but haste has helped us build a platform into which these values can be constructed. I believe that in the site’s current form, we as a group have already created something truly meaningful and worthwhile. And among the many things I am grateful for – beyond the most important thing, which is our team (just made up of the best people) – is that its current scale also still allows for modification to structure and design that will make it even more deeply mission consistent before growing consumed with processing and managing data.

It will be helpful and healthy to formalize reflections in the form of our end-of-term papers, and to tie them to the DH values we worked through in the spring. I’m genuinely looking forward to that process, rather than dreading that final paper – yet another thing to be grateful for!

Amanda Week 13 Journal

This past week was especially tough to juggle everything as I had some competing deliverables for work to handle, but we had some really productive meetings as we’re wrapping up some of the final details for our project. Most importantly though, I feel so lucky to be on a supportive team that’s really being generous with their time and care for each other.

On Sunday we brainstormed some ideas for our project trailer that we can use for future outreach and social media efforts. We heard feedback from last week’s presentation about showing off more of our student submissions, so the trailer will really amplify some of the stand out pieces. While we’d love to include a portion of this video during the final presentation, we’re going to avoid any awkward zoom issues that might happen with that. Instead we’re focusing on pumping our slides full of these student stories in creative ways. Does anyone know how to make a gif?

We also had fun going around the call where each of us did a lightning 20 second pitch of what our project is to inspire that opening energy that every good presentation has. One of our goals with this presentation is to be memorable to the audience on the day of the showcase. During an evening Zoom call with back to back projects, it’s easy for anyone to zone out a little even though this class has done some seriously impressive work. I’m so inspired after watching the other group accomplishments last week, and I can’t wait for the rest of the GC (and some public viewers) to also be blown away by what we’ve built.

In the meantime, I continue to focus on keeping the team updated and on track by providing meeting notes, agenda items, and heads up on upcoming milestones. I’m happy my organization skills could be useful to this project. I’m also very thankful that I work with wonderful project managers that I can model my role off of.

Its Only Tuesday GIFs - Get the best GIF on GIPHY

 

Bianca personal post Week 13: DH side trips

I took some time out for three DH Zoom events this week: two were CUNY related or recommended.  The other came from Book History but was equally informative.

First, I attended some of the NJIT conference on April 23rd:  Unfortunately I was late for the presentation that seemed most directly relevant to my work, on the history of machine translation, but I stayed and saw really interesting presentations on archiving DH projects, conceiving of cities as relationally rather than strictly geographically constructed spaces, and using VR to measure popular religious devotion in local Roman street shrines.  I also attended a breakout discussion of the poster related to this last project: I was impressed by the creativity and thoughtfulness of the undergraduates and their advisor, Louis Hamilton.  I loved the intersection of disciplines and the possibilities of more in the future.

I also dropped in on the CUNY Visions of Open event Friday afternoon, where 4 advanced PhD/post-doc students and recent alumni shared their current or capstone projects.  I found it inspiring and particularly helpful to see how different the presentations were as we prepare for our own launches and demonstrations in a few weeks.  It also clarified for me how a DH pedagogy project might look compared to a DViz or Text/Archival research project: the range of media and forms was liberating.

While I showed up for the first two events because they were recommended by the program, the last event (also on Friday) I linked to through a regular Material Text colloquium out of UPenn that I’ve been able to go to more frequently now that I don’t have to take Amtrak to Philadelphia on a Monday night.  While I don’t usually follow Manuscript studies, this Schoenberg Institute for Manuscript Studies introduction of VisColl, a digital collation tool being developed by Alberto Campagnolo (Udine) and Dot Porter (SIMS) drew me in.  Although I’m awaiting the adaptation coming this summer for reproducing the structure and imposition of printed books, this leaf and quire collation formula is amazing in its own right, with icons for Flesh side and Hair side, ways to note aberrations in sewing structure or additional/missing leaves, or simply as a means to visualize the bifolia construction of a MS, compare it to others, reconstruct a work by importing bifolia from distantly held texts and on and on.  Check it out!

https://viscoll.org/

While the first two events broadened my understanding of what DH can be on the undergraduate and graduate level and beyond, the last returned me to my own work in early modern textual studies, making me impatient to begin to apply what I’m learning to my own research.  It was also heartening to see the collaborative spirit of DH at work beyond the Arcadia of CUNY: VisColl has benefited from and supported in turn advances made by VisCodex at the University of Toronto and EVT at the University of Torino in similar areas.  Sharing trouble-shooting, back-end creations, and UX has made each develop faster and better.

Rating Rebuses

This week, as a group, we ran through a list of selected rebuses organized in a spread sheet, and we rated each on a scale of 1-3, with 3 being the best. Essentially, the rebuses we unanimously voted “3” on are the ones that we’re going to give the most attention fastest. Outside of that, we’ve formally begun writing the pieces we plan on posting to the website. At the moment, I’m working on a condensed version of the heraldic iconography guide, along with some longer-form analysis of some selected works.

With regards to the former, I realized that my expanded iconography guide wasn’t particularly user-friendly. This is in part because I originally created it to be useful as a personal reference for me. I’m currently in the process of elaborating on bits of information those less experienced in heraldry may have trouble understanding, and picking and choosing which icons will actually be relevant to the rebuses on the site.

lane journal – taking time to listen

This has been a somewhat hectic week for me. My time has been consumed with work, finalizing research for other projects, and attempting to plan out  next semester. However, when it comes to this course, I have been able to slow down a bit and take time to enjoy the work. As I mentioned in my last blog post, I revisited the African Burial Ground National Monument to record some sounds for our podcast. This was a moment of serenity for me as I took a break from other responsibilities to just sit with myself, observe my surroundings, and appreciate minute details I typically don’t even notice – the distant smell of salt in the air, fleeting snapshots of others’ lives, and the city’s hectic cacophony of sounds which are simultaneously abrasive and beautiful. I’ve been looking forward our team’s next podcast recording, which will be happening very soon!

In terms of outreach, my most recent post that went up on Instagram and Facebook promoted our Making Mapping Cemeteries site that Bri has put together. The site houses so much information and Bri did a wonderful job building it so if you have not checked it out yet I highly encourage you to! I’ll link it below. Asma and I will be meeting tomorrow to go over our first Tik Tok post. I will unashamedly admit to having posted a video or two on the platform before myself so I will be helping Asma with the editing process if needed.

In our last meeting, I presented the team with some logo designs I had created. After some helpful feedback, I have a better idea of a logo that best represents the project (and looks cool/cohesive with our aesthetics). Because I’ve been so busy this week, I haven’t had a lot of time to dedicate to this but this is something I plan to have done by our next class on Thursday!

Check out Making Mapping Cemeteries

Elena’s Journal (Week 13) – Putting out fires

When I started working as a project manager of the NYCCFA, what feels like centuries ago, my partner had an interesting comment. A manager himself (for an actuarial team in an insurance company), he just told me: “Being a project manager is like constantly putting out fires”.

He was right.

Here’s some examples:

  1. Yay! We’re making an archive!
    Do we need an IRB???
  2. Yay! We don’t need an IRB!
    We need hosting ASAP!!!
  3. Yay! We got the hosting!
    What version of Omeka are we gonna use? Omeka S is not right for us!
  4. Yay! We chose Omeka Classic!
    OMG, Omeka freaks out every time we try to import the CSV file with our dataset. We need to enter all the information BY HAND, one by one.
  5. Yay! We built an archive!
    Where are the contributions?? People are not contributing!!!
  6. Yay! People are contributing!
    People are sending us TOO MUCH STUFF via email and Instagram instead of using our contributions page. Ugh. Now we need to add all these from the backend. We need to make a video tutorial to explain to people that contributing is actually easy.

And so on. Oh, also, this is only 40-45% of the fires and the putting-out-of-fires, the ones I could explain in a linear fashion. Intertwined with all this, there are:

  • Developing relationships with fridge organizers that don’t know us and are skeptical of the project.
  • Managing 5 different people with different schedules, needs, and personalities (this includes me)
  • Doing the homework for class (that Friday deadline for the Group project updates kills me every week)
  • Following the feminist ethics of care that we have as our guiding principle is HARD, as I’ve explained in one of my previous posts.

Anyway, to conclude on a good note: now that I’ve been listing all these “fires” and ways my team and I managed to put them out (or at least contain them LOL), I realize that they were an essential part of the project. That they all make sense in the journey to get to a solid archive with a good amount of items inside. Every time we encountered a hurdle, we had to figure out a way of overcoming it TOGETHER. Lots of learning opportunities. And a good amount of stress.

I guess I should have believed my partner sooner and accepted that yes, putting out fires is an essential part of the job. And that’s ok.

Freedom of Speech* Group Project Update 4/25

After a fairly hectic few weeks, everything seems to be coming together! Group-wise, we’ve been communicating consistently via our Discord server, and Eva and I have been working on putting our code scaffolding into practice. So far, we’ve built out the skeleton and matched our site design to Kevin’s fantastic designs, which the whole group has been actively suggesting minor tweaks to in order to match our project’s goal of providing information on the boundaries of freedom of speech in a clear and accessible way.

The topic model is essential to our functional website, so Martin is doing a manual quality check on the resulting dataset to understand if our predicted threshold would be viable for determining if a case falls into a certain topic. The template question that’s being asked in investigating the threshold for a topic is “Does the topic in question accurately reflect the case’s content at a 25% threshold?” and we will replace the percentage with any percentage that is needed in order to do this in the most accurate way possible. Thankfully, the topics have been super clear since Eva removed common judicial stop words, so hopefully this goes well!

Development-wise, we’ve been trying to have fun with putting everything together. Eva and I have been sharing work in progress screenshots of things that go horrifically wrong during coding (in a way that is hilarious and can be fixed in two minutes) and, of course, memeing about it.

A picture of a large, hand-drawn map of the US with a smaller, computer-generated map of the US beneath it. user eva_sibinga replies,

An image comparing a website to a high fidelity mock-up. The mockup is very detailed and looks complete, while the website looks simple and is in progress. The caption reads "you vs the guy she told you not to worry about"

The great thing about having designs done is that putting the skeleton together for a site becomes much easier. The most work is definitely in assembling the logic that we’ll need in order for everything to flow correctly according to our prototypes.

In terms of design, as noted, Kevin’s made some cosmetic tweaks after our group meeting to make major revisions, and everything looks great! We added Alaska and Hawaii to our map and changed a few things like buttons and colors, and those things are super easy to tweak in our code.

The schedule we set at the beginning of the semester is relatively blank, but internally, we’ve set deadlines for ourselves and we’re aiming for complete rather than perfect. We, of course, want the project to be as good as possible, but to get a little pretentious, the root of perfection is completion.

Some things that we’re actively working on include:

  • The code for the website
  • Finishing touches on data
  • Web copy
  • Outreach

NYC Community Fridge Archive – Group Project Update (Week 12)

Last week we were super excited about our first contribution to the archive – now, we are trying to figure out how to manage the flux of incoming contributions!

Contributions

Thanks to Allison’s extensive outreach on Instagram, a lot of fridges have answered our call for contributions – and are sharing stories and pictures with us! One of the issues is that Omeka only allows users to contribute one item at a time, so many fridge organizers have started sending us photos via email and in our Instagram DMs. This is pretty awesome contributions-wise, but it causes some additional steps on our end:

  1. We need to ask/glean info about these pictures since they often come without sufficient information
  2. We need to make sure that the photos respect our Terms and Contributions: for example, are the people in the pictures consenting to have their image on our archive?

Omeka

We have also been working on Omeka:

  • Metadata standards: we decided on some metadata standards for contributions. Luckily, this can be done at the level of the contributions page, so all the information that users enter falls into the right category in the backend.
  • We have worked on improving the user experience for the contributions page, making our prompts easier to understand. We are working on:
    • adding some text to the contributions page, so people can have some instructions
    • prepare a video tutorial to explain how to contribute
  • We have tested different formats for contributions (PDF, doc, ZIP)

Milestones and Adjustments

Let’s celebrate our Milestones:

  1. We have built a functioning structure for our archive!
  2. People are contributing!
  3. We have raised a lot of awareness and interest in our project within the fridge community!
  4. Our outreach efforts worked, and the Oral History team will start interviewing people next week!

These milestones also mean that we had to make some adjustments to our plan and our priorities.

  1. We need to find a streamlined way to add contributions to our archive, especially when we receive them via email or Instagram DMs
  2. We need to be on top of responding to people’s emails and DMs, especially when they are asking questions about the project or having technical issues when they submit contributions
  3. We need to figure out a day and place for our launch party: our guests may be many, and we want to make sure everybody is safe COVID-wise. Also, we need to decide how to stream our launch party (and who’s going to do it).