Mariage

Completed 12/02/2007.

We're finally close to having a working eXist 1.1.1 setup on Lettuce, which will be the long-term home of all our eXist projects. This setup is a substantial improvement on the old one, because it allows more flexible indexing (for better performance), handles large files, and has some other useful new features.

However, moving projects to the new eXist requires:

• Having a user for the project (we already have one called "mariage").
• Moving the project Cocoon/eXist files into a "webapps" subdirectory in the project user home directory (a simple task, which enable other Cocoon instances to use the same site files without having to make copies of it, and allows access through common url paths such as cocoon/collections/mariage).
• Uploading the XML files into the new eXist db.
• Rewriting the XQuery to take account of changes in eXist.

All but the last are relatively trivial. Once this move is made, the current site can continue to be maintained with new data, but all functionality updates (such as the addition of a search page) will be done in the new location.

For some reason, it was impossible to establish a reliable connection to Endive from any other Windows computer today, so markup work was disrupted. Greg is working on the problem. Meanwhile, I manually edited an IMT file to import categories from another document (which prompted a feature request for the IMT to be able to do this itself). We also discussed how to handle the multiple Sonnet de Courval texts, which are not exactly multiple witnesses of the same text, but close enough to be (possibly) marked up together, and how we might handle variants at the markup and display level.

Finished updating the XSLT code, and uploaded new versions of all the image docs to the database. Everything seems to be working OK now.

I'm just updating the document format from the old Image Markup Tool format to the new 1.4 format, and in the process, the XSLT which renders the image pages isn't functional. It should be working by the end of the day.

Claire reported that when she opened Agresseure, a copy of Correction opened. I checked the files on Endive and my backups, and determined that:

1. The files are different on my backups, so prior to January 4, the files were different.
2. The file dates on Endive show that both files were saved on January 4.

The most likely explanation is that Claire or France saved the correction.xml file over the top of the agresseure.xml file. I've solved the problem by copying my backup of agresseure.xml over the top of the file on Endive. My backup was from November 29, so any changes made to agresseure.xml after that date will have been lost, but I suspect there weren't any (unless you made some on January 4, in which case they were lost anyway when correction.xml was saved over the top, unfortunately).

The error was caused by this sequence:

<l>Et tout le reste n’est qu’un Poisson monstreux.</l>
<pb n="90"/>
Ou le Serpent cauteleux…
<l>Mais dedans on y void, qu’un Cocodril affreux,</l>

The phrase "Ou le Serpent cauteleux…" was just hanging there in the middle as text; it wasn't inside any tag. Looking at the rest of the document, I found that you've been using <p> tags for text like this, so I wrapped it in a <p> tag, and the document now validates.

However, I'm a little concerned about the structure of the markup here. There are very long sequences of <l> tags interspersed with <p> and <pb> tags. Only rarely is there an <lg> tag. There also seem to be <lg> tags embedded in other <lg> tags, in circumstances which don't look right to me. An <lg> is normally a stanza, or a verse-paragraph, or a complete poem. Around line 170-180, I see something with a paragraph containing the phrase "La Laide", followed by some lines not in a line group; then I see some page breaks with another paragraph containing "La Laide Jalouse", then an embedded line group. I don't know what the original document looks like, so I can't say for sure, but it seems to me that:

1. Phrases such as "La Laide" and "La Laide Jalouse" are actually titles of poems, or headings. If so, they're NOT paragraphs, and they should be marked up with some kind of head tag.
2. The second group of lines beginning with "Elle peut s’offrir aux autres..." is a new poem, not a line-group embedded in the previous poem. If so, the previous <lg> tag should be closed before this one is opened.
3. There are lots of instances of pages (such as 40/41) containing a single line of a poem. This doesn't make sense to me. Are these notes about the content of the poem, which is not transcribed? If so, they should be in <note> tags, not <l> tags.

These aren't major problems, but they do need to be fixed before any more markup is done. If I'm right in my assumptions above, the current markup doesn't reflect the document structure properly.

In response to Martin's post of Dec. 18, I changed the tags from "head" to "front" on Arrest_des_cornards and Varin; Sonnet_de_Courval had already been tagged as a stand-alone document (along with Allard, which I think has been removed from the website).

In the Image Markup Tool: In attempting to select "Agresseure", a second copy of "Correction" comes up.

We see all of the XML encoding in the tool when last year's transcriptions are brought up. Is this intended, or have I screwed something up?

BTW, I removed all of the spirals on the old images in favour of ellipses (and rectangles, in the case of commentary on the transcriptions).

Completed 11/01/07: IMT 1.4 should have been released, and there are small changes to the file format which will require that:

1. IMT 1.4 be installed on the project computers.
2. All image markup files be loaded and saved, to make the format conversion.
3. These new versions of files be uploaded into eXist.
4. The XSLT which renders the interactive image pages be updated to handle the changes.

Right now, the only change is from attribute name svg:id to plain id. There may be more by the time of release, though.

Included minutes putting this task together.