I've not done this before with name/title headings, but off the top of
my head wonder if there isn't a way to use XLink. Seems like that's
sort of what you're trying to do--link the name and title headings
(although it is really one heading to begin with). I'm probably not
using the xlink attributes correctly here, but I could imagine something
<name type="personal" xlink:type="simple" xlink:title="ME"
<!-- ... -->
<titleInfo type="uniform" xlink:type="simple" xlink:title="ME"
<!-- ... -->
As far as I know, our community hasn't really established best practices
for XLink. Here at Princeton we have done something similar to the
above to link between data available in multiple scripts (Roman and
Arabic, to replicate the use of MARC 880 fields), but I have to admit
that I wasn't very comfortable with it because it wasn't an established
practice. To me it seemed like the better choice over ID and xlink:href
pairs, because we're not really trying to add navigation or imply a
hierarchy (by linking one TO the other, though maybe that's ok in this
Anyway, I don't have too much experience with XLink, but was just
looking at this article:
http://www.xml.com/pub/a/2000/09/xlink/part2.html. Seems like some of
the other xlink:type values might have some interesting things to offer,
but the MODS schema keeps us limited to xlink:type="simple".
I'd be interested to hear others' thoughts on this.
C-17-D2 Firestone Library
Princeton, NJ 08544
Email: [log in to unmask]
Riley, Jenn wrote:
> Hello all,
> I'm having trouble figuring out how to encode a Uniform Title in a MODS record. While some Uniform Titles (e.g., for the Bible) only have a title component, most have both a name and title components, with the title not making sense without the name. This is common for music.
> This is what a sample MARC name-title authority record would show:
> 100 10 |a Beethoven, Ludwig van, |d 1770-1827. |t Symphonies, |n no. 5, op. 67, |r C minor
> And this is how the UT would appear in a MARC bibliographic record:
> 100 1_ |a Beethoven, Ludwig van, |d 1770-1827.
> 240 10 |a Symphonies, |n no. 5, op. 67, |r C minor
> The full UT is split across the 100/240 pair. For a MODS record, one would think Beethoven would go in <name> and Symphonies... in <titleInfo type="uniform">. But how is the connection between the name and the title parts of the full UT made in the MODS record? In MODS, lists all the contributors in <name> elements, whereas in MARC you only have one 100 field - other names are in 7xx fields.
> I'm not advocating MODS adopt the concept of main entry, but to use the UT effectively (which presumably is a goal of MODS since type="uniform" is defined for <titleInfo>) there needs to be *some* way to connect the right name with the UT. I'm very uncomfortable with the idea of including the name as part of the <titleInfo type="uniform"> - is that what is intended? The MARC to MODS mapping seems to support this not being the right thing to do. At <http://www.loc.gov/standards/mods/mods-mapping.html>, it just pulls in 240 data into <titleInfo> - it doesn't include data from the 100. But what other options are there?
> Jenn Riley
> Metadata Librarian
> Digital Library Program
> Indiana University - Bloomington
> Wells Library W501
> (812) 856-5759
> Inquiring Librarian blog: www.inquiringlibrarian.blogspot.com