Chapter summaries

[Jen Reese]

Carolyn:
> On the discussion of the smaller incidents, it is difficult to
> have one rule to fit them all. My definition as I have coded to 
> chapter is if there was no other useful place to put it. Eg, 
> discussions of the valentine in CoS - who sent it & why. Whilst 
> that can be cross-coded to the various characters involved, in 
> essence it is discussing an incident in Chapter 13. However, your 
> JFF example should most probably go to the character, as you 
> suggest.

Jen: I forgot to mention the posts coded only to the chapter. I'm 
definitely keeping smaller incidents coded here esp. if there's no 
other logical place to start looking. Like you said, sweeping 
through a review of Ron's category to find a discussion on the slug 
incident with Malfoy would be infuriating. 

Carolyn:
> The next thing is the chapter summaries and the questions related 
> to them. Obviously, the headline summary should go to the chapter 
> code, but then my rule of thumb has been to code reponses on a 
> diminishing returns basis - ie, once they start to wander off into 
> separate sub-threads rather than stay answering all the questions, 
> I stopped coding to chapter.

Jen: As you know, I can't help myself from coding-to-thread a bit in 
these chapter summaries. Continuity and all. And right now we're 
still talking about *very few* chapters with more than 25 posts. I 
suspect in the end only a handful of chapters will have 100+ posts 
to wade through, maybe upwards of 200-300 when we get to post-OOTP. 
More than that would just be recycling the same arguments with each 
new wave of posters. We'll just have to pick the most definitive 
posts at each junture and then cull to the best of the best.