Hi Scott,
in our journal digitization projects we have two different kind of METS
records:
- one METS record for the journal just containing a single <div> in the
<structMap> and an appropriate MODS record in the dmdSec for the journal
- a METS record for each volume. These METS records include all the
content files for a volume, all nested <div> elements for issues,
articles and chapter within the volume and appropriate MODS metadata in
separated dmdSecs for each of those <div> elements.
The journal level and volume level are linked by the MODS <relatedItem>
element, which I found more appropriate as you could qualify the link a
bit better than using a <mptr> element. We are just linking upwards from
the volume to the journal level. There aren't any links from the journal
to the volumes as this is regarded as an operational feature of the
Document Management System we are using.
All other structures (within a volume) are not reflected in MODS; we use
nested <div> elements for these.
I guess, this is a reasonable approach to avoid redunandancy of metadata
and structural data (which is problematic for updates, corrections) and
still have a limited amount of METS files (that's why we avoid having
separate files for single issues). Our METS files for a single volume
are usually about 1 -2 MB large (without any technical ,digital
provenance metadata and content files) and did not find any problems to
deal with these files.
You can find a description of our METS usage on our new website (going
to be officially relauned in the next days) at
<http://dz1.gdz-cms.de/index.php?id=42&L=0>.
Ciao
Markus
Scott Yeadon wrote:
Hi,
I have a question on marking up a journal issue or an entire journal in
METS. If for example I was using MODS for descriptive metadata to describe
the journal is it more correct to have the entire journal's MODS metadata
within a single dmdSec (i.e. covering all discrete objects which make up
the
journal), or to have dmdSec containers for each of the discrete objects
(e.g. the journal, issues, sections, articles, etc).
In the situation where a single dmdSec held all MODS, the structure
reflected in the structMap would be (redundantly) replicated within the
MODS
metadata (using the part and relatedItem MODS elements). It would also mean
DMDIDs from within the structMap and fileSec sub-elements would be
linked to
IDs within the MODS metadata which seems not be very package-oriented
(surely better to link to package-level elements rather than payload
elements?).
The description of the dmdSec element within the METS docs appears to
support both ways (which makes sense given the docs aren't content
sensitive), so I just thought I'd get the opinions of some experts before
progressing. Thanks!
Scott.
|