Re: [Koha] Fwd: Converting MARC 21 from AACR2 to RDA
On a sort of related point, our cataloguers have recently brought to my attention the "new" RDA "264 - Production, Publication, Distribution, Manufacture, and Copyright Notice" field, which some of the Z39.50 imports appear to be using *instead of* 260 -- they tell me they're seeing it more and more often. 264 does not exist in Default framework (therefore in no others) so they are having to manually copy the data fields. Has anyone looked into this? Any thoughts of how best for Koha to deal with it? Thanks -- Paul At 10:35 AM 7/6/2015 -0700, Hernandez, Heather wrote:
Forgot to also send this to the list! --h2
---------- Forwarded message ---------- From: Hernandez, Heather <heather_hernandez@nps.gov> Date: Mon, Jul 6, 2015 at 10:34 AM Subject: Re: [Koha] Converting MARC 21 from AACR2 to RDA To: Elaine Bradtke <eb@efdss.org>
Hi, Elaine--
Cataloging rules change, and IMNSHO, "old" doesn't mean "wrong." We have records in our catalog that are perfectly correct ISBD, AACR, AACR2 and now RDA, and they all seem to exist together happily! Retroactively trying to change catalog records from one cataloging rule set to another could be problematic, since the rules for what data must be transcribed from the item, and how, can differ greatly. We are a museum library, though, and so may be paying greater attention to visualizing the exact nature of the item from the cataloging record than most libraries!
We're creating all new cataloging records according to RDA--there is a sound recording here: http://keys.bywatersolutions.com/cgi-bin/koha/opac-detail.pl?biblionumber=36...
And a list of some RDA records here: http://keys.bywatersolutions.com/cgi-bin/koha/opac-shelves.pl?viewshelf=52&sortfield=
Hope this helps! Cheerio, h2 ~~~~~~~~~~~~~~ Heather Hernandez Technical Services Librarian San Francisco Maritime National Historical Park Research Center 415-561-7032, heather_hernandez@nps.gov http://www.nps.gov/safr/learn/historyculture/museum-collections.htm
"The sailor does not pray for wind, he learns to sail."--Gustaf Lindborg _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
There is an RDA Framework that should handle all these fields http://wiki.koha-community.org/wiki/MARC_frameworks I have one installed (an earlier version it seems, looks like I'd better update that). Our staff are supposed to check for those telltale RDA fields in downloads and use the appropriate template. On Mon, Jul 6, 2015 at 7:05 PM, Paul A <paul.a@navalmarinearchive.com> wrote:
On a sort of related point, our cataloguers have recently brought to my attention the "new" RDA "264 - Production, Publication, Distribution, Manufacture, and Copyright Notice" field, which some of the Z39.50 imports appear to be using *instead of* 260 -- they tell me they're seeing it more and more often.
264 does not exist in Default framework (therefore in no others) so they are having to manually copy the data fields.
Has anyone looked into this? Any thoughts of how best for Koha to deal with it?
Thanks -- Paul
At 10:35 AM 7/6/2015 -0700, Hernandez, Heather wrote:
Forgot to also send this to the list! --h2
---------- Forwarded message ---------- From: Hernandez, Heather <heather_hernandez@nps.gov> Date: Mon, Jul 6, 2015 at 10:34 AM Subject: Re: [Koha] Converting MARC 21 from AACR2 to RDA To: Elaine Bradtke <eb@efdss.org>
Hi, Elaine--
Cataloging rules change, and IMNSHO, "old" doesn't mean "wrong." We have records in our catalog that are perfectly correct ISBD, AACR, AACR2 and now RDA, and they all seem to exist together happily! Retroactively trying to change catalog records from one cataloging rule set to another could be problematic, since the rules for what data must be transcribed from the item, and how, can differ greatly. We are a museum library, though, and so may be paying greater attention to visualizing the exact nature of the item from the cataloging record than most libraries!
We're creating all new cataloging records according to RDA--there is a sound recording here:
http://keys.bywatersolutions.com/cgi-bin/koha/opac-detail.pl?biblionumber=36...
And a list of some RDA records here:
http://keys.bywatersolutions.com/cgi-bin/koha/opac-shelves.pl?viewshelf=52&sortfield=
Hope this helps! Cheerio, h2 ~~~~~~~~~~~~~~ Heather Hernandez Technical Services Librarian San Francisco Maritime National Historical Park Research Center 415-561-7032, heather_hernandez@nps.gov http://www.nps.gov/safr/learn/historyculture/museum-collections.htm
"The sailor does not pray for wind, he learns to sail."--Gustaf Lindborg _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Elaine Bradtke Data Wrangler VWML English Folk Dance and Song Society | http://www.efdss.org Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY Tel +44 (0) 20 7485 2206 (This number is for the English Folk Dance and Song Society in London, England. If you wish to phone me personally, send an e-mail first. I work off site) -------------------------------------------------------------------------- Registered Company No. 297142 Charity Registered in England and Wales No. 305999 --------------------------------------------------------------------------- "Writing about music is like dancing about architecture" --Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)
On 07/07/15 04:05, Paul A wrote:
On a sort of related point, our cataloguers have recently brought to my attention the "new" RDA "264 - Production, Publication, Distribution, Manufacture, and Copyright Notice" field, which some of the Z39.50 imports appear to be using *instead of* 260 -- they tell me they're seeing it more and more often.
264 does not exist in Default framework (therefore in no others) so they are having to manually copy the data fields.
Has anyone looked into this? Any thoughts of how best for Koha to deal with it?
Yes Paul, I know you don't like it, but its time to upgrade. Bob
At 11:24 AM 7/7/2015 +1000, Bob Birchall wrote:
On 07/07/15 04:05, Paul A wrote:
On a sort of related point, our cataloguers have recently brought to my attention the "new" RDA "264 - Production, Publication, Distribution, Manufacture, and Copyright Notice" field, which some of the Z39.50 imports appear to be using *instead of* 260 -- they tell me they're seeing it more and more often.
264 does not exist in Default framework (therefore in no others) so they are having to manually copy the data fields.
Has anyone looked into this? Any thoughts of how best for Koha to deal with it?
Yes Paul, I know you don't like it, but its time to upgrade. Bob
Bob, thanks for your thoughts, but as you well know I spent quite some time earlier this year (Koha-devel) looking into 3.18.x on Ubuntu 14.04LTS. We came to the conclusion that the search speed penalty was unacceptable (for us, I am not generalizing), and that there was no solution easily available. For the record, we were truly looking forward to upgrading, but, after over 100 hours of IT time, backed out of it. We rely on Koha, genuinely appreciate it, and since 2010 have developed it from an internal management tool to a full on-line catalogue attracting much more traffic than we expected. We are not a lending library, therefore a lot of Koha's capability is unused, but have customized it to allow for full inventory control (physical and fiscal), the production of tax receipts for our donors, etc., and, above all, the internal (LAN) version has become a very good research tool. As a charity, my budget does not allow me the luxury to upgrade a major system every few weeks or even months. My 58 years of experience with "computer sciences" (the term hadn't even been invented when I first got my hands on an IBM 704) have led me to a philosophical belief in 2-year cycles for upgrades, *exception* made for security fixes. I certainly am not pretending, nor preaching, that this is the right or only approach to IT -- just that it works for me in my circumstances. Best -- Paul --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>
Hi! We have a similar collection to Paul's naval and marine archive, I think--we have over 34,000 titles in our Koha catalog and we are not a lending library (although some materials do circulate to staff). I was surprised to read your message, Paul, about your finding a search speed penalty with 3.18.x--we haven't experienced any degrade in search speed, and are now on 3.18.06. I'm sorry that I can't provide any technical details on this, though--our Koha catalog is hosted and supported by ByWater, so perhaps if you contacted them they could provide you some information on our installation? The feature in 3.18.x that we're using the most (if I remember correctly about when it was included!) is the advanced item search--it's so handy! It's been very useful for us. The adaptations for RDA have also been very useful for us, but perhaps we find this more useful than others, since we contribute to OCLC and all our original cataloging is in RDA. Cheerio! --h2 ~~~~~~~~~~~~~~ Heather Hernandez Technical Services Librarian San Francisco Maritime National Historical Park Research Center 415-561-7032, heather_hernandez@nps.gov http://www.nps.gov/safr/learn/historyculture/museum-collections.htm "The sailor does not pray for wind, he learns to sail."--Gustaf Lindborg
participants (4)
-
Bob Birchall -
Elaine Bradtke -
Hernandez, Heather -
Paul A