I finished the "selection" portion of the summary report script. It's basically a question/answer kind of thing in order to narrow down the activity sequence that the user wants to summarize. Once the sequence has been identified the user is given a list of all the activities in that report. The user checks a box next to each activity and submits the form, which then presents the details of each activity. I guess it's not really a summary report since what's returned is all the information related to the activity it's more of a detail report.
I'm currently working on the actual report page. I haven't gotten very far just yet, but I suspect that I can hammer this out in a day (Friday to be exact). I have sequence info listed and the beginning of the activity info. I should be able to duplicate some of the script relating to the sightings from other portions of the utility. Of course, the trick comes from making the script generic enough to handle both enacted and literal while at the same time providing the information specific to each analysis. Thinking about all the data related to each type of analysis and all the possible stages of analysis can be a bit mind-boggling at times (what needs to be included, what tables need to be linked, how the data is to be represented, what if something has yet to be rated, etc.).
I think it may help to have a summary of the results somewhere on the document. Maybe at the top before the activity details are presented. I'll have to talk to KM about that.
