I wrote a little piece of code that identified 624 rows in BI's spreadsheet which contain values in the keyword field that don't appear in the keyword sheet, then submitted a report to BI. He'll need to update the keywords sheet and the records in the main sheet and return.
Added bit of code to identify rows which have NULL in the chapter field. It's OK to have NULL in that field, but I gave BI the report in case some of those rows should have a value in that field.
Added bit of code to identify rows which have NULL in the document_type field. It's OK to have NULL in that field, but I gave BI the report in case some of those rows should have a value in that field.
Marked up a 1789 map of Ahousat. It doesn't look much like modern-day Clayoquot Sound, though, so I've found it almost impossible to set the Google Map coordinates with any precision.
Did the header and metadata, and also marked up the biblio, which is relatively short. Sent two questions to JT on biblio items.
The live site and dev site are now identical, featuring all tables. Next I have to look at the possibility of sorting relational field drop-downs in descending order of id (to bring the newest to the top).
Went back to square one and created a new QSortFilterProxyModel to filter the list of xml:ids coming from the HcmcImtDoc object. This has solved the problem; I now have a working regular expression filter in the GUI, which can be used to select items in the list.
A new problem has emerged, though: each xml:id in the list is duplicated. This is not caused by the new filter; if I change back to the original unfiltered behaviour, I still get two of each item in the list. So this is due to what looks like duplicated code in HcmcImtDoc, which I think ended up in there when I was making changes to allow switching on and off of namespace-awareness. Shouldn't be hard to fix.