There's a new MARC 21 authorities to MADS mapping out to correct these
(and other) problems. See:
Please report any errors to us. We should have a transformation available
(MARC authorities to MADS) soon.
On Thu, 22 Sep 2005, Houghton,Andrew wrote:
> > -----Original Message-----
> > From: Metadata Object Description Schema List
> > [mailto:[log in to unmask]] On Behalf Of Rebecca S. Guenther
> > Sent: 20 September, 2005 09:42
> > To: [log in to unmask]
> > Subject: [MODS] MADS mapping draft
> > Please note that we've made some changes to the draft MARC
> > authorities to MADS mapping, since we discovered in writing
> > the stylesheet for conversion that the authority attribute
> > was missing. That became very complicated particularly
> > because of LCSH coding rules. A revision is up at:
> > http://www.loc.gov/standards/mads/mads-mapping.html
> > Please let us know if you see and possible errors.
> Looking at the mappings we noticed that there are no mappings for 180, 181, 182 and 185. In addition, after doing some queries with a recent copy of the LC authority file (2005-09-14), we noticed that there are 7 records coded with a tag of 111 which have an LCCN prefix of sh and there are 466 records coded with a tag of 130 which have an LCCN prefix of sh.
> There doesn't appear to be any mappings that indicate 111 authority="lcsh" and 130 authority="lcsh". The only mappings for 111 and 130 are: 111, 130 and 008/11=a authority="naf".
> BTW, for reference here are the LCCN's for the 111:
> sh 85053891
> sh 85053892
> sh 85117102
> sh 85018098
> sh 85019367
> sh 93010664
> sh 93010136
> BTW, for reference here are the LCCN's for the first 7, 130:
> sh 85132126
> sh 85132127
> sh 85132128
> sh 85132129
> sh 85132130
> sh 85132131
> sh 85132132
> Andrew Houghton, OCLC Online Computer Library Center, Inc.