EML

Please clarify how this relates to bug #338, which is intended to provide
specific documentation for each eml field. Is this going to be a tutorial that
utilizes the field definitions? Also, how does it relate to the morpho tutorial
(bug #296)? Thanks.

This is closely related to the work that Eric is doing for the seminars. It is not intended to be an
complete documentation of EML, nor a specific Morpho tutorial, but rather a practical bridge
between the two. I invision taking portions of the McLaughlin journal article "Native and Alien
Species..." that Eric and Cristy are using an example metadata for the seminar as well as using
some of the Sevilleta datasets (metadata & data combined in a sngle document) to show how one takes
metadata from a "familiar" source to enter it into Morpho. Feedback that I have received tells me
that both students & LTER ecologists would benefit from a practical guide to bridge conventional
reporting mechanisms to the more structured EML format.

Contributed partial version of documentation set to CVS for review.

Now that EML 2 is close to release, I can continue with this project. Since i
will be working one-on-one with LTER information managers over the next few
months I will be revisiting the documentation this week. I plan to rework my
"Taxonomy of EML" in light of the changes from beta8.

My work with LTER information managers will give me a better idea of the
appropriate level to aim the documentation.

We agreed during the conference call that this would best be a "Primer" sort of
document that systematically builds up an eml dataset document, explaining why
each section is needed as one proceeds. First you might start with just a
dataset with a id/title/creator, explain it, and then add in an entity with its
attributes, and explain it (showing the new parts of the XML in a highlighted
color like red), and then keep adding modules (coverage, project, protocol,
methods, etc), explaining each addition as we proceed. Ideally this would be
distributed with the EML 2.0.0 release, but if that schedule can't be met, then
we could just link it into the EML web site when it is ready. Chris suggested
that maybe the eml should be represented as a tree diagram of blocks rather than
as XML for understandability for end users, but there's probably a need for both.

Continuing to make progress but may not be ready for 2.0 rollout. I have been
putting more effort into developing the scripts for converting site metadata.

EML Primer is postponed until December 1 in order to be ready For the next Morpho release and for the Spring KNB seminars

Making progress. I plan to have a draft for review avaiable on Monday, Dec 16.

Progress has been much slower than I anticipated. I am hoping the the balance
goes faster.

I am producing this in Adobe InDesign which allows me to export in xml. I have
been using a subset of docbook tags. Once I get further along I will write a
stylesheet to display the document in html form

Basically includes introduction and detailed coverage of creator elements

This is an xml document using the docbook.xsd elements. Once I get further I
will include an xslt for this.

This is a microsoft word document. It should be reviewed for content, not
format/design.

Changing QA contact to the list for all current EML bugs so that people can
track what is happening.

Original Bugzilla ID was 365