Hi Bruce
I can answer your question re <typeOfResource> sound recording-musical and
sound recording-nonmusical.
Here at the National Library of Australia, we are using MODS for the
following projects (with more to come):
* as an exchange format to facilitate harvesting and conversion of
data in multiple original formats/schemas to MARC and subsequent loading
into Australia's National Bibliographic database (NBD). This will allow us
to include records from non-MARC, non-traditional NBD contributors in this
union catalogue (1100 Australian libraries contribute - the database
includes approximately 33 million holdings). Our Harvester will allow
contributors to FTP their data, or make it available for OAI harvesting.
Most (we hope) will have already converted their local record formats to
MODS via XSLT stylesheets. If not, we will convert it for them. Once we
have the data, we will use the MODS to MARCXML stylesheet and then the
MARCXML to MARC conversion tool provided by LC, and then load the data using
the NBD's Batchlink service. We've already done an almost full 'pass' at
this process with a set of 20 000 records from the Australian Music Centre -
I say almost because there are some remaining diacritics encoding issues to
be resolved.
* as a storage format for the MusicAustralia service for which I am
responsible. We will be gathering data from various contributors -
libraries, archives, museums, the commercial sector - via the Harvester
project, and loading all records into the NBD. We'll then extract the
records we want from the NBD and convert them to MODS for the MusicAustralia
service itself. The extract relies on several criteria, one of which is
MARC Ldr/06 value = "j" - so you can see that discriminating between musical
and non-musical sound recordings is very important for MusicAustralia. The
National Library has also recently invested significant resources in
cleaning up the "i" and "j" values in the NBD - and we didn't want this work
compromised by inclusion of records which did not distinguish between these
resource types.
*
Well done to Rebecca and team - we are very excited to see the new draft
version, and believe the Schema will have many applications in Australia.
Best wishes
Marie-Louise
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
http://www.musicaustralia.org
> ----------
> From: Bruce D'Arcus[SMTP:[log in to unmask]]
> Reply To: Metadata Object Description Schema List
> Sent: Saturday, 23 August 2003 9:12 AM
> To: [log in to unmask]
> Subject: Re: [MODS] MODS Draft Version 3.0 available for review
>
> I like the changes! Below are a few comments/questions...
>
> On Friday, August 22, 2003, at 03:54 PM, Rebecca S. Guenther wrote:
>
> > 2. Declares all first-level MODS elements (those immediately
> > subordinate
> > to <MODS>) as global, so they can be root elements of instance
> > documents,
> > or imported into other schemas..
>
> Nice.
>
> > 5. Adds the following enumerated values under <typeOfResource>
> > sound recording-musical (MARC Ldr/06 value "j")
> > sound recording-nonmusical (MARC Ldr/06 value "i")
> > ("Sound recording" by itself will be retained to be used when a
> > mixture of
> > musical and nonmusical or if the user does not need to make the
> > distinction.)
>
> I don't really understand the need for this, but oh well.
>
> > 7. Adds under originInfo:
> > dateValid (MARC 046$m and $n)
>
> I've earlier raised this privately as I've tried to code some example
> records:
>
> Would this element be appropriate for an "access date" for online
> material? I think there needs to be some way of coding this
> information, at least for citations.
>
> > dateModified (MARC 046$j)
> > copyrightDate
> >
> > For all dates adds attribute "qualifier" with values: approximate,
> > inferred, questionable
>
> Great; thanks! But not for names?
>
> > 8. In <place>, <role>, and <language> changes to a consistent
> > treatment
> > of code or text as follows:
> > <place> (MARC 008/15-17; 044, 260$a)
> > <placeTerm>
>
> So this allows further parsing of places? So I could have the
> following?
>
> <placeTerm type="city">New York</placeTerm>
>
> > </place>
> > <role> (MARC 1XX, 7XX $e and $4)
> > <roleTerm>
>
> Why the need for this element? Is it to allow multiple role terms?
>
> > Attributes: authority, type (code or text)
>
> I've not mentioned this before, but I find the text and code elements
> in v2 awkward, so this is a nice improvement.
>
> > 12. Adds <part> to relatedItem (with type="host") to enable detailed
> > coding for generating citations:
> > <part>
> > <detail>
> > Attributes: type, order
> > Type: Suggested values include part, volume, issue, chapter,
> > section, paragraph, track
> > Order: contains a number
> > Subelements:
> > <number>
> > <caption>
> > <title>
>
> Related to the comment above about the code and text elements that are
> being converted to attributes, cannot this information (certainly the
> number) be handled via an attribute switch? Or is the idea here that
> one can then mix text and numbers with the detail element?
>
> > <extent>
> > Attribute: unit
>
> Why use a different attribute name here for the same thing in <detail>?
>
> Bruce
>
