Re #1. I've noticed it goes offline for a while when the LC is
#5. <placeTerm> is required. No MODS elements have mixed content.
#6. From the user guidelines:
"identifier" contains a unique standard number or code which
distinctively identifies a resource."
A URI in <identifier>, then, should be a canonical name for the
resource, same as an ISBN in <identifier> would be. A URI in
<<location> is where the resource may be found at the time, no
different than a shelf location.
#7. Could that information be coded under <originInfo>?
From: [log in to unmask]
Sent: Tuesday, December 09, 2003 00:11
To: <[log in to unmask]>
Subject: [MODS] A compendium of MODS questions
A series of queries to the list/LC.
1. The MODS review page at:
http://www.loc.gov/standards/mods/changes 3 0.html gives the following
for the location of the schema
http://www.loc.gov/standards/mods/v3/mods 3 0 draft nov 24.xsd
but the file is not at that location. Could you advise the correct
I can't get my files to validate as I'm including V3 coding but
the older version.
2. LC colleagues any timelines on updated MODS2MARCXML and
stylesheets becoming available?
3. I've noticed a discrepancy between the MODS2MARC mapping for
<originInfo><dateCaptured> and the Guidelines. Mapping reads:
<dateCaptured> with encoding="iso8601" 033 ind1=0 ind2=0 $a
with point="start" and 033 ind1=2 ind2=0 first $a encoding="iso8601"
<dateCaptured> with point="end" and 033 ind1=2 ind2=0 second $a
with the ind2=0 Capture, defined as:
The recording of sound, the filming of visual images, the making or
producing of an item, including the creation of an item not involving
recording or filming.
However, the MODS guidelines state:
"dateCaptured" contains the date on which the resource was digitized or
subsequent snapshot was taken. This is particularly useful for Web
because of their changeability. This could be a date that the resource
captured or could also be the date of creation.
I'd just like to check that <dateCaptured> is the most appropriate
store information about recording dates.
4. I'd really like some advice on <relatedItem type="host">,
I see there are some additions there, and there are some special issues
we'll be converting these records to MARCXML (and MARC doesn't handle
thiings particularly well!).
We have some sample records output from ScreenSound Australia's MAVIS
database, which incorporates the concepts of 'cover' and 'track' level
records. I've included the following coding:
<title>Josie and Me; Pagan Love Song</title>
<physicalDescription>1, Shellac disc (78s,
10" Standard Play</physicalDescription>
inside a MODS record for one of the components (which includes a URL to
online sound recording etc.). This will all map to various 773 sub
but looking at the changes to V3.0, I can see quite a lot of 'part'
Any advice on how these might be used, and what MARC fields and sub
they might map to?
5. In V3.0, we now have
<placeTerm type="code" or "text" authority="">
Could you advise whether <placeTerm> is required (as namePart is
or whether it is acceptable to simply have <place>Australia</place>
6. Now that MODS allows us to include a URL for an online resource in
<identifier type="uri> AND
are others planning to include this information in both places and only
7. My colleagues in the Australian National Bibliographic Database
whether any other organisations had raised the needs for a MODS
to MARC 008 character position 28 to represent government publications?
Would you use
<genre authority="marc">government publication</genre>
But in this case, there is no way to indicate the jurisdictonal level.
is an issue for us as we are using MODS and our new Harvester system to
metadata bout online government publications through to the NBD.
Dr Marie Louise Ayres
Project Manager, Music Australia
National Library of Australia
Parkes ACT 2600
Email: [log in to unmask]
Phone: +61 2 6262 1536
Fax: +61 2 6273 5081