The EMLS project now has its own account, which includes Greg and myself in its group; Karin will be added later so that we can all log on as ourselves and edit materials in the emls account (no-one should need to log on as emls). I've posted the site materials there, and everything created so far appears to be working (except for the links to full issue display, which are not finished). The new, hopefully permanent, URL for the project is:
Here is a draft of the EMLS project charter, based on Martin's estimates.
This is the current status of EMLS:
Before we can set up the eXist db for EMLS, we need the 1.1.x release of a build of Cocoon with eXist built as a block. Wolfgang has promised that it will be released any minute now.
Meanwhile, the P4 format of the existing EMLS files has become obsolete; they should really be converted to P5 before we go forward with a site. I've been working on XSLT to convert the ScanCan code to P5 this week, and that is now working; I'm going to move next to the ACH abstracts, elaborating the XSLT as I go, and finally I'll deploy the same code against EMLS so that we can at least start the project with good P5 XML. That should be done (I hope) around the same time that the new eXist version is running on Lettuce, at which time we'll be able to start work properly.
If you'd rather leave the code as P4 and work with that, then let me know and I'll start writing stylesheets for the Web interface. I don't really mind either way. I think P5 has more long-term stability, but it will take a little longer to do the conversion (an additional ten hours or so, conservatively).
To build the entire Web interface, I would estimate something like:
1. Setting up the DB: 4 hours.
2. Index/TOC page: 4 hours.
3. AJAX search page: 8 hours.
4. Article display (XQuery/XSLT/XHTML): 20 hours.
5. Site styling/CSS: 20+ hours (depends largely on what Ray wants -- apparently simple requests for particular display features can eat up days with CSS).
6. Peripheral pages (About, Contact, etc.): 5 hours (assuming content is readily available).
7. Debugging, cross-browser testing, fixing and tweaking: 10 hours (very roughly).
8. PDF output (if required): 20 hours.
That's a total of just over 100 hours, give or take.