I've completed the literal portion of the reporting functionality. It looks decent, though usability could be improved somewhat by making the report more modular using a show/hide scenario or something like that. As it is, the document gets pretty large depending on the number of activities chosen from a sequence.
The enacted sequence is taking a bit longer to prepare, but I think it's coming along. I've got the framework down for getting the information. The basic info for an activity is being pulled same as with the literal, but I need to make a few modifications to allow for the sighting details to be pulled.
I'll need to do quite a bit of testing to ensure that the report accurately reflects the data stored in the database. I'm not as concerned about the data itself but of the various posibilities when data is not present (omitted, never entered, etc). Plus I'll need to make a few stylistic decisions on how to represent the various situations. I want to ensure that the representation of these various possibilities is accurate in the report. I should be able to do a comparison between the editing screens and report screens to get a good feel for whether or not the accuracy is there.
