10/02/19

Permalink 10:19:31 pm, by jtakeda, 65 words, 6 views   English (CA)
Categories: Activity log; Mins. worked: 60

TEI Server workaround

I needed to regenerate the schema, but the TEI outage was causing issues. A simple fix for this was simply to switch the defaultTEIServer parameter and the defaultTEIVersion parameter in the XSLT. I've now codified this in the ANT as a set of conditions, so that, by default, we use the TEI server, but if that's down for whatever reason, then use the TEI Jenkins.

09/02/19

Permalink 09:44:58 am, by jtakeda, 118 words, 7 views   English (CA)
Categories: Activity log; Mins. worked: 400

Mtgs

Extensive mtg with MH about LEMDO; mostly just catching up and came up with a plan for various copies (for lack of a better term) in collations, and sent an email about that. Also started to work through the issue 328 on Github, but ran into some issues with the git pull stuff (which I'll figure out myself)

Then, met with JM twice, to work through encoding challenges and to resolve some issues; fixed some of the code template stuff in the process and he updated his oXygen (he was running on 16). Worked through some encoding problems and some errors, including some pretty printing problems; we really should see if we ca disable that by default in a project.

07/02/19

Permalink 11:06:41 am, by jtakeda, 52 words, 6 views   English (CA)
Categories: Activity log; Mins. worked: 120

Landscapes: Finalizing first step of build process

The FODS tables to TEI tables conversion is now working; a quick spot check seems that the results are correct, but we'll need to run some diagnostics on it both to ensure that the conversion worked correctly and to identify any oddities in the source data. Added a bunch of documentation, too.

06/02/19

Permalink 09:28:40 pm, by jtakeda, 188 words, 6 views   English (CA)
Categories: Activity log; Mins. worked: 160

Landscapes: Initial work on FODS

[Posting this blog here for now; I'll move it to the Landscapes blog once I can]

Spent some time evaluating the spreadsheets and thinking through the best process for turning them into RADish. Got a basic build set up with a conversion process. So far, the process looks like so:

  1. Copy the files into a temporary directory and, in doing so, clean up the filenames (no brackets, no spaces)
  2. Take those files and convert them to FODS using soffice (there's lots there so it takes a while)
  3. Then, take those FODS and convert them into a TEI table; I'm still working on this bit, but, so far, I have a process whereby the XSLT gets all the fods in a particular directory (using collection()) and then combines them into TEI document with multiple tables. This might not be the right approach in the long run, but I think it makes the most sense for now, particularly if the various spreadsheets in a collection need to be reconciled
Note that much of this relies on ant-contrib, which is likely fine since it won't need to be run long term.
Permalink 12:44:03 pm, by jtakeda, 73 words, 6 views   English (CA)
Categories: Activity log; Mins. worked: 180

KNDW

JM sent a bundle of files for KNDW edition--including a selection of annotated primary sources, an OS text, a modern text, and an essay--for conversion, which I've now done. It was an interesting experiment: most of these documents were in older forms of IML, which we didn't necessarily know how to handle. So I've modified the IML conversion slightly to allow for an AB element, so we can fix hierarchy issues more easily.

05/02/19

Permalink 07:43:45 pm, by jtakeda, 42 words, 6 views   English (CA)
Categories: Activity log; Mins. worked: 15

odd2lite work

Over email, discuss Stylesheet work with MH; he has created a branch and we're going to do a dive into the odd2lite stuff. This will be particularly useful for LEMDO, but will be broadly useful for any of the Endings projects

Permalink 07:42:02 pm, by jtakeda, 83 words, 7 views   English (CA)
Categories: Activity log; Mins. worked: 150

Mtg w JM

Biweekly meeting with JM and worked through a number of issues. Came up with plan for the next two weeks

  • JM's SVN access isn't working at the moment, so he's getting me to merge his Ado_M [DONE]
  • Rom_Q2M was out of date; reconvert [DONE]
  • Convert Err for editors and add linebreaks to the OS as test case for bare display
  • Start thinking about metadata display (discuss with MH and PS)
  • Add schematron to use em-dash instead of double dash [DONE]

28/01/19

Permalink 04:23:19 pm, by jtakeda, 142 words, 9 views   English (CA)
Categories: Activity log; Mins. worked: 120

Conversion and schema process

Added some new schematron for common problems that arise after conversion that have to be fixed by hand, including when there is embedded verse in prose (which could be done programatically but is safer to do by hand to confirm lineation, etc) and other common errors (unescaped angle brackets et cetera). The idea here is that if the texts pass the basic TEI conversion (which they basically all do), the converter must then check the text and ensure that they are valid against the LEMDO schema; if not, then the texts must be modified slightly by hand to fix things that require human intervention. It's a bit more involved, but it stops absent minded conversion (which I am guilty of).

Fixed a ton of small issues (mostly embedded verse, but some other small things) and converted Mac and 1H4 as per JM.

21/01/19

Permalink 06:39:45 pm, by jtakeda, 168 words, 12 views   English (CA)
Categories: Activity log; Mins. worked: 640

Mtg w JM and acting on action items

Long meeting with JM to discuss progress; discussed plans and priorities going forward. He also asked for a better display of overlapping annotations, which I agreed with; he wants everything that crosses multiple lines to be displayed as a line on the side rather than multiple types of underline. This is, of course, a rendering issue primarily, but we do need to get the algorithm in place to get the annotations and collations embedded in the HTML so that rendering decisions are easily handled later.

So, reworked the code so that if something goes over two lines, the behavior is slightly different. One way to resolve this would have been to create container divs, but decided against that since it's a lot of manipulation of the HTML; instead, we'll just add an onclick() event to the div itself and a left-border, and make sure the events don't propogate. Seems to be working alright; more work will likely need to be done, but it's mainly aesthetic at this point

17/01/19

Permalink 05:05:25 pm, by jtakeda, 241 words, 11 views   English (CA)
Categories: Activity log; Mins. worked: 480

Major rework of annotation matching code

I realized that the annotation matching code was a bit too generous with its selection of nodes, due to the preceding:: and following:: axis. I've now reworked it into something much more efficient and cleaner. The problem is that there are a number of different ways in which an editor might select a bit to annotation; the best way would be to point directly to an element (say an l or an lg), but most often editors want to gloss particular words or phrases using an anchor, so we have to handle both (and both in combination: say something starts at a line but ends halfway through another). So the solution to this is to first generate all the nodes that are between the two boundary points (using the incredibly fast << and >> selectors, which I've just learnt about) and then group them based off of ancestor nodes that were in that original selection of nodes. (That's not a very elegant way to describe it, but it's all documented heavily in the XSLT.)

This new process shored up a number of issues with the annotations. Many of them are aesthetic, some are functional, and some are processual. We'll have to have a set of diagnostics to check whether or not something that was annotated with anchors could be better annotated by pointing to a line or a line group. That won't be trivial, so that'll take some time

:: Next Page >>

LEMDO

Linked Early Modern Drama Online

Reports

XML Feeds