HCMC Blogs

With RE's help, got four new exists deployed, with their apps working, and publicly available. Lesson learned:

• For configuration and deployment of the XAR, use Chrome, and connect to the internal :8080 address. If you connect through Apache, you risk a timeout during deployment, which will bork eXist completely.

Other than one case of that happening with the MoEML app, everything worked as planned; the deployment script goes seamlessly, the XARs all worked, and everything looks good. Couple of bugs to fix in MoEML and Mariage.

Late duty.

Divided up the workload with SA, and continued work on my bit. I've done the first presentation.

I've extracted the editorial content from the master volumes, and I'm now building a separate index page for each of the volumes we've created, including the editorial stuff. On the other listings pages, volume numbers are now links to the volume pages. This answers (I think) the last of HT's requirements for the new site, other than a redesign.

I've also tested Apache Tika with the old volume PDFs, and the results are very promising; I think we may be able to process them to ugly XHTML, which eXist could then index, and provide people with search capabilities and linking out to the specific page in which the hit is found.

Debugging a form got a bit easier with the FormData() method in javascript.

Insert function like:

function inspectFormData(formId){
	var formElement = document.getElementById(formId);
	var formData = new FormData(formElement);
	console.log('FIELDNAME: Value');
	for (var pair of formData.entries()) {
		console.log(pair[0]+ ': ' + pair[1]);
	}
}

And it’ll deliver this:

FIELDNAME: Value
METHENL: E
SURNAME: Adams
FORENAME: Charles Frederick
ADDRESS: 
MILSERACT: 
POB: Toronto, Ontario
NONOK: 
AONOK: 
RONOK: 
OCC[]: 
HISCO[]: 
DUGUID[]: UN
MARRIED: N

Our popup date information in the static build points to an explanatory page which is supposed to be at mol:dates, but no such file was there. I've created a basic stub with a couple of links, not yet published, but it will do the job for the moment.

Received email from DD (UVRA) advising of new information for events.
Updated test site with new information; created pdf of registration page information; filed pdf in cascade assets; republished page.
Sent email to DD,MK,PL (UVRA) advising test site updated.

Leaving a little early.

We've hit a problem with the normal situation where we're running eXist listening on a different domain from localhost. To summarize:

If eXist is running on the default localhost:8080, I can use startup.sh and shutdown.sh to start and stop it.

If it's listening instead on another ip name, I can still start it with startup.sh, but I can't stop it with shutdown.sh or with start.jar directly. I get:

ERROR: Failed to create input stream: Unexpected end of file from server
CAUSE: Failed to create input stream: Unexpected end of file from server

Disowning the process in the terminal where it was started makes no difference. Supplying credentials also makes no difference. Waiting to see if anyone on the eXist list has any ideas.

The new translation is done, thanks to numerous hacky shortcuts to converting ODT to TEI, including search-and-replace on the contents.xml file. The results highlighted a couple of minor layout annoyances, so I've also fixed those. The document comes in at about 100 pages. It's now posted for proofing.