Interesting! Alas, I am a Mac OS X user, so I guess I can't take a
look. Nevertheless...
On Tuesday, September 16, 2003, at 10:58 AM, Dieter Köhler wrote:
> However, while a MODS record is gathering a lot of information
> directly in one record, much of this should be stored separately in
> the catalog of my application. For example the meta-data for a
> journal article should be stored separately from the meta-data of the
> journal issue it appeared in,
But can't MODS handle this, with its support of xlink?
> and be linked by an intermediate information object that represents
> the "appearance" relation. If later the article reappears in another
> publication a new additional "appearance" relation is added to the
> catalog pointing to this other publication.
Isn't this "manifestation" in the language of the FRBR?
> Another problem is that some features of MODS seem to be too
> sophisticated for my target audience of humanities scholars. An
> example is the nonSort element in the titleInfo. I would prefer here
> to encode the whole title in one element and use another (repeatable)
> element to include sorting hints:
:-) I don't see how your example below is easier than how this would
be handled in MODS. Why not just have a list of non-sort words (the,
a, etc., etc.) in the application? Then you'd just have:
<titleInfo>
<title>The Naïveté of Louis XVI</title>
</titleInfo>
Bruce
> <titleInfo>
> <title>The Naïveté of Louis ⅩⅥ</title>
> <sortkey type='full'>The Naivete of Louis XVI</sortkey>
> <sortkey type='skipping'>Naivete of Louis XVI</sortkey>
> </titleInfo>
>
> I do not advocate here to include this notion into MODS, because it
> would break its design principle to be a derivative of MARC. This
> notion is only an example for a modification I am intending for my
> application.
|