Category Archives: Group Project Updates

Group project update 4/21

This week the theme of the FOS* group was concretization. Because our team works in Discord channels where everyone routinely posts their latest successes, it’s fun to see things come to realization step-by-step. For example, in order to make the Topics more consistent in the Topic Modeling scheme Eva took out justice names and other common stopwords. Joanne posted about how she was able to get a “protected speech” variable by splitting the data set, then shared what that logic looks like in code! The Figma software adopted by Kevin as the de-facto way to share design work has been a fantastic resource for seeing the evolution of the wireframes and how the comments we made have influenced the shape of the website. And I made stickers of our Project mascot 🙂

Eva and Joanne have been working on getting the Topic Models finalized, which involves running the syllabi to see if reliable categories emerge. Knowing how to “chunk” this information is part of the art + science of the methodology. Having “better” or “worse” topics relies a bit on subject area knowledge but also a general understanding of what kind of text can be grabbed for the software. 

Kevin took our comments on his whiteboard designs, and together we cemented the flow of the website. In tandem with Eva and Joanne, the code Scaffolding page is slowly being fleshed out with lines of code. It’s exciting to get a behind the scenes look at the machinery that will eventually drive the website. 

I will begin posting “educational” style social media posts, in addition to reaching out to law and meme accounts to see if they might potentially be able to start liking our posts. Eva has been sharing with us interesting papers and organizations with contacts we could potentially reach out to. I have begun doing that as well.

We routinely meet every weekend and at least once during the week as a group. Smaller co-working meetings are also held when 2 members have something to advise each other on.

Some things to work on include:

  • Qualitative research of topic models.
  • Creation of web copy including terminology like Precedent and Tests.
  • Formalize the Guided vs. Exploratory format of the website.

Mapping Cemeteries: Research Deadline

This week was a big milestone for us. We agreed that April 15 was our deadline to finish our research. When we set this deadline it felt like we had all the time in the world to leisurely research our locations. Now that we’ve reached it, it doesn’t feel like it was enough time. Regardless, it seems like the correct deadline given the tight timeline. We’re all feeling a bit concerned we haven’t done enough research, but we’re also feeling great about what we’ve learned and the ways our research puts our locations in dialogue with one another.

And it marked a very exciting turn in our meetings. Nadia has been doing amazing work writing code and building our GitHub site. She’s been working hard on a hover feature for our horizontal timeline and a filter feature for our vertical timeline. And she built out our location pages in a way that ties it in aesthetically with the timeline page (organized in boxes). The box design is also making our research feel more manageable–encouraging brevity and showcasing the varied visual assets we’ve found and created. And it’s helping us think more in terms of web text rather than research paper text. When Bret joined our group breakout room, he echoed this. And this week we got to talk about ways we can make the site even better. We talked fonts and colors–and how we can use design across the GitHub and Commons sites to create an even more cohesive user experience.

We also started brainstorming about our logo. We’d talked about logos before, but we mostly wanted to wait until we understood our locations and project better. I’m thinking we may have something to debut as soon as our next project update. Stay tuned!

Thanks to Asma, we also have prompts and recording dates set for our three-episode limited audio series (plus a fourth bonus episode). We’re doing a mix of synchronous and asynchronous recording sessions, all of which Asma will edit and produce with a partner. Especially for our asynchronous recordings, she has us embracing the noises we capture in our background environment as part of our data (rather than something to be edited out). You can listen to our episodes via SoundCloud. We’ll post here when new episodes are ready.

Corona Chronicles: Update on Where We Are and Changes We’ve Made

We’ve come to the point in our project where a lot of the heavy decision making is done, and we’re shifting our focus to processing our student submissions and making the final tweaks to our site. (It’s looking really great, BTW: https://corona-chronicles.world/)

On Thursday we walked through our submission intake process to clear up confusion and ensure everyone is on the same page. When students upload their submission with parent/guardian supervision, it has to make its way through a few steps before ending up in the public gallery space. We think the process should now be smoother and speedier as we all support each other in getting edited submissions up on the site. It’ll be all hands on deck as we’ll probably be ambushed with many new pieces soon—certainly not a terrible problem. But we want to be respectful of how the work responsibilities fall.

Generally, the team is feeling excited about the submissions we’ve received so far. Anytime a new, creative piece is shared in our group meetings we all get big grins on our faces. There’s a real sense of honor I think we all share that these students are willing to share their honest experiences with us and the world.

In our breakout room, Bret reminded us of all the tough obstacles we’ve had to work through this semester: legal documentation, student and parent/guardian consent, working with student consultants, design aesthetics, and ethics of care. Not to mention working through differences in opinion and bandwidth. And along the way, we’ve made many changes to our original project scope, including but not limited to the following:

  • Changing our name from an archive to a collection
  • Not using social media for recruitment
  • Color palette and site design
  • Coming up with a student compensation plan

We’ve been thinking about the $200 stipend, and we all agree that the best use of it will be to reimburse one of the groups of students we’ve been working closely with. We plan to treat them to a pizza party celebration as a thank you for the time and effort they put into the project for us. We also want to give back to the school staff member who offered to translate our student submission form into Spanish. Both myself and other teammates have mentioned in previous posts that over the past couple of weeks we focused a lot on ethics of care and the importance of recognizing the hard work these students are putting in to this. While we of course want students to jump at the chance to create and share with us through their submissions, we know they’re juggling school work and other interests. Elise, our wonderful student consultant, was messaging with Karyn on Thursday evening because she’s been helping us with our logo. She asked if it was OK to get back to us after she wrapped up some homework. We of course would never push back and interfere with that, but it was just a funny moment that continues to make us think about the full context of working with students.

All that to say, I think the team feels comfortable with the milestones we’ve hit, but we know we still have a lot to do to intake the rest of the submissions we have in the queue for publishing. Over the next week you’ll be seeing a handful of new student submissions coming to the site, joining the 3 currently posted ones. Watch this space… we’ve settled into our groove and are making meaningful progress.

NYC Community Fridge Archive – Group Project Update

Omeka Data Entry

As of this morning, we have entered over 60% of the data related to fridges and collections. Our data entry process was complicated by some factors:

  1. As I mentioned last week, Omeka didn’t like us importing a CSV file, so we had to enter every collection and every item manually
  2. Our dataset has a bunch of information that requires more effort to enter: for example, we decided to enter the Instagram handle for a fridge with a link to the Instagram page – same for websites, donation pages, and media coverage. This requires a couple of extra steps that take us some time.
  3. Our dataset (the Google Spreadsheet) was still organized according to our data research, not according to how the Dublincore metadata appear on the Omeka page. Very simply, this meant that we had to jump back and forth on the spreadsheet to copy the information we needed to enter in Omeka. I am happy to announce that our Research Lead (Lola) has edited the columns of the spreadsheet so that now entering the data in Omeka is more intuitive – and thus, easier for us.

Like Bri, I am a fan of Zotero. Zotero is awesome! So, last week I suggested we use Zotero to create a “bibliography” for each fridge. This way, the media coverage does not only look like one long link, but like a proper MLA citation. See the example of the Overthrow Fridge, which had a lot of media coverage because it was the first plant-based community fridge in the city.

I realized that not everyone feels comfortable with Zotero, so I created a tutorial on how to add media coverage to the fridges by using this software, and shared it on our team’s Google drive.

Contributions Page

As I announced last week, the contributions page is up and running. Last night we also did a bunch of testing, to see how different options (and different file types) would look on Omeka. It is our goal to keep testing this function, especially with bigger files, stranger files, and zip files. All kinds of files.

We are all very impatient to receive our first contributions from community fridges, and realized that having “an empty shelf” might not look super appealing to people coming to our website. So, we have decided to start entering:

  • Some of the photos that we took of the fridges. Of course, we need to respect our own terms and conditions, so: no pictures of people without their consent!
  • Articles and media coverage. These will be entered as items in the collection of a fridge.
  • Mission statements and other information that is publicly available on the websites of the fridges.

More Omeka Stuff

We decided to add a page dedicated to “Friends of the Archive”: our stakeholders, meaning all the people we contacted and that gave us feedback, help, and support. Montage will also test out some more functions of Omeka for how metadata are displayed, draft a homepage where we can use CSS, and install OHMS.

Lola also suggested looking at other Omeka projects with basic design, like https://gulaghistory.org by Harvard.

Our next meeting will be dedicated to developing metadata standards for different kinds of contributions: photos, audio, media coverage, poems, stories, and more.

Outreach/Social Media

As many of you have noticed, we have launched a pretty intense social media and outreach campaign. Our Community Outreach Manager (Allison) has figured out a strategy that works pretty well: visiting the fridges in person, sharing images and info about them on Instagram, and then chat with the organizers in the DMs. After establishing a relationship on Instagram, Allison follows up with them via email, to provide them with information about how to contribute to the Archive and how to sign up for the Oral History Project. She will also start contacting the artists that decorated the fridges, to ask them for photos and documentation of their artistic process.

Another important part of outreach will be media coverage: Andy will draft a press release that we can send out to local papers and food media (including podcasts) to promote the launch of our archive. Lola will reach out to CUNY to see if we can get included in a newsletter, or on CUNY tv/radio.

Group Project Update: We have an archive!

We’re Live!

We are happy to announce that our Omeka archive is finally online. This means that not only we have a structure (and a map!), but we’re actually ready to accept contributions from the public in the form of text, photos, and audio.

This is what we are working on this week:

  1. Data entry on Omeka: we discovered that Omeka had trouble ingesting our CSV file with the fridge data, so we have to manually create all the collections and the “fridge items”, which correspond to the “physical object” of a certain fridge.
  2. Outreach: we need to send emails to fridge organizers to let them know that now they can contribute to the archive.
  3. Budget: this week we’ll make our final decision on how to spend the 200$ budget and send the proposal to Bret.
  4. Social Media: we’ll finalize some targeted posts (for example, on “specialty fridges”) and schedule them for the next few weeks.
  5. Research: we’ll check the fridges lists to see if there are any new fridges we need to add to the archive
  6. Tutorial: we’ll be recording a tutorial to explain how to contribute to the archive. We’ll send this tutorial to our fridge collaborators and share it on social media.

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!

 

FOS* Group Project Update #2

This week, the FOS* team managed to complete a lot of the milestones that we’d set before spring break. Joanne and Eva completed the dataset, Kevin finished mid-fi wireframes, and Martin has been consistently keeping up our social media platforms. Additionally, we’ve finished selecting and purchasing a domain for our site, as well as completed our branding (logos, color scheme, fonts). We’ve also, of course, been creating and sharing memes with each other as well. As of now, we’re just fleshing out the details on both the data and design side of things.

Once again, we’re not particularly concerned about time, given the amount of leeway we baked into our schedule. As things are becoming completed, we’re now at a stage where we simply need to flesh out nits and details, and pull everything (dataset, designs, external resources) together into a cohesive whole. The fact that we’ve selected our domain and completed our branding helps in doing this work of making things feel put together. 

We’re also still meeting on Sundays for the most part, though we’ve found that scheduling things on a weekly basis based on our ever-changing personal schedules has been good. We also amp up the amount of meetings per week based on what we need to get done, which hasn’t been a problem either. We’ve also found it helpful to even just work independently on our own tasks in the Discord space together, and ask for feedback or ideas as we go.

By the end of the week, we are aiming to:

  • complete high-fidelity wireframes for the website
  • finish our topic modeling and get started on code scaffolding
  • plan outreach strategy for next week
  • Get started on writing web copy

Corona Chronicles: Progress and Lots More to Come

We were all productive in different ways over the break, so it was great to regroup yesterday and check in on what we accomplished so far and what’s still to come. One great benefit of meeting virtually is that it’s easy for us to invite our student consultants to meet with us. Of course one disadvantage is having to navigate wifi and audio issues. After some troubleshooting we were able to connect with Elise and Sarah who have been working with us and giving their very insightful feedback on our working prototype. Their contributions were our first to intake, so they’re truly essential colleagues of ours and we’re all thankful to be able to work with them.

This week we really wanted to make a decision on our new color scheme for the site and we successfully voted on a single choice! It was great to hear different opinions around our options, and I think we’re all happy with the final outcome. Phil will start to experiment with it and plug it into our Adobe Portfolio site. He agreed to record himself doing this while sharing his screen on Zoom so that we can learn how to make these kind of updates in the future. Thanks for that tip, Elena! Next we’ll be finalizing our logo and font option. It’s interesting that making these design choices can be one of the most difficult parts of the whole project.

We also have a few things to iron out around process flow and standardization. This includes creating documentation around: which Google sheet is the one to pick up student entries from (we’ve had challenges with permissions and version control of shared documents); how to handle different media submission types (video, still photo, artwork, audio, poem/text, etc.) during the intake and editing processes. If Phil’s screenshare recording goes well, perhaps we can have Maggi also record herself while she edits the submissions so we can assist with these activities. These kind of documentation improvements will help everyone work efficiently and on the same page.

Lastly, we ended yesterday’s meeting with a wonderful discussion around how to care for all of the students taking the time to participate in our project. We’re so grateful to them for sharing their thoughts and artwork with us, and we recognize that this is actually a lot of work that we’re asking from them. Vallerie brought up the important point that some students might be triggered while following one of our prompts and digging up a traumatic memory from surviving the pandemic. We also need to remember that not all students have access to the technology and equipment needed to upload media files. While we briefly touched on versions of this earlier on in the semester, we came to the conclusion that not fully realizing all of this until now isn’t a failure. It’s really good and important that this is coming up and we shouldn’t beat ourselves up for not better clueing in and solutioning this earlier. In our meeting this weekend, we’re going to dig more into what Karyn and Vallerie have heard from students and educators during their outreach activities. We’re also going to explore how to use the generous $200 to give back and return our thanks to these groups of participants.

Lots more to come…

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.

FOS* group project update #1

This week, the FOS* team got our website and our two social media sites up and running. Joanne put in some crucial legwork on our dataset, Kevin designed our landing page and starter style guide, Eva built the landing page, and Martin sorted out our social media posting schedule and organizational software. All of us also made and/or critiqued each others’ memes as we worked on bulking up the content we have to share.

We set some very ambitious goals for making a complete, clean dataset, as well as for finishing the website’s midi-fi wireframes; this is obviously the best way to lead up to saying those aren’t done yet, but they’re being done properly. As a group, we’re not concerned with being behind on those deadlines, since 1. We baked in enough time to be “behind”, 2. There is no way of rushing quality data here and 3. More time on the data means more time available for designing. 

We’ll meet, as usual, on Sunday. This week, Joanne outlined some QC and data-sorting tasks that are best done manually, so we’ll apply an hour of our time together towards that. We like to work in a Discord voice channel, which has a great coworking vibe and relevant tech capabilities without the complication and screen fatigue of videoconferencing. 

By the end of Spring Break, we’ll aim to have:

  • our dataset finished
  • Observable prototypes for visualizations
  • Mid-fi wireframes complete for the website
  • 2-3 posts per week on our social media + engagement with other relevant accounts
  • Outreach to CUNY law students (and others, potentially)