Booting up this morning, Lab B 19 went into CheckDisk. It eventually completed the bootup successfully, but this may be a sign of a dying HD. Station 21 booted up at 800 x 600, and when I logged in to change it to 1024 x 768, it seemed to lose all communication with the monitor for a couple of minutes before coming back with a wobbly picture, then settling down. Watch this one in case the monitor is on the way out.
In a May posting to her blog, Digital Scholarship in the Humanities, Lisa Spiro addresses one of the most obvious questions to strike anyone who's interested in learning more about digital technology and texts. Why the fuss about machine-readable texts? Isn't it enough to circulate high-quality human-readable reproductions of texts, and make them more available to scholars? What can you do with machine-readable text (think XML, mark-up etc.) that can't be done with human-readable text?
I’ve had a longstanding, friendly debate with a colleague about whether it is sufficient to provide page images of books, or whether text should be converted to a machine- and human-readable format such as XML. She argues that converting scanned books to text is expensive and that the primary goal should be to provide access to more material. True, but converting books into a textual format makes them much more accessible, allowing users to search, manipulate, organize, and analyze them. Here’s my summary of what you can do with an electronic text. Most of these advantages are pretty obvious, but worth articulating.
Read Lisa Spiro's full post, "What can you do with texts that are in a digital format"
Had a medical appointment first thing in the morning.
Back after a month away, with a pile of email to work through and file, and some other bits and pieces (distributing a couple of payroll advices; figuring out SM's timesheet for the Lansdowne Video work; and so on).
JS-R has contracted his friend to make some changes to the CityStats code, to add a new option for users. Fixed a couple of validation problems (missing close tags on two of the tables on selecttTracts.php, then sent the code off to the programmer. Then I found another problem on details.php (evil word-processor apostrophes), which I fixed on our site.
While I was away, JC reported a bug with the file format -- @facs references should be preceded by a hash, of course. Easy to fix, but I'll integrate the fix into the next release, when I add discrimination between transcriptional (@facs) and non-transcriptional (@corresp) associations between annotations and zones.
I tried to build the PDF of volume 17, including some newly-marked-up documents, for a while without success. I kept getting the error message "The system cannot find the file specified." It turned out that the xep.bat file in the RenderX\XEP folder, which is called by oXygen to transform the FO to PDF, had the path to an old 1.5 JRE which I'd deleted. I replaced it with a working 1.6 JRE path, and everything seemed to work fine. Reported the new volume size (112 pages) to John.
There are quite a lot of obvious problems with the newly-marked-up volume 17 files. We'll have to proof carefully.
After fixing the first bug, the contents page title was not being correctly selected; it defaulted to "Reviews". The logic of the XSLT was correct, but perhaps due to some Cocoon cacheing or some other oddity, it wasn't producing the correct result, so I added an "any" value in the XML, and trapped for that explicitly, working around the issue.
Sorting code in the proofing page was mirrored from the articles and reviews pages, but because it combines both, it didn't quite work correctly; when you clicked on a header to sort the list, it defaulted to showing only articles. This is now fixed.
Back from vacation, and here's what I've used:
- Absent July 14 through August 8.
- 20 weekdays, - 1 stat (August 4) = 19 days to account for.
- 49 - 19 = 30 vacation days remaining.