14/05/18

Permalink 11:02:27 pm, by jtakeda, 206 words, 19 views   English (CA)
Categories: Activity log; Mins. worked: 300

Fixes to sources appendix and more sourceDoc stuff

  1. Spent the beginning of the day cleaning up some tickets from Asana and answer email. JJ noticed that the Works Cited at the bottom of the documents was pulling in too much stuff. That took some investigating, but it turns out the bibliography was getting pulled in from any ref/@type='bibl' citation indiscriminately across the TEI document. JJ decided that we should just be getting the bibls referenced in the text; these bibls already appear in the listBibl in the sourceDesc, so it makes sense to use that to make our appendix. That's fixed now
  2. Spent the other half of the day working on the text to sourceDoc transformation. There are a number of little bugs that appear; whenever I think I've got it finished, a different pageant becomes invalid. I've realized that I need to rewrite the whole thing and incorporate what I've learned about these documents and the shifting hierarchies. It will go faster now that I have a better plan going forward and I think this will be a tenable way to move forward in the sourceDoc encoding of our texts; we might even want to adapt this for LEMDO to create actual folio transcriptions (or some base transcription) for these texts.

13/05/18

Permalink 08:38:45 pm, by jtakeda, 60 words, 14 views   English (CA)
Categories: Activity log; Mins. worked: 240

Text to sourceDoc

More work on the text to sourceDoc transformation. Tested across all of the published mayoral pageants and spent a good amount of time re-working the pb/fw extraction code, which is convoluted but I think is now working well. There are also some issue with hi elements and line elements to do with styling, but those should be resolvable soon.

11/05/18

Permalink 09:39:22 pm, by jtakeda, 94 words, 17 views   English (CA)
Categories: Activity log; Mins. worked: 480

A potential conversion from text to sourceDoc

Spent today experimenting on a text to sourceDoc transformation for the new Mayoral pageant protocol. I wanted to see if it was feasible to take a mayoral text that is encoded in MoEML's current standards and transform it into a sourceDoc version. It's a tricky thing, since the hierarchies are radically different. That said, I think I have it working; the hardest, and most time consuming part, was getting it so it would break the a paragraph/div at a pb element. Tested on MONU1 and CHRU1--works okay, but still more to do.

Permalink 03:47:22 pm, by mholmes, 104 words, 12 views   English (CA)
Categories: Activity log; Mins. worked: 360

In-page OL maps now basically working, but more to do

Today I replaced the Google Map with an OpenLayers map in the site pages. The map is based on KML rather than JSON, because that's what we have, but ultimately I'll probably switch it to JSON. It also needs functionality for showing the popup info about sources, and the OL KML parser currently fails to pick up the rose icon for points, but we'll get there on that one. I'm now a little less worried about being overtaken by the Google problem, but I'll need at least another couple of days to get everything properly shaken down to the point where we can publish.

10/05/18

Permalink 04:33:33 pm, by mholmes, 133 words, 11 views   English (CA)
Categories: Activity log; Mins. worked: 360

Agas Map now working with current OL; plans for replacing Google

I now have a fully working Agas Map based on Open Layers. There's more that could be done, and I will revisit the pan/zoom functionality later, but the next job is the urgent replacement of the Google Maps feature with OSM. I've successfully tested an implementation of an OL map using the KML that we're currently generating, and I think that will be the way to approach it. It'll take some work. At present, the Icon style setting doesn't appear to be supported, although it is being retrieved. I think we'll need to override the styles from the KML, which will actually be nice because OL gives us more flexibility there. The other thing not yet working is the annotation popups, and that may have to be done in a different way.

Permalink 04:21:45 pm, by jtakeda, 87 words, 12 views   English (CA)
Categories: Activity log; Mins. worked: 450

Regnal calendar now in db/data/

Further to my last post, I have now moved the regnal calendar out of the spreadsheet and into a TEI document; I just took the latest one built in the Jenkins build and went from there. It's should now be rendering properly on the Jenkins site; I had to change the structure of the document slightly, which caused a chain-reaction of errors throughout the static build, mostly to do with add events to the standalone header and with rendering the date popup. These should now be resolved.

09/05/18

Permalink 06:52:41 pm, by jtakeda, 36 words, 13 views   English (CA)
Categories: Activity log; Mins. worked: 60

Fixing bug in regnal calendar processing

The regnal calendar spreadsheet was modified so that it had an unexpected column on the left; this broke the regnal calendar processing, which relies heavily on the placement and order of the table rows and columns.

Permalink 04:06:07 pm, by mholmes, 115 words, 14 views   English (CA)
Categories: Activity log; Mins. worked: 240

Beginning work on porting the map code to OL 4.5

We need to update the Agas Map code so we can use the latest OpenLayers for GIS maps as well. It turns out that the changes in OL since the original code was written have been significant, so I made a start on this today. I have the basic functionality working (although I still haven't managed to successfully reproduce the pan/zoom functionality -- needs more work), but more important is the drawing code, which is only partly working; drawing itself works, but no feature is available at the end of the process, so the TEI output is not being created in the text box. We can't switch to this version till I've fixed this.

Permalink 04:03:04 pm, by mholmes, 27 words, 9 views   English (CA)
Categories: Activity log; Mins. worked: 20

Fix for controller

The controller didn't have anything set up to show the XSLT files which we provide as part of the documentation. JT reported it, and I fixed it.

08/05/18

Permalink 01:52:51 pm, by mholmes, 48 words, 9 views   English (CA)
Categories: Activity log; Mins. worked: 60

Fix for XSLT bug

Tiny bug in the TEI Simple XSLT broke the build: LS used the @resp attribute on <soCalled>, which is a nice idea and makes perfect sense, but which the simple code wasn't expecting. Took a while to narrow it down, but it was an easy fix.

:: 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.

Reports

XML Feeds