EMLS

The EMLS search capability doesn't work in Safari -- there's no response at all. I also noticed that the logo is overlapping the text in IE7, but I'll try to fix that. Logo position is now fixed.

1. Remove the View column, in favour of...
2. The title of the article should click through to the XHTML version.
3. Give the XML and Text links a class, so they can be styled small and icon-like.
4. The Vol/Issue column can simply read Issue.

Basically completed, with some caveats explained here:

Add the extra processing to article.xq and p5_to_xhtml.xsl as described in this post.

Found and fixed. Whenever I click on a link to a plain text version of an article I get the following error in cocoon.log:

WARN (2007-01-17) 09:44.33:413 [sitemap.serializer.text] (/cocoon/%7egregster/article.txt?id=EMLS1-1CARLSKEL) http-8080-2/TextSerializer: Encountered text before root element. Creating <text> wrapper element.

This task abandoned: Ray doesn't believe it to be worth the time it will take.

If Scott approves the hours, build a PDF rendering system using XSL:FO and XEP for articles, and possibly also for the volumes, as requested by Ray.

Before we can get started on this, here are some details we'll need the following info from Ray:

• Page size
• Margins
• Columns (2 columns is more common in journals, but there are problems with displaying images spanning columns).
• Page numbering. Consider these issues:
  • The original Web page versions had no page numbering, naturally, but print documents do.
  • If page numbering is not supplied, Acrobat will supply it anyway, and people will cite using Acrobat's page numbers.
  • Both individual articles and issues will need page numbering; if they don't match, there will be confusion (e.g. if an article is numbered from page 1 when viewed alone, but starts on page 50 in the issue, there will be two competing numbering systems).
• How to include/display metadata. PDFs are typically printed, so data visible in XML (or even XHTML) renderings may be lost; it should be included in a standard way, so we need to know what to include for issues and articles, and also how to display it.

If Ray can post his ideas on these issues as a comment to this post, I'll have enough to get started. I estimated about twenty hours for the PDF; Scott should approve that in advance, because it wasn't part of the original discussions.

This task abandoned -- no longer necessary because main TOC allows sorting by volume.

Create a rendering for each individual volume (= XML file) which will include all the peripheral content, but not the main articles (these would be links to the article rendering).

After one bug report on Safari (fixed), nothing further from ETCL, so I'll put this one to bed.

General hammering and usability testing. Main input should be from ECTL folks.

Marking this as completed: no outstanding requests as of Jan 29 for more pages.

Marking this as Completed as of Jan 29. The core work is done, although Ray will probably have other requests and requirements over the next couple of months.

This is really a collaboration task: work with Karin to ensure that her CSS is working well, and if necessary tweak the XHTML output created so far to enable her to better style the pages.

Basically completed as of Jan 29: Create XHTML output for articles, accessed through links in index/TOC and search results.

CSS is to be provided by Karin -- link in a default CSS file which is on one of her servers, so she can hack at it easily.