I have taken a look (not detailed) at this. Most of the core elements fit
in pretty well, except that we need to define a "type" attribute for
coordinates (to say east bounding, west bounding, etc.) and for scale.
This should not be too difficult (we may need some help with determining
what the type values should be for scale or for now may have an
uncontrolled list while we research it a bit more). There are a few core
elements that we need to look at in more detail where you've used elements
that don't exist in MODS. There are many places where you've used note
with a type, which is fine, since it is an open-ended list. However, for
those highly specific to FGDC elements, I would suggest that we use the
extension element, specify the FGDC XML schema (we'll have to investigate
this further; looks like they have a DTD and not a schema), and include
the data there.
On Wed, 23 Apr 2003, Elaine L. Westbrooks wrote:
> Hopefully the collective wisdom of the list can enlighten me. We are in
> the process of making FGDC metadata accessible in "less complicated"
> metadata schemas for our GIS Repository. I have created a FGDC to MODS
> crosswalk at the following
> address: http://metadata-wg.mannlib.cornell.edu/elaine/fgdc/. I would
> appreciate any comments regarding the mappings. It is quite long, but you
> can concentrate on what I consider core, which are in bold print. Any
> comments or suggestions can be sent to me directly. Many Thanks!
> Elaine L. Westbrooks
> Metadata Librarian
> Albert R. Mann Library
> Cornell University
> Ithaca, NY 14853-6401
> [log in to unmask]