Permalink 02:35:23 pm, by mholmes, 190 words, 5 views   English (CA)
Categories: Activity log; Mins. worked: 180

Cleanup of old code; fixes for Standard XML rendering; more bugfixes

JT's run of our diagnostic tools package against the Standard XML static output revealed thousands of errors, most falling into a few categories, which I've been addressing today:

  • rs/@target was assumed to be pointing at ORGS1.xml, but it could equally point to PERS1 or BIBL1. Fixed.
  • The obsolete facsimile pointers to images in the old tiled map display were not pointing at anything concrete. I've bitten the bullet and removed all of those references, along with pointers to them from elsewhere in the same file, and commented out resulting empty facsimile elements.
  • File + fragment pointers were being handled wrongly, with just '.xml' appended to them. I've fixed that.
  • The @change attribute on person elements (relating to their "publication status") only makes sense in the context of the PERS1.xml file, where they point to a specific change element; I'm now removing them where person elements are copied to another file.
  • Many files had actual errors that hadn't been caught before; I've fixed a lot of those manually.

I'm now building and validating various parts of the static process before I run the diagnostics again on the results.


Permalink 04:41:58 pm, by mholmes, 102 words, 5 views   English (CA)
Categories: Activity log; Mins. worked: 120

New category and changes to build process

I wanted an easy way to list all the Stow chapters in a table, and decided on a new category, mdtPrimarySourceStowChapter, which is added to the chapter files when they're generated. To make that work in the build, I had to rewrite the XML category file generation process so that it works from the site/xml/original documents (where these generated files are) rather than the XML source in /db/data (where they're not). In the process of doing that, I cleaned up the globals module so that it has no hard-coded paths in it; they're all relative to the baseDir now.


Permalink 04:38:43 pm, by mholmes, 21 words, 5 views   English (CA)
Categories: Activity log; Mins. worked: 60

Fixes to display of document tables

Following a request at the team meeting the other day, I've added document status displays to all the category listings pages.


Permalink 03:52:52 pm, by mholmes, 46 words, 9 views   English (CA)
Categories: Activity log; Mins. worked: 90

Team meeting, changes to draft display

Following a good team meeting with lots of discussion, I've made a formal link to the viewable-draft document so that it's easier for everyone to access drafts, and also fixed a bug in the class attribute generation that was preventing the display of the draft watermark.

Permalink 10:39:35 am, by mholmes, 35 words, 52 views   English (CA)
Categories: Activity log, Announcements; Mins. worked: 10

Map of London new build goes beta

The new static build version of the Map of Early Modern London project has now transitioned from alpha to beta, meaning that we believe all key features have been implemented and we're in bug-fixing mode.

Permalink 10:36:13 am, by mholmes, 74 words, 8 views   English (CA)
Categories: Activity log; Mins. worked: 120

Working on Walsingham text, and fixes to the search in the new webapp

Got some sample transcription from KB, and did a test encoding, tweaking the XSLT and the schema too to get more worthwhile results.

Also fixed the problem with the generic search box on regular pages; it was missing some named hidden fields, so wasn't providing enough info to the search.xql file. I do need to make this a bit more robust, though; missing fields shouldn't break the results paging navigation as it does.


Permalink 03:41:18 pm, by mholmes, 29 words, 10 views   English (CA)
Categories: Activity log; Mins. worked: 120

Implemented yesterday's plan, and more

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.

Permalink 10:51:20 am, by mholmes, 132 words, 11 views   English (CA)
Categories: Activity log; Mins. worked: 60

Added interim fix for hybrid document problem

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.


Permalink 04:49:04 pm, by mholmes, 350 words, 11 views   English (CA)
Categories: Activity log; Mins. worked: 50

Planning a fix for an annoying header issue

In the static build output, all of the standalone documents which are created from AJAX fragments (people, bibls, orgs) have a particular problem in their headers: they are constructed based on the entire containing document rather than the fragment which forms the actual body of the document. This is because the same hcmc:createHtmlHeader() function is called passing in e.g. PERS1 rather than the target person entry. I've been trying to figure out how best to remedy this, and I think the best approach would be this:

The hcmc:createHtmlHeader() function, along with the hcmc:getDcMetadata() function it calls, should have an additional optional parameter which is the component item which is actually the focus of the page. Where this is not passed in (the default situation), the same processing would be applied, but where it is, the document title and resulting metadata should be constructed based on it. Some of that data will still have to be derived from the parent document, but (for instance) the list of places and people referenced (the former already implemented, the latter still not generated in the DC metadata) should be drawn only from the links appearing in the target fragment.

Steps to proceed:

  • Add the parameter to the two functions.
  • Fix any calls to those functions such that they pass the empty sequence or the relevant fragment.
  • Test the build process to make sure nothing is broken, including search (which depends on header metadata).
  • Add conditional branching to handle the different cases where a full document versus a fragment is being dealt with, for the current output. This includes ensuring that the document title is correct -- so instead of "Complete Personography" for every person page, it should be "Complete Personography: Fred Bloggs". (Not yet sure what should happen for bibliography entries, where there's no natural "title" other than the document title; perhaps the first title element in the bibl should be used.)
  • Add (to both cases) processing of the person data (listing persons mentioned in dcterms.appropriatething, presumably dcterms.subject).
  • Check that the outcome is appropriate for all fragment pages.
Permalink 04:09:42 pm, by mholmes, 88 words, 9 views   English (CA)
Categories: Activity log; Mins. worked: 30

Reorganizing some graphics

I noticed that some procession maps were stored in the site/images folder rather than in data/graphics (which actually meant that they failed to appear on the static site), I've moved them, and fixed references to them in the documents. As a general principle, images which form part of the site structure and design (thus appearing on lots of pages) should be in site/images, while images which are linked in specific documents appearing on the site should be in data/graphics, where editors can manage them.

:: Next Page >>

Map Of London

This project allows literary and scholarly works (primary and secondary) to be associated with locations in London, providing the reader with a richer understanding of the works.


March 2017
Sun Mon Tue Wed Thu Fri Sat
 << <   > >>
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31

XML Feeds