Worked on mol-includes all day and I'm now at a version that is at least coherent, correct, and complete. It still needs to be rationalized, but that's a larger project (that may be in conversation with TEH's recent work on the teiHeader). Also added a schematron rule for local pointers; the only thing holding us back before was that it made Stow a pain to validate (another reason why splitting Stow is the right idea).
July 10, 2018
Got started on a plain statement of our principles, arising out of what we've learned, which may form the basis of our white-or-not-paper. Lots of input from various people, and it's beginning to take shape.
Did the keywords for the second of my assigned interviews; also noticed a common tendency to include leading or trailing spaces in name elements, so I added a Schematron rule for that, and fixed all existing instances.
Did DM's timesheet, which required Windows, which required updating, which took four hours in total. FFS.
After rebuilding my desktop, VirtualBox worked fine except that my Windows VM could not connect to the shared folder I had configured for it. After finding this page, I was able to run this command:
VBoxManage setextradata "Windows 10" VBoxInternal2/SharedFoldersEnableSymlinksCreate/vmShare 1
where "Windows 10" is the name of the VM, and "vmShare" is the name of the share, then restart the VM, and it worked. Obscure thing, so I document it here. The issue is that the path to the shared folder depends on a symlink on my system, since the shared folder lives on an encrypted data drive, not the system drive.
July 9, 2018
Met with MDH today to discuss the plan for putting Stow back together. Most of the big concerns were regarding rendition elements and pointers. I've been able to implement the first bit of the plan today: getting the renditions rationalized. It's a multi-step process like so:
- Create an XSLT based off of each include (i.e. find all the documents with mol-include, resolve those includes, and then process each of the included documents). This uses pre-existing code for the standalone.
- Copy over the XSLT and its corresponding document to a temporary directory
- Use the pre-existing for-each target to apply the XSLT to the XML file (it takes longer than I'd like, however, but I don't think there's anyway to make it go faster)
- Now process the files that have the includes and bring in the stuff that's meant to be included; since all of the rendition selectors are processed, it's simple to get the style values from the rendition in the header.
I'm currently doing this after the original build, but I don't know if that's the right time to do it; the issue is that it breaks if you try to do in quick and subset (since there are now no documents that have to be resolved); this isn't great if you're trying to rebuild the reconstituted Stow in a smaller build process. I'll have to investigate that.
886 new page-images (in three different sizes) from the following volume have been added to the Colonial Despatches collection: CO 60 Vol 26 (BC 1866 Public Offices and Miscellaneous). These will now be linked into the transcription documents.
The now-fragmented Stow document needs to be reconstituted in XML form, even though we don't want or need a complete version in HTML. After JT's successful work splitting out the source files, we planned out in detail the steps necessary to reconstitute a complete XML version for the "original" set, from which the other XML versions will be generated. It ain't simple. It took two hours.
Record deletion was broken on the VPN db, and it turned out it was because it was timing out because the project_settings.php file was not being included in del_rec.php, so the time required to do the deletion was running over the default time for PHP requests. However, having fixed that, I decided that the way del_rec.php was behaving made no sense anyway; after deleting a record, it made a whole fresh request to the db for its first set of records and replaced the existing table with that. Instead, it now returns a simple OK, and the JS code instead calls a function which deletes the two table rows associated with the deleted record, leaving the rest of the stuff intact. That's much quicker and more intuitive.
A similar process was required for multi-record editing. At first I thought this was going to be really complicated, but it turned out that since all the search filter data is being sent along with the editing data as part of the query, it's sufficient just to include the regular get_search_results.php file at the required point, causing the current search query to be re-run and the modified results returned. Looks like it works perfectly; we'll see if there are any reports of errors.
July 6, 2018
1032 new page-images (in three different sizes) from the following volume have been added to the Colonial Despatches collection: CO 60 Vol 25 (BC 1866 Despatches to London July to December). These will now be linked into the transcription documents.