From: STANLEY, DOUGLAS <dmstanle@ke...> - 2011-04-04 20:36:32
We're having some trouble with our fez and fedora combo. We're one of
the NSDL pathways, and we get OAI harvested regularly. Apparently,
they'd like us to provide more metadata than we currently do.
Has anyone on the list modified fez to provide more than the simple
dublin core metadata (particularly the qualified dublin core fields) via
My one user has been trying to folow some tutorial she found online to
update the xsd's to add the additional fields, and she's running into
lots of problems. We have a really old version of fez and fedora 2.2.4
in production, but she's been doing her testing on fez from mercurial
tip and fedora 3.4.
So, has anyone specifically added the full qualified dublin core, and
could provide some pointers (or maybe documented the process). Or at the
least shed some light on what she might be doing wrong? (see her
Any help would be greatly appreciated.
We’re trying to learn how to customize XSDs through the geospatial example.
In following the instructions, there were some problems:
We tried to clone Generic Document (DC version), but it doesn’t seem to
create an exact clone. If we try to select the cloned display type
without making any changes, the record does not show most of the fields
displayed in the original. Should the clone work the same way as the
original or does it need to be modified?
Since cloning was a problem, we tried to add the geospatial datastream
to the original Generic Document. It seems to partially work. Long &
Lat fields show up on the display, but any information entered into
those fields is lost after the record is published. The original fields
associated with Generic Document are fine. We tried both using the
datastream title given in the instructions “Geospatial” as well as the
Top Element Name “geospatialCoveragesMD”, but it made no difference.
How can we cause the information entered into the new fields to be saved?