Skip
repetitive navigational links
L-Soft  -  Home of  the  LISTSERV  mailing list  manager LISTSERV(R) 14.5
Skip repetitive navigational links
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (December 2006)Back to main MODS pageJoin or leave MODSReplyPost a new messageSearchProportional fontNon-proportional fontLog in
Date:         Fri, 22 Dec 2006 16:03:28 -0500
Reply-To:     Metadata Object Description Schema List <[log in to unmask]>
Sender:       Metadata Object Description Schema List <[log in to unmask]>
From:         Rebecca Lubas <[log in to unmask]>
Subject:      FW: MARC2MODS conversion bug
Comments: To: Metadata Object Description Schema List <[log in to unmask]>
Comments: cc: MacKenzie Smith <[log in to unmask]>
Content-Type: text/plain; charset="us-ascii"

Forwarded on behalf of MacKenzie Smith -----Original Message----- From: MacKenzie Smith [mailto:[log in to unmask]] Sent: Friday, December 22, 2006 2:37 PM I found a bug today in the conversion stylesheet for MARC to MODS http://www.loc.gov/standards/mods/v3/MARC21slim2MODS.xsl If the MARC record has an 010 field with both a current LCCN (subfield a) and an obsolete LCCN (subfield z), the stylesheet puts the good LCCN in the <identifier type="lccn"> element, as you would expect, but it also adds a "invalid="yes"" attribute because of the presence of the subfield z... This is probably true for other fields that define a subfield z for old or obsolete identifier values, I just noticed it in the LCCN conversion. MacKenzie Rebecca L. Lubas MIT Libraries rll@mit.edu [log in to unmask]


Back to: Top of message | Previous page | Main MODS page

LISTSERV.LOC.GOV CataList email list search Powered by LISTSERV email list manager