Eml documentation for Seminars & LTER sites
This will be an overview of EML and its relationship to Morpho. It will also be practical guide for
users to understand how to take conventionally reported metadata, such as text documents or
other legacy systems, and manually enter it into Morpho. (This is not to be confused with
automated conversions of metadata into EML).
#2 Updated by David Blankman about 17 years ago
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.
#4 Updated by David Blankman over 16 years ago
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.
#5 Updated by Matt Jones about 16 years ago
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.