Differentiating multiple topic term thesauri in authorities
My library uses both Library of Congress Subject Headings and MeSH in our bibliographic records. We're looking to upload the MeSH vocabulary into Koha Authorities, and I'm wondering how we can go about distinguishing authority headers from MeSH from those from LCSH (or other sources). Both headings are stored in the USMARC 650 field. They use different second indicators to delineate source; LCSH is 0, MeSH is 2. In the MARC, this is the only way to tell which source a header in a bibliographic record comes from. I would think I should create a new Authority Type for MeSH, but it's MARC framework would be exactly the same as TOPIC_TERM, since the MARC frameworks do not currently factor in indicators in any way. Looking at the code bulkauthimport.pl, which looks at whether the incoming record has certain MARC fields (100 for PERSO_NAME, 150 for TOPIC_TERM, etc.), the mappings are hardcoded. That is, there is no way for me to specify that these incoming MARC authorities, which have 150 fields in them, are MeSH and not TOPIC_TERM. What's the best way to deal with this? Should I patch the bulkauthimport.pl code to allow for specification of the Authority Type? Alter the MARC Frameworks code to respect indicators? Or should I just let MeSH and LCSH co-mingle freely? I think our catalogers would really prefer to have the source of the authority clearly marked when they're editing records; MeSH is more important to us by far than LCSH in most cases. Have any of you out there dealt with multiple subject heading sources before in your Koha installations? Do you have any best practices? Cheers, Ian Walls Systems Integration Librarian NYU Health Sciences Libraries 550 First Ave., New York, NY 10016 (212) 263-8687 </PRE> <html> <body> ------------------------------------------------------------<br /> This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is proprietary, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, or distribution is prohibited. If you have received this email in error please notify the sender by return email and delete the original message. Please note, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email.<br /> ================================= </body> </html> <PRE>
Hi, On Feb 11, 2010, at 4:51 PM, Walls, Ian wrote:
Both headings are stored in the USMARC 650 field. They use different second indicators to delineate source; LCSH is 0, MeSH is 2. In the MARC, this is the only way to tell which source a header in a bibliographic record comes from.
To mention a wrinkle in this - if the second indicator of the 650 is 7, the thesaurus is identified in the subfield $2 of the heading.
I would think I should create a new Authority Type for MeSH, but it’s MARC framework would be exactly the same as TOPIC_TERM, since the MARC frameworks do not currently factor in indicators in any way. Looking at the code bulkauthimport.pl, which looks at whether the incoming record has certain MARC fields (100 for PERSO_NAME, 150 for TOPIC_TERM, etc.), the mappings are hardcoded. That is, there is no way for me to specify that these incoming MARC authorities, which have 150 fields in them, are MeSH and not TOPIC_TERM.
The thesaurus type is orthogonal to the authority record type, so I suggest not creating a whole new framework just for MeSH headings if we can avoid it. Working on including the thesaurus in the bib headings indexes would be an excellent project for 3.4. When I did the config work for the DOM indexing of MARC21 authority records, I indexed the thesaurus - see etc/zebradb/marc_defs/marc21/authorities/authority-koha-indexdefs.xml. Regards, Galen -- Galen Charlton VP, Data Services Equinox Software, Inc. / The Evergreen Experts email: gmc@esilibrary.com direct: +1 352-215-7548 skype: gmcharlt web: http://www.esilibrary.com/
participants (2)
-
Galen Charlton -
Walls, Ian