Lindsay Poirier

Lindsay Poirier

Cultural anthropologist of data cultures; Assistant Professor of Statistics and Data Sciences at Smith College

DEAL Lab Book

Introduction

Welcome to the Data Ethnography and Advocacy Lab Book! Here we outline the values that guide our work, group roles and responsibilities, protocols for facilitating meetings, guidelines for documenting our work, and expectations on group conduct.

These protocols are inspired from the work of several groups that inspire us - in particular the Carceral Ecologies Lab Book, the CLEAR Lab Book, the Aly Lab Manual, the PECE Design Team Protocols, and the Energy Rights Project Protocols. In-text citations are provided throughout the document where text is drawn directly from these sources documents. Full citations of these resources are listed in the References section.

Further, the protocols are continuously being collectively (re)authored as new members join the group.

Lab Values

Compassion

In this group, we care about each other, not just in our work lives, but also as individuals that have lives outside of this work. We encourage our collaborators to prioritize their personal health and well-being before our research, and we respect each other’s personal boundaries. We strive to embody kindness in all of our interactions with each other, and attempt to show up for each other in moments of distress. We honor each other’s identities and backgrounds.

Community

In this group, we strive to foster a supportive research environment. We show respect for each other’s time by setting clear expectations on project timelines, roles, progress, and issues. We assess progress towards goals often, adjust our expectations when necessary, and offer flexibility/wiggle room when unexpected circumstances come up. We make an effort to coordinate our work with an understanding that we all have unique work styles. We consistently keep lines of communication open, especially when things are not going as planned or when conflicts arise. We work to develop trust in each other by following through on commitments and showing respect for each other’s ideas - both in moments when we are in agreement and in moments when we are offering critique. We offer mentorship in cases when we have specialized knowledge to share, and we acknowledge the unique knowledge that everyone in the group brings to the collaboration. We celebrate each other’s successes and hype each other up in moments when we feel discouraged. We strive for consensus in our decision-making and understand that this, at times, requires compromise.

Grit

In this group, we work hard toward our goals. We are proactive problem-solvers, taking initiative in order to persevere as challenges arise. We set the intention to follow through on our commitments. We recognize the significance of diverse kinds of labor - from the most tedious and monotonous to the most innovative and creative.

Purpose

In this group, we work towards a collective vision of advancing social and environmental equity, justice, and accountability through improvements to data infrastructure. We are transparent about the social and political aims of our work to newcomers and in public presentations of the work. We seek out opportunities to advocate on behalf of interventions that align with our collective vision. We prioritize our collective vision when making decisions about who will be invited to participate in the work, which groups we will seek input from, what resources we will accept/leverage to support the work, and through what channels the work will be disseminated.

Integrity

In this group, we are committed to presenting our work with honesty and context. We value reflexivity in our research practice. We acknowledge what we don’t know, can’t know (due to our unique positionality), or have yet to learn. We listen carefully, especially to perspectives held by those with cultural identities we do not share, and are willing to have assumptions challenged. We admit mistakes, learn from them, and then move on from them.

Roles and Responsibilities

Joining the Lab

We are thrilled to invite new members to the lab. When joining the lab, you should do the following:

  1. Read this lab book.
  2. Email Lindsay or the Lead Mentor and ask to be added to our Slack Workspace. Check out this tutorial if you are new to Slack.
  3. Join the #onboarding Slack channel, and follow the instructions in Lindsay’s October 4, 2021 post.
  4. Join Slack channels related to the projects you will be working on and read recent correspondence in these channels. Configure your Slack notifications in these channels.
  5. Create a GitHub account, and send Lindsay your GitHub handle.
  6. Create a Zotero account here and install both Zotero and Zotero Connector here here. Send Lindsay or the Lead Mentor your Zotero username so they can add you to our shared Zotero account. Then watch this video, introducing Zotero.
  7. Ask Lindsay to be added to the shared Google Drive. See if you can find your work folder for this semester.
  8. Sign-up for a Dedoose account here. Then install Dedoose Desktop Application here. Ask Lindsay or the Lead Mentor to add you to our shared Dedoose project.
  9. Complete CITI Training here (Navigate to Required Online Ethics Training and follow instructions). You should complete the Basic Human Subjects - Social and Behavioral Course. Send me a copy of your certificate upon completion.

Faculty Responsibilities

This section draws heavily from the Carceral Ecologies Lab Book and the Aly Lab Manual

As the director of the Data Ethnography and Advocacy Lab, Lindsay commits to:

  • Support you (academically, intellectually, emotionally, financially)
  • Provide timely feedback on project ideas, data analysis, writing, and presentations
  • Review and approve timesheets on a timely basis
  • Be regularly available in person and via email to discuss both lab-related research and other research interests
  • Support your career development (e.g. helping you network with people in the field, introducing you to infrastructures and workflows that may be relevant to your future career, writing recommendation letters, and inviting you to attend conferences when finances permit)
  • Ensuring that you are acknowledged for your contributions in all presentations of our work
  • Encourage you to prioritize your physical and emotional well-being before other obligations

Student Researcher Responsibilities

This section draws heavily from the Carceral Ecologies Lab Book and the CLEAR Lab Book.

As a student researcher, you will be expected to:

  • Take care of your physical and mental well-being first. If you are sick or burnt out, please stay home. If possible, let us know ahead of time that you need to step back. The Schacht Center has a number of resources available to help navigate distressing times.
  • Attend weekly lab meetings. Lab meetings are held weekly for one-hour. In these meetings, we discuss how we operate as a lab and as a community, along with our progress on a number of projects. Please let us know ahead of time if you cannot make a meeting via the #general channel on Slack - preferably at least 24 hours in advance (though we recognize this is not always possible). You do not need to explain why you cannot attend a meeting in this message, but please don’t create a habit of missing meetings.
  • Take personal initiative with group support. While we collaborate as a team, each individual member of our group has a personal responsibility to ensure that their contributions to the work get done. There will not be a great deal of oversight of your work, so we expect that each member will take steps to manage their time effectively, honestly communicate their capacity to contribute, and let us know if/when they need to re-evaluate their time commitments. To help cultivate and sustain this culture of accountability, all group members are encouraged to support each other by outlining manageable tasks, helping out with tasks in times of struggle (when asked), and respecting a group member’s decision to step back when needed.
  • Problem solve when you can. Ask questions when you are unsure. We are all here to help each other navigate this work, and we encourage you to ask questions and request help when it’s needed. Still, attempting to problem solve when you can demonstrates that you value your collaborator’s time, so try that first. If you learn how to do something that might be helpful to others, share it in our Slack Workspace!
  • Contribute to a caring and collaborative environment. Celebrate each other’s successes, respect each other’s individual strengths and weaknesses, demonstrate compassion for each other’s struggles, and affirm each other’s diverse identities.
  • Mistakes happen. Admit mistakes, and then move on.

Assignment of Roles

Roles get assigned to members of the lab that have already been with us for a full semester. After your first semester as a lab member, you will be expected to take on at least one role per semester. Roles will be assigned during the previous semester’s last lab meeting and will be rotated every semester. Roles will be determined on a volunteer basis and confirmed via group consensus.

Note-taking will be a shared rotating responsibility. We will maintain a spreadsheet listing who is responsible for note-taking in the Google Drive.

Lab Manager

  • Schedules meetings and sends out meeting reminders
  • Takes attendance at all meetings
  • Point person for attendance
  • Archives zoom recordings
  • Manages assets
  • Manages Kanban

Documentation Manager

  • Responsible for keeping Google Drive organized
  • Responsible for ensuring that each GitHub repo meets requirements outlined in the Documentation Guidelines
  • Maintains to-do lists on our documentation

Web Manager

  • Responsible for keeping the website up-to-date
  • Maintains a blog publishing schedule,
  • Collects and edits blog posts from collaborative teams,
  • Collaborates with social media manager

Social Media Manager

  • Responsible for finding relevant organizations to network with and follow
  • Responsible for posting news stories and videos relevant to our work
  • Responsible for advertising blog posts on social media

Lead Mentor

  • Point person for new members
  • Checks in with new members regularly
  • Answers or directs questions in the #newbies Slack channel

Event Manager

  • Maintains lab calendar
  • Main point of contact for guest speakers (managing scheduling, setting up meeting times etc)
  • Plans end of semester social event
  • Maintains list of lab birthdays and sends birthday cards from the lab

Exiting the Lab

We understand and respect that you may need to step away from your position in the lab to prioritize attention elsewhere. As advocates for your success, we also celebrate when new opportunities arise! If you need to step away from your position, you should reach out to Lindsay as soon as possible. We will set up a meeting to discuss how you should document the state of your work and to complete a short exit interview.

Communication

Slack

Slack will be the primary means of lab communication. Here is a link to our Slack Workspace. This Slack channel is on the Smith Enterprise Workspace, meaning that anyone with a Smith email address can immediately be added to this Workspace and view and join all public channels, but guests must be invited and manually added to relevant channels. When posting message, please be sure to post in the relevant channel:

  • #general: announcements to all group members
  • #[project-name]: communication regarding a particular DEAL project
  • #support: questions about the group protocols, timesheet reporting, or other group infrastructures
  • #cheers: celebrate lab member accomplishments or express gratitude for a lab member’s work
  • #random: non-work related conversations

Since Slack is our primary means of communication, you should check Slack regularly. You may wish to install the Slack Desktop application to help keep track of Slack messages. You can also configure Slack to notify you when messages come through on specific channels. You are not expected to respond to Slack messages on evenings and weekends.

GitHub

When you join the lab, you will be added to our GitHub organization. There are series of repository templates available for creating new GitHub repositories. We’ve created these templates to ensure consistency across our folder structures and completeness in the contents of our README documents. Please be sure to select the appropriate template before creating a new repo. Reach out to Lindsay if you are unsure of which template is most appropriate.

Lab Meeting Protocols

The general format for all lab meetings is as follow:

  • Opening: Lab manager disseminates link to meeting notes document and takes attendance. Note-taker is determined by referencing the rotating note-taker schedule in the Drive.
  • Group check-in: Lab manager asks the group check-in question: Where is your head and your heart today? Everyone has an opportunity to respond (round robin style). Members may pass if they choose.
  • Project updates: For each project, group members detail what was accomplished since the last meeting, what they plan to accomplish in the coming week, and what is getting in the way of being able to accomplish those tasks. Everyone has an opportunity to ask questions.
  • Lab check-in: Group members have an opportunity to ask questions or voice concerns about any aspects of lab operations.
  • Summary: We close each meeting with the note-taker summarizing to-do list items for the next week.

Documentation

Lab Meeting Agendas and Meeting Notes

All lab meeting agendas and notes will be stored in one running Google Drive document. In this document, each new meeting should be marked with the date of the meeting formatted as ‘Heading 1’. This will ensure each date appears in the document’s table of contents so that we can quickly navigate to those notes. Notes should list who was in attendance at a meeting, along with pertinent information discussed during the meeting.

Google Drive

We maintain a shared Google Drive for all shared lab documents and files that are not hosted in GitHub repositories. This may include:

  • lab meeting agendas and meeting notes
  • lab planning documents
  • datasets that are too large for GitHub storage
  • drafts of collaboratively edited manuscripts, abstracts, or proposals
  • data inventories and quality assurance checklists
  • spreadsheets for lab contacts
  • tutorials
  • etc.

Code and Data Documentation

For code and data documentation, we will follow the Hack for California Guidelines (soon to be updated and adapted for our specific work.)

Authorship & Acknowledgements

As members of the group, you may be asked to participate in the preparation of manuscripts, presentations, or other forms of media presenting our work. As the faculty lab director, it is Lindsay’s responsibility to ensure that:

  1. Group members are properly acknowledged for their contributions to the group in all presentations of our work.
  2. Opportunities for authorship and presenting our work are equitably distributed across group members. Note that, while we will always work to value and reward diverse forms of labor in this group, promoting equity in authorship sometimes means prioritizing credit to those that, for a number of reasons, haven’t been able to contribute quite as much as others. See Liboiron, Max, Justine Ammendolia, Katharine Winsor, Alex Zahara, Hillary Bradshaw, Jessica Melvin, Charles Mather, et al. 2017. “Equity in Author Order: A Feminist Laboratory’s Approach.” Catalyst: Feminism, Theory, Technoscience 3 (2): 1–17. https://doi.org/10.28968/cftt.v3i2.28850.
  3. Clear and direct conversations about authorship and acknowledgements are held early in the process and are revisited as necessary as the work progresses.

Code of Conduct

This anti-harassment policy is based on the example policy from the Geek Feminism wiki, created by the Geek Feminism community. DEAL is dedicated to providing a harassment-free experience for everyone, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, age, race, or religion. We do not tolerate harassment of participants in any form.

This code of conduct applies to all DEAL spaces, including lab meetings, our Slack Workspace, and our GitHub, both online and off. Anyone who violates this code of conduct may be sanctioned or expelled from these spaces at the discretion of the project director.

Some DEAL spaces may have additional rules in place, which will be made clearly available to participants. Participants are responsible for knowing and abiding by these rules.

References

Aly Lab. (2021). Aly Lab Manual. Columbia University. https://github.com/alylab/labmanual/blob/master/aly-lab-manual.pdf

Carceral Ecologies Lab. (2021). Lab Book (draft version) University of California Los Angeles. https://github.com/Carceral-Ecologies/lab_book

CLEAR. (2021). CLEAR Lab Book: A living manual of our values, guidelines, and protocols, V.03. St. John’s, NL: Civic Laboratory for Environmental Action Research, Memorial University of Newfoundland and Labrador.