OpenNews wants to help you get to events, plus meetups later this month.
In researching Settling for Misconduct, we had to account for details from hundreds of county and federal court filings, identify thousands of officers named in civil complaints and tally hundreds of millions of dollars in monetary awards. We also needed thorough reporting to connect issues of police misconduct to fiscal accountability. And oh yeah – we had to have a slick web app to present the data to the public.
Slow start to the new year for events, but that means more time for fellowship applications.
As a Knight-Mozilla fellow, I wanted to do some type of research during my fellowship that could benefit the news community. During my 10-month fellowship in Berlin in 2016, I spent about eight months researching, collecting data and interviewing reporters, editors, managers, and directors about their on-boarding and off-boarding processes.
Working in the news cycle often leaves little time to design different iterations of story ideas, and even less time to test them with an audience. But as an author or designer—and as a media outlet which provides a public service, like WNYC at New York Public Radio—we have a responsibility to know how the public might understand and engage with our stories. The reason to make time for some kind of usability testing is because it makes our work better and increases its impact on the audience we serve.
We wanted to get a better idea of where President-elect Donald Trump gets his information. So we analyzed everything he has tweeted since he launched his campaign to take a look at the links he has shared and the news sources they came from. But first, we had to get the tweets.
Lessons learned from trying to create one chart with as many applications, libraries, and programming languages as possible.
This week, eleven contributors gathered with us in Washington, D.C. to work on a new resource—a playbook for open-sourcing newsroom code. Together we hoped to tackle a question that’s come up again and again: how to help more newsrooms produce open-source projects, so that everyone can spend more time on great journalism instead of re-creating common tools, tech, and datasets from scratch.
Cleverly named meetup from Journocoders, and a scant few other events and deadlines before the end of the year.
The Los Angeles Times created a new publishing system by focusing on the needs of editors and reporters, supporting great journalism with better tools.
Deadlines this week for the JSK fellowship and IFF conference, plus some upcoming events.
We can take advantage of our human ability to analyze natural language and use really simple techniques to assist and amaze our users. Here are a couple of ways to use these techniques in your own projects.
Session ideas are due soon for the Internet Freedom Festival, plus a bunch of other upcoming grant and fellowship deadlines.
Applications for ONA’s Women’s Leadership Accelerator are due tomorrow, plus other events and deadlines.
OpenNews (and thus Source) exists to do one thing: to help a community of newsroom technologists, data scientists, and interactive designers thrive. We believe in the value of the work, now as ever. We will continue to look for new ways to support what you do, and to support you, as human beings. For now, we offer some links to your work on the way the vote went down, a map of loss, images of new Europeans, strong words, and more.
If you’re not buried in elections work, there area few events this week and upcoming deadlines to check out.
We created a tool that allowed users to peek under the hood of the MLB playoffs by simulating the postseason as many times as they wanted, which we hope taught even baseball fans something new about their sport.
The Mozilla Festival is back this weekend. We’ll be in London and have coverage here on Source.
For the presidential debate season, NPR is providing live transcripts of the debate with embedded fact checks and annotations throughout each debate night. Coordinating the workflow between live transcriptions, live fact-checking, and a live-updating page inside of our CMS was no small undertaking, resulting in what may have been our team’s most complicated technical architecture yet.