ALEG

What I've done

• I was away for two and a half days this week, so I didn't start on the data maintenance UI proper

• However, as part of developing the interface between the database and the data maintenance UI, I further developed the initial XML representation of the objects in ALEG, which pretty much follows the FRBR/INDECS/Harmony ABC philosophies. To make sure these representations were "practical" to use, I greatly extended the stylesheet to format the XML into an HTML representation and linked all this up to the prototype search infrastructure.

  To get an idea of what the XML model looks like, here are some examples:

  NOTE! If you click on the XML links below, the XML will only be shown in your browser if you are using Internet Explorer 5 or 5.5. Otherwise, you'll have to download the files and view them with something like "notepad", or an XML viewer if you have one. The HTML versions require a browser which displays cascading style sheets. I really want to stress than the HTML output formatting is NOT intended as final, or even proposed - it is just a very simple format which shows me what is being retrieved!

  1. Simplest case - The Outcasts of Foolgarah - monograph work with one recorded expression and manifestation.
     • As XML
     • As HTML

  2. In the Via de Calzaioli - a poem by Antigone Kefala with 3 manifestations as parts of other work/expression/manifestations.
     • As XML
     • As HTML

  3. European Notebook - selected works by Antigone Kefala with 3 manifestations as parts of other work/expression/manifestations.
     • As XML
     • As HTML

  The European Notebook shows 2 manifestations, because one of the poems, Farewell Party : III : Eumenides is recorded in Austlit (probably erroneously) as being in an edition published by A&R.

• Drafted a proposed interface between the ALEG server and the holdings retrieval component which will be implemented by ABN. I've just finished the draft, and Judith Pearce from NLA should find it in her email inbox on Monday morning!

• Actually start writing the data maintenance UI!

• Document how ALEG will handle some tricky cases - The "Poets of the Month" works from the mid 1970's and "Down the Lake with Half a Chook". These are amongst the most "difficult" cases Tessa and Kathy can come up with, so if we think the proposed data model can handle these, we'll be happy!

• Tidy up some complicated cases in the XML representation, especially related to periodical issues.

• Start on the data maintenance (input) suite.

• I'm aware that there isn't time before the Partner's meeting and that it is very important to have some prototype data maintenance screens to discuss for that meeting - hopefully I'll make a start on these this week!