The course has three main kinds of assignments. The first kind is related to exercises with computer-assisted reporting tools. A short memo should be written for each of these exercises. These assignments are done individually, not as a team. Exercises will be usually be assigned on Wednesdays and due the following Monday.
To get things started, each team will undertake a Web search to explore dimensions of computer-assisted reporting. Consider such aspects of CAR as: courses, both in and out of universities; on-line publications about CAR; organizations supporting some aspect of CAR; resources for databases to be used in CAR. Each team should write a 5-page summary of what was learned, including a conclusion about the meaning and use of CAR in journalism. A class discussion will compare each team's findings and conclusions.
The second kind of assignment is the term project. This involves developing a news or feature story idea that draws on computer-assisted reporting techniques. A key to success with the project is to "work backwards," beginning with identifying a database, moving toward story ideas to be drawn from the database, then data analysis, interviewing and writing. The term project will be very difficult to accomplish if you begin with a story idea and then search for a database that can support the story. Each team will work together to gather a public record database (city, county, state or federal) related to the story project idea. Team members will then write a series of stories (between 3 and 6 stories total) on the topic. Imagine that the final product would be a package that could run across a few pages of one day's newspaper, or as installments over the course of a week. Not all stories need be related to database analysis. Some could be related feature sidebars, for example. The term project is due during the last week of class. You will also present your story in class during that week.
Components of the term project are broken down into intermediate steps, each with their own deadline:
1) Project idea memo describing three potential databases
for the term project is due on Wednesday, September 23. Be as
specific as possible, describing where the database for the story
would come from, possible story angles and interview ideas. Try to
stretch out and go beyond the basic interviews with public officials.
Consider how the story would be developed and whether it would be
multi-part series or a main story with sidebars. See the file of
project stories in the Resource Center, as well as the book of 100
CAR stories on reserve there.
2) Database acquisition memo describing the process that
was used to obtain the project database. This memo should also
discuss the fields that are provided, the quality of the data, and
some potential ideas for analysis.
3) Preliminary interviews memo describing the people you
talked to for developing story angles and directions. Provide some
discussion of what you learned about the overall topic from your
interviews, what you need to be cautious about, and what you need to
explore further, both in terms of records and additional
interviews.
4) Database analysis memo describing what was learned through
examination of the database in Excel and/or FoxPro. Provide a list of
key patterns and discuss their implications for development of the
story. Suggest interviews that can explore and explain your results.
Go beyond a list of top officials.
5) Follow-up interview memo. As before, describe what you have
learned from these interviews and how they are shaping the final
story ideas. Include a basic outline of the form of the final
project, including each story that will become part of the
package.
6) First story drafts will begin to draw the pieces of your
project together. Keep a careful eye to your chosen audience and how
you are telling the story for them. Provide a 75-word abstract with
each piece explaining what it is about and how it fits in to the
overall project.
7) The final story project follows from the work you have done
throughout the semester, and that has been developed and refined by
each of the preceding steps. This should represent your best possible
work, something that could be published with little additional
development.
Each team member additionally will turn in an analysis report that analyzes (a) the research process, (b) what would have been done differently if the project were done again, and (c) the effectiveness of the team's working arrangement.
Another assignment is the project story report, where teams find a project story (preferably one using CAR) in a newspaper of their choice and address the following areas: (1) summary of the story and the separate parts that constitute the package; (2) summary of the reporting resources (database, interviews, etc.) that appear to have been used; (3) a critique of the breadth and depth of the project; and (4) suggestions for further refinement and development of the story. Teams will present this report in class and turn in a written paper for grading.
Finally, a portion of the grade will be based on class participation. Regular class attendance is crucial for understanding the tools and process of computer-assisted reporting. Particpation in class discussions will make the course content more meaningful for both you and others in your class. Short papers reacting to class ideas will help you connect with our topics. Attention to all these aspects will be grade-enhancing.