Tuesday, February 14, 2006 23:08 CST Hi, Carol, Just in quick response to your inquiry, which I noted before and was hoping somebody more knowledgeable on MARC coding history would respond to ... Now, Dave Bigwood or other cognoscenti can correct this if I have it wrong, but I was given to understand some years ago by an authority I trust that fields like 880 are basically the vestigal remains of the inadequacy of earlier computer systems. When they were conceived, computers were just beginning to be able to handle more than Latin letters with the occasional accent (whereas now we are almost at the point where alternate scripts could be encoded within the same field, as was originally desired/intended -- see AACR). I don't know what Koha's coding of the various scripts used by various languages allows for, but I understood it could handle both roman and non-roman scripts at the same time. ***If that is correct, I don't see why you would need to use the 880 at all. Moreover, even if you still want to do so, Carol, Koha doesn't -- that is, at present, it CAN'T -- make use of the required $6 linking subfield.*** I can't see how you would overcome that barrier without a heavy investment in programming. While you cannot repeat the 100 and 245 in a valid MARC21 record, you can work your way around these limitations (rules) easily enough. For example, one could opt to display a 900 field that could give an alternate graphic representation of the 100. Many ILS make use of 900 to allow for alternate forms of the 100 (an embedded authority). I should think you could add a 900 to your Koha MARC records and display. For the 245, assuming that one is using the 245 for the title coded in the actual non-roman script of the language, one could make use of the 242, Translation of the Title by Cataloguing Agency, to record the romanized transcription and translation. Alternatively, one could make use of a 246. If neither of these solutions is satisfactory/to your liking, as my cataloguing instructor would say, there are always Notes. Whatever you decide to do, just be sure to save your original records first in case you need to revert back to them at a later stage. Hope this helps a bit. Cheers, Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB, Canada P.S. If you still get no response from people with actual experience with the 880, I would suggest writing to one of the language areas at LC that would have recourse to it to see what they would suggest. ============================================================ From: Carol Ku <carolcool01@yahoo.com> Date: 2006/02/14 Tue PM 02:12:07 CST To: Koha Mailing List <koha@lists.katipo.co.nz>, Koha Windows <koha-win32@nongnu.org> Subject: [Koha] Tag 880 Have anyone successfully imported MARC record with tag 880? In Library of Congress, this field contains information of book stored in its native language. In MARC records, there seem to be some fields to match the information in tag 880 to 245(title), 100 (author name) etc... But I know Koha only has the subfield structure. If anyone has used the tag 880, I would like to seek your advice in this area. Thank you. _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Moreover, even if you still want to do so, Carol, Koha doesn't -- that is, at present, it CAN'T -- make use of the required $6 linking subfield.*** I can't see how you would overcome that barrier without a heavy investment in programming. Actually, Koha CAN make use of the $6 linking subfield in tag 880. It requires no programming, just about a minute of time setting up the
From the list, click on 'view subfields' for tag 880 Click on 'Edit Subfields'
On Tue, Feb 14, 2006 at 11:20:49PM -0600, Steven F. Baljkas wrote: framework. See here: http://koha.liblime.com/cgi-bin/koha/acqui.simple/addbiblio.pl (tab 4) To set up 880 $6 in your Koha system do the following: Go the the Koha administration page: /cgi-bin/koha/admin-home.pl Click on 'Biblio framework' Click on 'MARC structure' for the 'default framework' at the bottom of the page, click on 'Add New MARC Tag' Type in the number (880), Label for intranet and OPAC (ALTERNATE GRAPHIC REPRESENTATION), click on 'Repeatable' since 880 is repeatable. Click on 'Save Changes. Now you've added tag 880 and you can add $6. put '6' in the Subfield and change 'managed in tab' to '4'. Click on Save Changes. That's it, you're done! BTW: Steven, this is another example of you framing something in terms of what Koha is capable of doing, when in fact, it's merely a matter of not RTFM. Cheers, -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
Moreover, even if you still want to do so, Carol, Koha doesn't -- that is, at present, it CAN'T -- make use of the required $6 linking subfield.*** I can't see how you would overcome that barrier without a heavy investment in programming. Actually, Koha CAN make use of the $6 linking subfield in tag 880. It requires no programming, just about a minute of time setting up the
From the list, click on 'view subfields' for tag 880 Click on 'Edit Subfields'
Please refer to my comment in blue Joshua Ferraro <jmf@liblime.com> wrote: On Tue, Feb 14, 2006 at 11:20:49PM -0600, Steven F. Baljkas wrote: framework. See here: http://koha.liblime.com/cgi-bin/koha/acqui.simple/addbiblio.pl (tab 4) To set up 880 $6 in your Koha system do the following: Go the the Koha administration page: /cgi-bin/koha/admin-home.pl Click on 'Biblio framework' Click on 'MARC structure' for the 'default framework' at the bottom of the page, click on 'Add New MARC Tag' Type in the number (880), Label for intranet and OPAC (ALTERNATE GRAPHIC REPRESENTATION), click on 'Repeatable' since 880 is repeatable. Click on 'Save Changes. Now you've added tag 880 and you can add $6. put '6' in the Subfield and change 'managed in tab' to '4'. Click on Save Changes. That's it, you're done! i think the $6 linking field is different from a regular subfield a, b or c etc. In MARC, all the information on the book will be stored in the native language in tag 880. Then they use $6 linking field to tie 880 to tag 100 for Name etc... so e.g. 880 $6100 a.... so this tag means information stored here is the author name (designated by code $6100) in e.g Chinese. $6 is not a regular subfield.... BTW: Steven, this is another example of you framing something in terms of what Koha is capable of doing, when in fact, it's merely a matter of not RTFM. Cheers, -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS --------------------------------- Yahoo! Mail Bring photos to life! New PhotoMail makes sharing a breeze.
On Fri, Feb 24, 2006 at 12:26:29PM -0800, Carol Ku wrote:
i think the $6 linking field is different from a regular subfield a, b or c etc.
In MARC, all the information on the book will be stored in the native language in tag 880. Then they use $6 linking field to tie 880 to tag 100 for Name etc... so e.g. 880 $6100 a.... so this tag means information stored here is the author name (designated by code $6100) in e.g Chinese. $6 is not a regular subfield.... OK ... first let's discuss what you're trying to do. I have had two years of Chinese language classes so I know that there are several ways to represent Chinese. Are you attempting to put 'pinyin' in the 100a and then link to the actual characters in 880? What is your goal in using the 880?
Cheers, -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
You are perfectly right. I noticed that most libraries such as Library of Congress, they represent Chinese pinyin in tag 100, and this piece of info is linked to tag 880 $6100 and with other related subfields etc... We would like to do the following: 1) save the pinyin and Chinese in Koha. 2) Display Chinese info in OPAC 3) Allow user to search using pinyin if they don't have Chinese input Since Koha display only one line item for title, author etc, we are thinking may be we need to use MARCEdit to tweak tag 100 to 880 $6100. I was advised by others that I should instead designate new tag e.g. 900 for tag 880 $6100, 901 for tag 880 $6245 etc. To make things more complicated, MARCEdit does not seem to recognize the $6 link either. So it will treat all tag 880 as one tag. Joshua Ferraro <jmf@liblime.com> wrote: On Fri, Feb 24, 2006 at 12:26:29PM -0800, Carol Ku wrote:
i think the $6 linking field is different from a regular subfield a, b or c etc.
In MARC, all the information on the book will be stored in the native language in tag 880. Then they use $6 linking field to tie 880 to tag 100 for Name etc... so e.g. 880 $6100 a.... so this tag means information stored here is the author name (designated by code $6100) in e.g Chinese. $6 is not a regular subfield.... OK ... first let's discuss what you're trying to do. I have had two years of Chinese language classes so I know that there are several ways to represent Chinese. Are you attempting to put 'pinyin' in the 100a and then link to the actual characters in 880? What is your goal in using the 880?
Cheers, -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
participants (3)
-
Carol Ku -
Joshua Ferraro -
Steven F.Baljkas