HCMC Blogs

For Endings and workstudy.

Entered HT's proofing corrections for a couple of reviews.

All the usual suspects have posting privileges.

Advised Monk's of HCMC's new address. Now in their system.
Placed order with them today for office supplies.
Received confirmation order received and being processed.

... for Kott review now done, review is published.

Still on the quest of the best way to build a working eXist and update it cleanly, we've been testing the dist-zip build target. First, though, I determined how to build with DS's patch for the bug I reported the other day, which is still only a pull request (#1256); CLI for future reference:

git pull
git checkout 1256
git fetch origin pull/1256/head:1256
git checkout 1256

Then we do:

./build.sh clean
./build.sh 
./build.sh jnlp-all

the last of which signs the jars, enabling the Java client to work. This gives us a working build in the repo context, but of course it's cluttered up with lots of unwanted stuff, including source. That's why we wanted to use the dist-zip target, but the result is currently broken due to an obscure timestamping issue which I reported today on the gmane list. We could manually create a clean tree, of course, but it would be easier to have a script do it.

Went through the steps planned yesterday, and also added DC metadata for all the people and orgs mentioned in all documents; I think the headers are now looking good.

In section 15.3 Pausanius refers to "the hero, Marathon". I can find no evidence of this person, not sure where else to look.
In section 15.4 Pausanius refers to the "Scioneans". I can find them referenced in other literature, but no explanation for who they are.

Places that still need fixing:
-Sphacteria
-Palestine
-Macedonia

Have finished events for 14, edited up to 16.1. Events need to be created for 15 next day.

Hours: 9:30-3 (5.5)

I've been concerned for a while that, although I do generate both P5 and PDF versions of all articles and reviews and store them in svn as a matter of course, I'm not able to do that for XHTML versions; and in addition, the structure of the ancient site, based as it is on query strings containing ids, is not friendly to archiving tools. I've now started creating a static XHTML build process which will hopefully result in archivable versions of the web pages and a better URL structure (which should presumably be integrated into the old webapp in the medium term, so that archiver URLs are rewritten). Ultimately, we want to have a rich static archive we can pass on to any future editor at another institution.

We have an issue with a small category of documents, typified by QMPS1. These docs purport to be mdtPrimarySource, and indeed they contain transcribed primary source selections, but that content is interspersed with born-digital commentary and no attempt is made to describe the bibliographic features of the original source. When rendered in the static build as mdtPrimarySource, they end up unstyled. I've hacked around this by insisting that a true primary source document (for rendering purposes) must include at least one rendition element in the header (other than those auto-generated from @style attributes during the build process); failing this, the document is treated as born-digital. In the long run, we should find a principled solution to this issue, and JT is drafting a description of the problem for the next MoEML meeting.