About Us

This exhibit was created by Group 7 of the Fall 2018 Introduction to Digital Humanities Course at the University of Washington.

Project Manager: Catherine Lin

Catherine is a Senior double-majoring in Economics and History. She enjoys studying European cultural history, social memory, and bringing stories to life with data. In her spare time, she enjoys playing PC games, reading, photography, and spending time with her three cats. 

Visualization & Mapping Specialist: Kevin Huynh

Kevin is a Senior majoring in Informatics with a focus in Data Science. He's passionate about making technology more accessible for all types of users. In his spare time, he enjoys tinkering with hardware, traveling, and spending time with friends.

Data Specialist: Leona Wada

Leona is a Senior majoring in Economics. She is passionate about environmental sustainability and food sustainability, and is interesting in visualizing data, as well as making it more visually pleasing and easier to navigate. In her spare time, she likes to cook, watch movies, and take film photography.

Web Specialist: Rebecca Petrone

Rebecca is a Senior double majoring in Communication and Early Childhood Family Studies with a minor in Political Science. She is passionate about looking at home technology effects early learning and even more the classroom enviornments. In her spare time she enjoys making coffee, reading and photography.

Project Charter

OVERVIEW & PURPOSE

Even if you think everyone in your group is on the same page, it’s still a really good idea to have a discussion about expectations, ways of working, and even pet peeves. Think of a charter as an excuse to have a healthy discussion.

1. Choose three words to describe the spirit in which your group will work together.

Enthusiastically, cooperatively, and efficiently

2. How will you communicate with each other (e.g., text messaging, email, Google group, Trello, etc.)?

Facebook group chat and Trello

3. Where will you store your files (e.g., Dropbox, Google Drive, server, Github etc.)?

Google team drive

4. When you work on a document collaboratively, how will you ensure that you don’t overwrite each other’s changes?

Google drive updates everyone’s inputs simultaneously so no contributions will be overwritten. As for updating the Omeka exhibit, we will prevent lost data by working together in-person to effectively eliminate any communication errors about overwriting changes, and we will also backup our changes on our own devices so that they can be uploaded quickly in case overwriting occurs.

5. How often will you meet outside of class? Where will you meet? Do you need a regular meeting time? If you’ll schedule meetings as necessary, what days and times are generally good for people?

We will meet when necessary outside of class time on campus, in Mary Gates Hall. We will discuss availabilities of that week via our Facebook group chat and When2Meet and decide then. 

6. When are people planning to be out of town or especially busy? How can you work around this?

Week 5-6, everyone will be busy with midterms/exams for other classes, and people will be out of town for Thanksgiving. We will arrange necessary meetings (in person or online) when needed. From November 6th - 12th Leona is out of town, but will be able to work remotely. 

7. Assign the following roles to project member(s). Please note that no single team member is responsible for any of these roles; rather, the specialist coordinates activity related to this work and assigns tasks to team members. 

    1. Catherine: Project Manager: Pays close attention to schedule and milestones. Alerts the team to possible roadblocks or time-crunches. Ensures that communication among team members is efficient and harmonious. Keeps track of all project documentation. Takes notes at meetings. Communicates team needs (for example, additional training on a tool) to the professor, TA and/or IT Assistant. Communicates with subject-matter expert. Submits milestones on time via Canvas.
    2. Rebecca: Web Specialist: Oversees the design and structure of the site on Omeka.  Works with the CMS (or HTML files) to ensure that the site performs to the team’s specifications. Installs any required updates to the CMS. Archives the project and submits the files to the professor by the end of the quarter.
    3. Leona: Data Specialist: Oversees the cleaning, refining, and augmenting of the group’s dataset. Teaches other team members how to use OpenRefine. Ensures the data is standardized, usable, and well-formatted.
    4. Kevin: Mapping Specialist and Data Visualization Specialist: Oversees the project’s maps. Geolocates data. Learns how to use (and teaches teammates how to use) the appropriate tools. Fine-tunes map display. Adds maps to site. Oversees the project’s data visualizations. Ensures that data is in the right format. Learns how to use (and teaches teammates how to use) the appropriate tools. Fine-tunes data visualizations and adds them to site.
    5. Everyone: Content Specialist: Oversees the authoring of the site’s main narrative and ensures that the data visualizations and maps integrate neatly with the written content. Writes section headers and captions. Obtains necessary images and embeds them in the site. Oversees the creation of the “About” page. Everyone will manage this role by giving input on content and collaborating on the “About” page.

8. Do all decisions need to be unanimous, or is “majority-rules” OK?

“Majority-rules” is fine for our group.

9. How will you prevent meetings from going off-track?

We all have the common goal to work efficiently and use time wisely so we will not want to go off track and waste time.

10. What are group members’ pet peeves from previous collaborations? How will you avoid these?

Not communicating/responding; Having uneven amounts of assigned tasks. We will avoid these by promptly responding to the Facebook group chat and notifying each other ahead of time if we will be absent from class. In addition, we will avoid the inequality in work by strictly following our individual roles defined above in part (7).

11. What will happen to the project when you’re done with it? Will you maintain it, or let it expire?

Depending on how useful and how proud we are about our project, we will decide whether we want to keep it running long-term. It is likely that we will let the project expire because we will have different academic and career responsibilities in the near future that prevent us from dedicating time to this project; however, the data will be maintained and existent on our exhibit because it is all saved on Omeka.

Project One Pager

1. Project Name

Vegetarianism in WWI (VegEv)

2. Objective Statement

Our exhibit will provide textual and topic modelling analysis, alongside the mapping and display of menus, to illustrate the prevalence of vegetarian options in various regional restaurant menus during WWI, (1914-1918), helping us to understand if there was an impact on this dietary trend due to the war effort.

3. Requirements

Our complete exhibit will feature...

Images of menus containing vegetarian options, displaying the names of vegetarian dishes and ingredients.

Mapping of vegetarian restaurants globally and within the U.S. during WWI.

Visualizations of text analysis and topic modelling highlighting the keywords found in these vegetarian menus, and any trends we extrapolate from these visualizations.

4. Out of Scope

We will not address other dietary restrictions in restaurant menus (e.g. gluten-free, veganism, lactose-intolerant) or vegetarianism beyond the timeframe of WWI.

5. Team

Catherine Lin (Project Manager), Rebecca Petrone (Web Specialist), Kevin Huynh (Mapping & Data Visualization Specialist), Leona Wada (Data Specialist)

6. Schedule

Thursday, Nov. 15: have data collection complete and finalize layout of Omeka exhibit

Tuesday, Nov. 20: have data visualizations and mapping in progress (tweaking for presentation/bugs is okay)

Thursday, Nov. 29: mostly complete web content, as in accompanying analysis with the menus, image captions, styling; data visualizations and mapping mostly functional

Thursday, Dec. 6: fully complete project!

More specifics on Trello

Data Management Plan

Expected Data

  • Mapping of vegetarian menus and restaurant locations
  • Comparison of vegetarian dishes across regions (similar ingredients, cooking method, or name), presented in text explanations
  • Data formats will be images and text, downloadable in .jpg, .jpeg, and .png formats. Data will be managed/stored via Omeka, and because all data is open access (except for the few items that have specified rights restrictions, mentioned below) there should be no legal or ethical restrictions.

Period of Data Retention

December 14th, 2018 - the end of our Introduction to Digital Humanities course and the Autumn 2018 quarter.

Data Formats and Dissemination

Images (.jpeg, .jpg, .png) of menus can be downloaded from our exhibit and have full open access thanks to the New York Public Library. Accompanying text analysis is for viewing and educational purposes only and not meant to be copied or distributed. All data, including stock images, are open access except for the team profile photos, worklogs, and visualizations, those are private usage only and rights are specified in their metadata. This exhibit is allowed for display purposes. 

Data Storage and Preservation of Access

We do not plan to preserve this exhibit after the end of the quarter/course; no third-party repositories will be used to maintain our site data. All data will remain stored on Omeka only.