LISTSERV mailing list manager LISTSERV 16.0

Help for MODS Archives


MODS Archives

MODS Archives


MODS@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MODS Home

MODS Home

MODS  August 2003

MODS August 2003

Subject:

Re: MODS Draft Version 3.0 available for review

From:

Marie-Louise Ayres <[log in to unmask]>

Reply-To:

Metadata Object Description Schema List <[log in to unmask]>

Date:

Mon, 25 Aug 2003 10:55:47 +1000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (154 lines)

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
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

May 2021
November 2020
September 2020
August 2020
July 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
October 2019
September 2019
August 2019
June 2019
May 2019
March 2019
February 2019
January 2019
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
February 2008
January 2008
December 2007
November 2007
October 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager