Map Of London

At TL's request, added the <tag> element to the schema and implemented rendering for its various types. Also fixed rendering of some self-closing tags in example code.

Got an EPS file from RW at TCP and was able to edit it easily in Inkscape.

Using my new automated ODD build process I've built a new value into the schema for Parishes. Had to tweak the build process a bit, since I had the wrong @mode value on a couple of attributes.

I've implemented the variant spelling functionality. If you click on a variant spelling (either in the gazetteer or in the "List variant names and spellings" bit at the top of a location document), you'll see a popup with a list of documents which use that spelling. You can then click on the link to one of those documents to see it with only that spelling variant highlighted. That should help with proofing quite a lot.

One drawback is that the vast majority of spelling variants show up only in Stow, which is not published. Initially, I was hiding links to documents which are not published, but that meant that the majority of variant spellings seemed to be attested nowhere, so I've compromised by linking to them, but when you click you'll see the usual message for a document that's not published. Project members will be able to see those documents if the need to, of course.

I don't yet have a clear idea how we're going to handle the issue of large documents which can't be displayed all at once (like Stow); I think the best bet would be to divert the link to a pre-configured search which shows all the instances of that spelling for that name, each as a link to the particular page that it's on.

This was quite messy to implement; I think the JavaScript has grown to a point where it could do with some refactoring, since there are many functions doing quite similar things, and a lot of the XQuery would benefit from much better inline comments, as would general.xsl.

This task arising out of our meeting last week is now complete:

Set up location processing so that:

• any location div is always processed to add a map
• "List documents mentioning this place" is changed to "List documents mentioning [doc title]" so that it can be shown for all documents.
• the variant spellings link only appears for mdtEncyclopediaLocation documents.

REVE2 (a topic) is one working example for this. Developed and tested on dev, and ported directly to live.

All orgs, bibls and people now have individual pages, so they have full URLs they can point to; this also makes Credits work properly for non-JavaScript browsers. Org display has been enhanced to handle lists of people as in ppp classes.

Also fixed some bugs I'd noticed in the XML generation, particularly in terms of linking from names to orgs, and linking @datingMethod and @calendar in the standalone XML. More testing to do here, I think.

Inclusion of a remote image was slowing down page load, causing onload JS to be sluggish. I've now substituted a local copy of the image.

... as requested, in dev; once I've duplicated the functionality for org, I'll port this to live.

Meeting this afternoon, giving rise to these tasks:

• Consider making @resp global and using it to point to <respStmt>s, as an example for the @resp working group.
• DONE 2014-08-08: Make <bibl> entries able to render as discrete pages, linked from the header of their popup, as with people in the personography; and do the same thing with <org>s.
• Implement and document a protocol for linking to DEEP through <ref target="moldeep:xxx">. This depends on DEEP implementing individual pages for entries, which hasn't been done yet.
• DONE: Make <h4> through <h6> the same size in born-digital documents.
• DONE: Check list of elements rendered in <egXML>s as self-closing and add any we use that are missing (I added <catRef> and <link>).
• DONE: Add a grey-scale TEI badge to the page footer.
• DONE 2014-08-15: Check on JT's submission to have MoEML included on the TEI projects page -- did this go to anyone who is going to act on it, or should I just do it myself?
• DONE: Implement <table>/<head> as caption for table, rendered below it, in born-digital documents.
• DONE 2014-08-13: Set up location processing so that:
  • any location div is always processed to add a map
  • "List documents mentioning this place" is changed to "List documents mentioning [doc title]" so that it can be shown for all documents.
  • Fix it so that the variant spellings link only appears for mdtEncyclopediaLocation documents.
  REVE2 (a topic) is the working example for this.
• DONE 2014-08-13: Add a location type for parishes.
• DONE 2014-08-13: In the gazetteer page, make each variant spelling a link which pops up a list of the documents which contain that spelling.

We're experimenting with a JSON version of the gazetteer, and the biggest problem has been getting eXist to serialize it with the right character encoding in the header. After a lot of different approaches were tried, this is what worked in the end (snippet from controller.xql):

else if (text:matches-regex($exist:path, '/*\.json')) then
    <dispatch xmlns="http://exist.sourceforge.net/NS/exist">
    	<forward absolute="yes" url="/rest/db/generated/{substring-before($exist:resource, '.json')}.json">
    	 <set-header name="Content-Type" value="application/json; charset=utf-8"/>
    	</forward>
    </dispatch>

This is bound to crop up again, so I'm blogging it.