On Aug 30, 2004, at 10:57 PM, Evan Owens wrote:
> In the METS schema documentation I found this comment about GROUPID:
> "Two metadata sections with the same GROUPID value are to be considered
> part of the same group. This facility might be used, for example, to
> group changed versions of the same metadata if previous versions are
> maintained in a file for tracking purposes"
I will admit the documentation here is not the clearest. The notion
all of the various uses of GROUPID in different areas of metadata is to
you to indicate that different dmdSecs (or files or behaviors) are part
of a set. Different dmdSecs that have the same GROUPID attribute are
of the same set. With respect to versioning, the idea was that if you
have *multiple* dmdSec elements that apply to one version, they would
all have the same GROUPID. Different dmdSecs for a revised version
a different GROUPID.
> I was trying to take advantage of this by having two dmdSec to
> the original and revised versions of the DC metadata for a given object
> and linking them to each other with the GROUPID. That was fine until I
> got to the structMap and wanted to make the <div> point at the set of
> metadata versions, either by ID or GROUPID. As <div> has no GROUPID
> attribute, that didn't work. Pointing with IDs isn't great because I
> would have to point to one or all of the IDs and not the group as such.
> Ideally, I would like to be able to version the <dmdSec> without
> touching other parts of the METS record.
If I understand this properly, you have an original dmdSec, and a
version. You want the root <div> to point at both. The preferred way
do this would not involved GROUPID at all. If you really want to
root <div> to point at both, you should use the DMDID attribute on div
and list the ID attributes of the two different dmdSecs.
But to be honest, if I understand what you're trying to do, that's not
how I would structure things. If you have two dmdSecs, an out-of-date
(let's call it dmdOne) and a current version (dmdTwo), and you want to
the history/version info, I would have the root <div> point at *only*
version (e.g., <div DMDID="dmdTwo">). I would have a record
in the digiprov section of METS that indicates that the dmdTwo is a
version of dmdOne. That, of course, leaves you with the small problem
defining an extension schema for recording that type of information,
but at least
you're probably not alone with that problem.
Digital Library Development Team Leader
Elmer Bobst Library, New York University
70 Washington Square South
New York, NY 10012
[log in to unmask]