I spent a large chunk of today exploring possible Javascript-based visualization tools for the histogram feature, which is intended to show trends over time based on any number of criteria. There seem to be two clear frontrunners:
Previous post update: the problem appears to be a bug in the pam code itself which allows this kind of behaviour in some cases. The developer thinks it's possible that our system is allowing clients to anonymously bind. Fortunately there's a patch for that. Unfortunately recompiling PAM is close to being the last thing I want to do. Fortunately, there's a new version (v0.7.13 vs. the current v0.7.6) from Natty that installed with no drama. Also fortunately, it works!
I've installed it on carrot to test it in the real world.
I also spent a good deal of time submitting a bug report on Launchpad (Bug #720401).
Met with AC to discuss the db structure in detail, and worked out a more complex list of fields to add to the simpler of the two original options. Created a new schema document, and built the database, including some core data in the gender table that shouldn't need to be edited. I then started work on building the GUI, and found a couple of things I wanted to tweak in the AdaptiveDB code, so I've done that:
The db is now functional, and I've put in a bit of test data in the dev one and played around with it. When AC's research assistant comes down (Friday?) we'll do the training on the dev version, then start serious work on the empty live one.
Entered author's proofing corrections and swapped some em dashes for other punctuation.
Done on DR's instructions.
SM is working on abstracts, and we've now set him up with access to the SVN. He's working on 1852.
Had a bit of difficulty finding where this code resides, so I'm blogging it. The actual location of mallarme.uvic.ca is /lang02/www/fall07/coupde/penultima2/web_pages.
At ER's request, I've made the popup div position: fixed. I also noticed that clickable elements didn't have a pointer cursor, so I've fixed that. Just two minor fixes in style.css.
Made some good progress on the search interface today. Instead of having one Search class to handle both searching and returning one record, I wrote a separate Search_Single class that handles fetching a trial file based on a passed ID. Since a trial file can have multiple trials, respites, and outcomes (but only one criminal), the Search_Single class grabs those associated records via separate queries. Meanwhile, the main Search class simply does a LEFT JOIN on the trials, outcomes, and respites table to find at least one record that matches the search criteria.
I chose the trial_file as the 'main' table for the search because it's the parent for trials, respites, outcomes, and criminals. Since there's only one criminal per trial file but potentially multiple trials, respites, and outcomes, the trial file makes the most sense because we don't want the same criminal to show up multiple times in the search results, which would happen if we were to search with the trials table as primary.
JN and I went up to see AS for some advice about procedures for the end of year activities on the HCMC FAST account. It seems all our ducks are in a row; we'll do one final check through all the entries together some time in March, and we need to submit a letter about carry-over by mid-March.
Compiled some stats for govlet.ca and coldesp for the ACDP performance indicators report, for CP.