#BetaBagels 011 – MTA Open Data Team

Join BetaNYC and the Metropolitan Transportation Authority (MTA)’s Open Data Team for a briefing on their recently published operating budget data and a general overview of their work.

In this session, we’ll meet the MTA Open Data team and learn about their commitment to sharing data publicly. Grab a cup of coffee or tea and meet them! The team will provide an in-depth look into how the MTA’s operating budget process works. Additionally, they will demonstrate how we can conduct insightful analyses. Come prepared with questions and curiosity. Together, we will dive into their operations, subsidies, and headcount datasets! 

The MTA Open Data program is managed by the Data & Analytics team at the MTA. 

This event will take place on June 5 at 9:30 am on Zoom with closed captioning. We will speak in English and use technical terms. During the presentation, there will be a demonstration of Tyler Technology’s online visualization platform at https://data.ny.gov (formerly Socrata). If you would like to save visuals that you build during the event, it is recommended that you create an account before we start. All you need is a browser; no complicated technical skills or special software are required to participate. 

At the end of the presentation, we will open the floor for discussion and questions.

Links to Datasets: 

When: Wednesday, June 5, at 9:30am on Zoom

RSVP via Zoom: https://bit.ly/betabagels011 

What is BetaBagels?

BetaBagels is a breakfast salon series organized by BetaNYC. We invite New Yorkers interested in government at the intersection of technology, data and design. 

In 2018, we first invited New Yorkers inside the Municipal Building and brought transparency to the municipal government.

BetaBagels has served New Yorkers as a briefing on what’s going on and who’s who in government. Each event features civil servants and local leaders whose work is transforming government operations from the inside out. Through informed dialogue, we build bridges between municipal government and the people and communities that use municipal services. 

BetaNYC’s Code of Conduct for Events:

BetaNYC enforces a Code of Conduct at all of our events. We expect all event participants to adhere to it and will terminate attendance if anyone violates it. 

We believe in a welcoming and safe community for all. Our activities and events should foster meaningful collaboration between participants, community members, and government partners. We expect internal governance, participants, advocacy, activities, and events to:

  1. Provide a safe, respectful, and welcoming environment where all are free to fully express their ideas and identities free from discrimination or harassment. All spaces, online or physical, shall be governed by BetaNYC’s anti-harassment policy.
  2. Default to open and work to be objective.
  3. Collaborate for the purpose of generating ideas that empower, innovate, and develop local capacity.
  4. Presume the value of others and cherish everyone’s ideas, skills, and contributions.
  5. Encourage participants to listen as much as they speak, ask respectful questions, and demystify context.
  6. Foster energy that builds “yes, and” ideas and permits the ability to stretch.
  7. Build ideas, tools, and platforms that are open and free for reuse. Activities should prioritize public use, not private gain.
  8. Work to prioritize access for and input from those who are traditionally excluded from the civic process, be inclusive of all Boroughs, and be considerate of our Hudson River neighbors.
  9. Actively involve stakeholders, community groups, and those with subject matter expertise in all decision-making processes.
  10. Ensure that relationships and conversations between, and among, stakeholders e.g. elected officials, their staff, and government representatives, community based organizations and their partners, and members of the BetaNYC community — remain respectful, participatory, and productive.

Please visit our blog post on our community written code of conduct and anti-harassement policy or GitHub page.