- Project name: Condition of Anonymity
- One-line description of project: A fun way to explore the reasons the New York Times has given for granting anonymity to a source.
- Project URL(s), if applicable: Info will be published to a Heroku project and streamed to our Twitter account: @conditionof
- What are you building: Basically, this is a fun way to explore the reasons the New York Times has given for granting anonymity. We've got a method for consuming all articles published in the New York Times that contain statements from anonymous sources, a website to display the reasons the source was given anonymity ("because clause"), and a Twitter account @conditionof to stream new articles through time. The corpus is all NYT articles since January 1, 2000 that contain the phrase, "condition of anonymity" or "anonymity because". Users can click on any word in any because clause and see a chronological list of every because clase that contains that word.
- Who is it for: This site is for New York Times aficionados, click-happy types who like Internet rabbit holes, and people who dig getting data from unstructured text.
- Your goal for this weekend: Pull the relevant articles (done), analyze text (done), and publish the processed text in a chron list (done). Later: add ab about page, stream the because clauses on Twitter, and publish the Web site.
How is this project useful? It serves to highlight and draw attention to the reasoning given for using anonymous sources, and it does so in an accessible, entertaining way.
- Where is this project going and what lessons/concepts can be applied to other projects? The goal project is to have a web application and Twitter bot that tweets out reasons given for anonymity. More generically, this is a lightweight way to find structure and data in unstructured text. Many industries use consistent phrasing (e.g. style books for journalists, standard operating procedure in police departments), and it makes it easy to find consistent phrasing with a minimum of programming effort. And, sometimes organizations use common phrases as a defense mechanism (e.g. no comment), but this turns that approach on its head because the consistent language is exactly what makes it so easy to find, gather, and analyze repeated references.