Three out of five and counting...
December 9, 2008
December 8, 2008
I've written the methods of the tableQueryUnit object which do the calculations and build the necessary table cells. Everything seems error-free, but I'm getting an error which suggests that the temporary tables are not persisting long enough to be useful; in fact, they're not persisting through the lifetime of the connection. I've narrowed down the connection creation and disposal to the actual method in the tableQueryUnit object, but that's seemingly not enough to make it work.
There must be something I'm misunderstanding about the way this works, but there are a couple of approaches I could take: first, I could create ACTUAL tables and delete them when I'm done; and second, I could try using mysql_pconnect instead of mysql_connect, to create a (more?) persistent connection. Before doing either of those things, though, I need to clarify for myself why the tables are not surviving through the lifetime of the connection; it's as if they're only surviving through one transaction, which is not how I understood the documentation for temporary tables.
Had walk-through of B015, B005, A051, A012, A015 with committee to give concrete sense of spaces. A051 only room big enough to handle more than 24 students in a class, but is a very large space for and not dividable for smaller classes. Concern about how to provide sound insulation, plain work-tables and tutor areas in A012. Considered various options for adjusting adjoining space and administrative processes to accommodate concerns about A012, and to track students 1 hour a week.
Got template files from Joyce P. Obviously Dreamweaver-based. They include a lot of dreamweaver-specific configuration in commments (e.g. ) So, we'll have to see how difficult it is to modify the tabs using editing environments other than Dreamweaver. As the templates support a very large amount of navigational structure, and most sites will not need nearly that much, we'll need a simple way of pruning out excess code, and of centralizing repeated blocks (which are currently hard-coded into every single page).
As followup to last meeting, posted a couple of points to the sharespace:
- confirm amount of use of Sanako in lab B and C to see if we can get by with only one Sanako lab in future or not
- provide a few details on numbers and types of furniture in B005, B015 and A012.
- enquire about check-in policy in A012 and possibly in other spaces during peak times
- prepare simple floorplan map for next meeting
Met with JS-R to look at the wizard and design the table layouts for the other two tables. Decisions:
- In the current D table layout, the tract set information needs to be removed. It should show up as a list of items below the table, like this:
Victoria 1991 17 tracts. Total pop: 36070 Victoria 2001 17 tracts. Total pop: 33225
and so on, with the "17 tracts" a link to an expandable list of the tracts. - Inside the D table, the existing columns should be split, so that for each city/tractset/year, there are three:
Grp.Pop. Percent D
The first column having the total population for that ethnic grouping in the tracts. - The other tables should follow the plan I laid out on the whiteboard. There is an important requirement that they make very clear the directionality of the figures; the vertical columns represent "exposure of X to other ethnicities", while the rows represent "explosure of other ethnicities to X". This is especially important for the xPY table (table 2), because this table is not symmetrical (as table 3 is).
The deadline for getting the wizard working is the end of the month (which means Christmas). The article should be out in January, so the beta site with the wizard needs to be migrated to the main site by then. The Philadelphia data needs to be removed at that point.
Liz sent me two .doc files to integrate into the studiesinphil document and then turn that into a pdf.
Was a member of the interview committee for the post-doc position in Ray's lab. Did four hour-long interviews by Skype video. One person had slow connection at their end so we ended up using analogue phone, but other three connections were quite acceptable technologically. Then debriefed with Ray and Kim
Simon D and Marri came down to take a final look at the data and the oxygen editor. Marri will get in touch to set up times for her to come in an do the data correcting for the 1790s. Simon will be preparing the 1780s and 1800s. We'll ensure the 1790s data contains everything we want before processing any other decades. Once that's done, then I'll have to write the code to turn the XML structure into relational tables, and then start work on query and reporting php/mysql.
December 5, 2008
Left a bit early.