- Koha - lists.katipo.co.nz

Re: [Koha] Authorities difficulties
by BWS Johnson 25 Jul '09

25 Jul '09

Salvete! I probably sound like a broken record on this, but eXtensible catalogue has an authorities feature that's terribly relevant to the discussion at hand. The burden of the authorities work falls on the computer, so that in a pretend queue you'd see Evanovich, Janet Evanovich, Janet, Evanovich, Janet. Evanovich, Janet, 1943 - (LOC wasn't as nosy as I...) and mebbe even Janet Evanovich It picks up all of the remotely the same entries and leafpiles them for you so you needn't chase em round. Then, the *cataloguer* gets to decide which entries are indeed the same and can be rewritten. Notice how I didn't say the cataloguer had to rewrite them, I said they needed to select the ones to be rewritten. At the end of the day, the human is double checking, as we ought, and the computer is doing the drudgery, as it ought. >Yes, I see... > >However, as we have punctuation in thousands of records, wouldn't be possible to enable input in >bibliogr. fields which are defined as containing authorities? In this way, adding a comma wouldn't be a >problem. >Would anyone know how to enable this? In fact, input in this fields is not allowed (except >BiblioAddsAuthorities preference ON, which would create duplicate records). > >I would also like to ask the question about MergeAuthoritiesOnUpdate Function. Normally, updating >bibliogr. records with the authority (when MergeAuthoritiesOnUpdate is ON) rewrites all the subfields - >also for ex. relator terms (700$e in MARC21 - translator ecc.); but some fields (700$e) are not used in >authorities but in biblios, so updating biblios simply deletes this information. Is there a way how to >exclude this subfield from copying from authorities to the biblios? >- Hide quoted text - That's curious. What would happen to a given record were the first 700e entry different from the authority you were working on and the second entry the same or similar? (But yes, I can see how it's meddlesome to have the programme overwrite things that oughtn't be overwritten.) Cheers, Brooke

1 0

Label Crator - problem with long lines
by Ondrej Mlecka 25 Jul '09

25 Jul '09

Hi all, I tried to print label for books with a text which was longer than one line. I saw that the Laber creator cut the text. Moreover, it cut the text non at the end of the label, but before. (see attached image). Would anyone know what could cause this problem, and if it is possible to print longer texts on Labels? Thank you Ondrej Mlecka Roma

1 0

Re: [Koha] Authorities difficulties
by Ondrej Mlecka 25 Jul '09

25 Jul '09

Yes, I see... However, as we have punctuation in thousands of records, wouldn't be possible to enable input in bibliogr. fields which are defined as containing authorities? In this way, adding a comma wouldn't be a problem. Would anyone know how to enable this? In fact, input in this fields is not allowed (except BiblioAddsAuthorities preference ON, which would create duplicate records). I would also like to ask the question about MergeAuthoritiesOnUpdate Function. Normally, updating bibliogr. records with the authority (when MergeAuthoritiesOnUpdate is ON) rewrites *all *the subfields - also for ex. relator terms (700$e in MARC21 - translator ecc.); but some fields (700$e) are not used in authorities but in biblios, so updating biblios simply deletes this information. Is there a way how to exclude this subfield from copying from authorities to the biblios?- Hide quoted text - Thank you very much Ondrej Mlecka Rome

1 0

Authorities difficulties
by Ondrej Mlecka 24 Jul '09

24 Jul '09

Hi all, I would like to ask two questions on cataloguing with authorities. 1. The first one regards the MergeAuthoritiesOnUpdate function. I have a Personal Name Authority (for ex. "Givord, Robert"), and I use it in bibliogr. records in 700 field (always MARC21), once as translator (700$e - relator term - "tr."), once as author of foreword (700$e:"pref.") etc. When I change the name in Authorities (for example because I add a date of the death, or there is a mistake in the name) and I have the MergeAuthoritiesOnUpdate preferrence ON, it deletes all the relator terms in the bibliogr. records. Is there any way how to update bibliogr. records without deleting the contents of all the 700$e subfields? Obviously, I could have a special authority for Robert Givord as translator, another one for R.G. as author of the foreword etc., but this doesn't seem to me to be a good solution. 2. The second question regards cataloging bibl. records. I want to catalogue a book with a name of a translator. So I choose the name from authorities and I want to add 700$e subfield. For this, I need to add a comma at the end of previous subfield, so as to have, for ex. 700 1# $aGivord, Robert[comma]$etr. But the MARC editor doesn't allow any change in 700$a subfield. I could turn the *BiblioAddsAuthorities preference ON*, so as to allow the input in 700$a field, but this would create automatically one authority for the person as a translator, another one as an author of a foreword etc. Would anyone know how to resolve these problems? Thank you very much Ondrej Mlecka Rome

7 10

Re: [Koha] Authorities difficulties
by BWS Johnson 24 Jul '09

24 Jul '09

Salvete! As far as professors of cataloguing and awful cataloguing students are concerned, I'm sure that Bonnie Dede was fully sane before I sat class... >Colin - the UK way sounds awesome :) hehe > >I have to admit I haven't kept up with RDA - does anyone know if some >of the punctuation rules are removed? > Why, yes, yes I have. Cause I was needling our peeps to make sure they kept up with it, since if we play our cards right we can be ahead of the curve. If you're just getting acclimated with RDA, do not swim for at least 1 hour after reviewing the terms. Party, y'all. No punctuation :D http://www.rda-jsc.org/rdafaq.html#1 Look under 4.5 (I suspect this is because the human brain cannot hold both punctuation rules and RDA frameworks simultaneously. I would have commented on RDA, but I'm not a cataloguer, and I frankly don't feel smart enough to comment. Also, the days that I felt like doing so, there was naught written on subject yet, and well, that felt incompleat.) Cheers, Brooke

1 0

Hints on reconciliation branch
by LAURENT Henri-Damien 24 Jul '09

24 Jul '09

Hi, Release Maintainer for 3.0.x speaking. I will be on holidays tonight for 2 weeks. But you can see some progress about reconciliation branch on koha-maintenance branch reconciliation. Be warned that it is for testing purposes and should not be used in production. Moreover, update database has not been updated yet. This work is in progress. There is already some bases for that. But dbversion numbering has some missing numbers. And you should have some hints about that quite soon. see http://git.koha.org/cgi-bin/gitweb.cgi?p=koha-maintenance.git;a=summary for the code. How can I test it ? if you have a dev version : git remote add maintenance git://git.koha.org/pub/scm/koha-maintenance.git git fetch maintenance git branch --track testing_3.0.2 remotes/maintenance/master git checkout testing_3.0.2 for those who are using HEAD already, either your version is 3.01.00.30 and you have nothing to do OR your version is before, and you may have to fix your kohaversion in your database to set it to 3.00.01.00 so that updatedatabase can update your database. You may have some duplicate warnings for all the transformations which has already been made. then login to intranet and updatedatabase will occur. And test and file any bug to me personnaly. What IS NOT in that version : Nothing from master and 3.0.x. Comments and bug reports welcome. Please, if you see some patches which have not made their way into that branch and which you use, be so kind as to resend them to me personnally. 3.0.x and koha master branch patches should all be there, but maybe some patches sent on list are not integrated. In the future, in order to be sure that patches can be smoothly integrated, I suggest that vendors could open up chosen git branches so that integration of patches can be more sure than simply making it via emails. See git.biblibre.com to see biblibre exposed branches for koha : master is our master branch 3.0.x is our 3.0.x branch official_3.0.x is a copy of official/3.0.x dom_wip is work in progress on dom configuration with git So highly unstable. If someone wants to test. It is the same thing as for koha-maintenance, git remote add biblibre git://git.biblibre.com/koha-biblibre git remote update you can rebase your branches over those remote branches, so that your devs can be on top and you can format-patch and send those patches to me for integration. I'll be back on 10th, August but will participate in IRC meeting. cheers. -- Henri-Damien LAURENT

1 0

Librarian roles in koha 2.2.9
by Eugen Matei 24 Jul '09

24 Jul '09

Hello, I just installed koha 2.2.9 on the SME server (CentOS) - a more difficult task than I thought first, due to some SME configuration, but now it appears that everything works. However, in Koha I don't see a module to set up different librarian roles (someone does only cataloging, someone circulation only, etc.). In mysql I see the kohaadmin user but the koha users table is not populated and I cannot figure out how to do that. Should there be a module to do it? Should it be done in mysql? Please point me to the documentation on this, I cannot find it. Sorry if this is a stupid questions... Eugen Matei

1 0

Re: [Koha] Bulk Marc Import - error
by Librarian, SAIACS 24 Jul '09

24 Jul '09

Hello Friends, Can anyone of us help me off the KOha list? In order to discuss the help personal mails. library(a)saiacs.org Regards Yesan Sellan Chief Librarian SAIACS, Kothanur PO, Bangalore - 560077 -----Original Message----- From: koha-bounces(a)lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of koha-request(a)lists.katipo.co.nz Sent: 24 July 2009 10:41 To: koha(a)lists.katipo.co.nz Subject: Koha Digest, Vol 45, Issue 80 Send Koha mailing list submissions to koha(a)lists.katipo.co.nz To subscribe or unsubscribe via the World Wide Web, visit http://lists.katipo.co.nz/mailman/listinfo/koha or, via email, send a message with subject or body 'help' to koha-request(a)lists.katipo.co.nz You can reach the person managing the list at koha-owner(a)lists.katipo.co.nz When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha digest..." Today's Topics: 1. Can't save MARC - 040 field (Agnes Rivers-Moore) 2. Re: [Koha-devel] Marc framework test error (Joe Atzberger) 3. Bulk Marc Import - error (Librarian, SAIACS) 4. Re: Bulk Marc Import - error (Amit Gupta) ---------------------------------------------------------------------- Message: 1 Date: Thu, 23 Jul 2009 20:10:10 -0400 From: Agnes Rivers-Moore <arm(a)hanover.ca> Subject: [Koha] Can't save MARC - 040 field To: Koha List <koha(a)lists.katipo.co.nz> Message-ID: <4A68FBE2.2080602(a)hanover.ca> Content-Type: text/plain; charset="us-ascii" An HTML attachment was scrubbed... URL: http://lists.katipo.co.nz/pipermail/koha/attachments/20090723/1d874d57/attac hment-0001.htm ------------------------------ Message: 2 Date: Thu, 23 Jul 2009 22:04:02 -0400 From: Joe Atzberger <ohiocore(a)gmail.com> Subject: Re: [Koha] [Koha-devel] Marc framework test error To: Sivasankari <rms(a)srasys.co.in> Cc: koha(a)lists.katipo.co.nz Message-ID: <235bf14f0907231904v568b69a5j19989b185cd3422f(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" 2009/7/14 Sivasankari <rms(a)srasys.co.in> > THis is the error while running marc framework test, how should i resolve > this > Thanks > Sivasankari > Why are you still cross-posting to both koha and koha-devel lists? None of your questions have been related to development, they are just usage problems. Therefore, please send only to koha, not to koha-devel. In this case, the error message is clear. It says that the "PER" Authority Type used in your default framework at 700$a does not exist. That means you have probably deleted it or changed the code. Edit your default framework 700$a to refer to a valid Authority Type, or go add a "PER" Authority Type. Then run the tests again, since there may be additional errors.. -- Joe Atzberger LibLime - Open Source Library Solutions

1 0

Bulk Marc Import - error
by Librarian, SAIACS 24 Jul '09

24 Jul '09

Hello Everyone, I was trying to clean up my records from the database, as I noticed that several hundreds of duplicate records uploaded in the catalogue. Therefore I want to clean up the database and start a fresh. While cleaning I am encountering some errors. Could someone help me out in this? I would greatly appreciate. Error message: jlcopaco(a)jlcopac.org [~]# cd /home/jlcopaco/koha3RC1/misc/migration_tools jlcopaco(a)jlcopac.org [~/koha3RC1/misc/migration_tools]# ./bulkmarcimport.pl -d -t Can't locate C4/Context.pm in @INC (@INC contains: /home/jlcopaco/perl/usr/lib/perl5/5.8.8/x86_64-linux /home/jlcopaco/perl/usr/lib/perl5/5.8.8 /home/jlcopaco/perl/usr/lib/perl5/site_perl/5.8.8/x86_64-linux /home/jlcopaco/perl/usr/lib/perl5/site_perl/5.8.8 /home/jlcopaco/perl/usr/lib/perl5/site_perl /usr/lib/perl5/5.8.8/x86_64-linux /usr/lib/perl5/5.8.8 /usr/lib/perl5/site_perl/5.8.8/x86_64-linux /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.6.2 /usr/lib/perl5/site_perl .) at ./bulkmarcimport.pl line 28. BEGIN failed--compilation aborted at ./bulkmarcimport.pl line 28. jlcopaco(a)jlcopac.org [~/koha3RC1/misc/migration_tools]# pwd /home/jlcopaco/koha3RC1/misc/migration_tools - PWD jlcopaco(a)jlcopac.org [~/koha3RC1/misc/migration_tools]# kind regards Mr. Yesan Sellan Chief Librarian South Asia Institute of Advanced Christian Studies, Kothanur PO Bangalore - 560077 INDIA Alternative Email: yesans(a)gmail.com Ph: 91-80-2846 5649/5235/5344 Fax: 91-80-2846 5412 IMPORTANT : This message is intended only for the addressee. It may contain confidential information. Any unauthorized disclosure is strictly prohibited. If you have received this message in error, please notify us immediately so that we may correct our internal records. Please then delete the original message. Thank you.

2 1

Can't save MARC - 040 field
by Agnes Rivers-Moore 24 Jul '09

24 Jul '09

1 0