MS brought the map in; GN and I scanned it, then I optimized it a bit and tiled it, and generated the OpenLayers basic site using modified code from MoEML. It's working. I will need to make a lot of changes unless we can integrate categories into it; removing them from the existing code will be messy.
Updating computer schedule with additional Jan - April 2015 bookings
Confirmation emails sent to computer users
I met with NB on Tuesday to review situation. Progress is very slow and I will have to get back to projects deferred in the fall to accommodate this one, so I'll likely have fewer hours per week for this project going forward, thus progress will continue to be slow. No idea when I'll be able to provide substantial deliverables.
Contacted AS of OJS to ask which of two approaches to intercepting messages seemed a better option. He suggested a combination of both and suggested I look at the referral plugin that he thought might be helpful. Will do that in week 2. Tidied up a few things in the code.
Late duty, and last minute requests for data.
Opened up a section for submission for the new Issue 9 (conference papers from 2014), proposed a solicitation email to JW and RVDB, compiled a list of presentations, presenters and emails, and generally prepared for the campaign to get those contributions in.
Our new DR students started work today, and have made good progress, with some bios looking ready already. CH has encoded hers and they've been uploaded for proofing. CH also pointed out some discrepancies between the Guidelines explanation of the fn tagging and the actual practice, so we had a quick email discussion with KSW and GL about it, and we'll clarify. There are also some individuals tagged in 63 as fn, who don't appear to me to be fn; GL and CH will examine this more closely.
Added the ability to pass a location as a "container" and have all contained or contiguous features automatically turned on. OL currently has no test for intersection of geometries, just for intersection of a geometry and an extent (rectangle), so that's what I'm using; but an email discussion has generated a possible approach to testing geometry intersection in a quick-and-dirty way, until this function appears in OL (or in case it never does). Will implement when there's time.
Skype with SF and JS-R, after which SF made the final assignments for gen 1 custodian sales, and I generated the candidates for gen 2. I also added a new field to the titles table in which we can record the generation at which a chain became "polluted" by the admixture of properties that were not part of the original set (in this case, custodian sales), so we can track that.
We also discussed a procedure for assigning tentative ethnicity values based on the UC database; I'm not very clear on how or why we're doing it this way, so I've laid out the steps as far as I understand them to get confirmation before proceeding. I've also pre-generated lists of strong-probability Chinese and Asian (all of them) names, for use when it's clear what we're doing.