Endings

Fairly major overhaul of the original code, to do this:

• Handle all attributes, rather than trying to figure out which might be pointers.
• Determine instead whether a token value in the attribute is some kind of pointer.
• Resolve prefixDef/private URI schemes.
• Handle paths on Windows. This took some wrestling.
• Calculate the date in the ant script instead of getting it from Oxygen.
• Format the output much more effectively.
• Add tests for simple cases.

Lots more to do, of course, but this is coming along nicely.

JT started the diagnostics repo for projectEndings on GitHub, and did all the initial work to get something that will process a folder full of XML and check internal links. I tested and raised a few issue tickets, then set about solving some of them. We now have a process that will check three kinds of link: internal links within the same document (on the assumption that RelaxNG does not do this unless DTD Compatibility is turned on); links to external documents; and links to specific ids inside external documents. I think this is a good initial selection, and when run against Mariage, it does indeed find some bugs that need fixing, which I will fix. There's a lot to do in terms of making it prettier and more user-friendly, but the basics are definitely there.

All seems to be working well after some refactoring to work around an eXist bug.

The eXist search had somehow got broken due to a misplaced bracket in doc.xql. Fixed, and the site updated.

First meeting of the new year; reports, intro to J and the new blog, review of abstracts submitted, etc.

CC and EGW came by and we had some planning discussions about the metadata and intro page for Graves, the Special Collections pages, the Mariage deployment and much other Endings stuff.

I've previously tested the Solr docker container, which is probably the way I'll do most of my testing, but today I was on a machine in the RA room because my desktop is dismantled, so I worked with a download. Tested indexing Graves web content with the default settings; tested with Nutch, which is a web crawler that can pull content into Solr. Because of http://jenkins.hcmc.uvic.ca/robots.txt, though, Nutch can't do its thing; easy enough to change the robots file, but possibly a bit risky, so if we're indexing we should do it from another static version of the site. I would like to investigate the possibility of doing site indexing automatically in our own tame Solr, then exporting the index for ingestion into the Library's instance, so that we can tune and tweak as much as we like; not sure yet how practical that will be.

PS reported a bug that shows up with a trunk build of eXist from September; we're working on narrowing it down, but in the process I did some robustifying for request parameter retrieval and made a new release. More to do here, unless what he's found is a bug in a specific build of eXist.

Expanded the build script and wrote some bits and pieces to create a XAR; tested integration with Graves, and it works well. This will be a convenient way to add CodeSharing to all our eXist-based projects.

Legacy URLs are now fully handled in the eXist application.