Dear All, Koha 3.04.01 is currently installed. I am able to see the copies with accession number in staff interface but in OPAC it displays copies not available, I have activated Hold request but two error are displayed.
1. Copies not available for host. 2. Patron have over limit Hold Can anybody suggest. Thanks and Regards R Sunil Kumar Library Technologist. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: 03 January 2012 02:40 To: [email protected] Subject: Koha Digest, Vol 75, Issue 1 Send Koha mailing list submissions to [email protected] 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 [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha digest..." Today's Topics: 1. Fw:Software error (Peter Zhao) 2. Software error (Peter Zhao) 3. Re: Software error (Robin Sheat) 4. Re: Software error (BWS Johnson) 5. Re: Software error (Tomas Cohen Arazi) 6. Authorities lost during upgrade to 3.6.1 (Paul) ---------------------------------------------------------------------- Message: 1 Date: Mon, 2 Jan 2012 14:13:44 +0800 (CST) From: "Peter Zhao" <[email protected]> To: [email protected] Subject: [Koha] Fw:Software error Message-ID: <[email protected]> Content-Type: text/plain; charset="gbk" Hi, Could anyone fix this problem? I use Koha-3.06.02 to install. After installation, everything works well. I would like try use MARC21 and Unimarc in the same system. So I do like this "1.MARC Bibliographic framework 2.New Framework 3.import Unimarc.sql". After created the Unimarc Framework. The system doesn't work well anymore. When I use opac to search,it shows: Software error: Can't call method "data" on an undefined value at /usr/share/koha/lib/C4/Search.pm line 1488. For help, please send mail to the webmaster (webmaster@ubuntu), giving this error message and the time and date of the error. It can't allow to Add MARC Record. Software error: Tag "" is not a valid tag. at /usr/share/koha/lib/C4/Biblio.pm line 2170 For help, please send mail to the webmaster (webmaster@ubuntu), giving this error message and the time and date of the error. How to fix these problem? Do you have any idea to use MARC21 and Unimarc together? Than you. Peter Zhao -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.katipo.co.nz/pipermail/koha/attachments/20120102/b4727b77/atta chment-0001.html> ------------------------------ Message: 2 Date: Mon, 2 Jan 2012 14:14:41 +0800 (CST) From: "Peter Zhao" <[email protected]> To: [email protected] Subject: [Koha] Software error Message-ID: <[email protected]> Content-Type: text/plain; charset="gbk" Hi, Could anyone fix this problem? I use Koha-3.06.02 to install. After installation, everything works well. I would like try use MARC21 and Unimarc in the same system. So I do like this "1.MARC Bibliographic framework 2.New Framework 3.import Unimarc.sql". After created the Unimarc Framework. The system doesn't work well anymore. When I use opac to search,it shows: Software error: Can't call method "data" on an undefined value at /usr/share/koha/lib/C4/Search.pm line 1488. For help, please send mail to the webmaster (webmaster@ubuntu), giving this error message and the time and date of the error. It can't allow to Add MARC Record. Software error: Tag "" is not a valid tag. at /usr/share/koha/lib/C4/Biblio.pm line 2170 For help, please send mail to the webmaster (webmaster@ubuntu), giving this error message and the time and date of the error. How to fix these problem? Do you have any idea to use MARC21 and Unimarc together? Than you. Peter Zhao -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.katipo.co.nz/pipermail/koha/attachments/20120102/7f44ee6b/atta chment-0001.html> ------------------------------ Message: 3 Date: Tue, 03 Jan 2012 02:15:31 +1300 From: Robin Sheat <[email protected]> To: [email protected] Subject: Re: [Koha] Software error Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1" Op 02-01-12 19:14, Peter Zhao schreef: > I would like try use MARC21 and Unimarc in the same system. So I do like > this "1.MARC Bibliographic framework I'm fairly sure that's a bad idea and not possible. The differences between them (in terms of Koha internals) is a lot more than just the MARC type. My natural instinct from the bit quoted would have to be "run away screaming" :) Probably not related to the error you're getting though. Most likely you've got your system set to something (say, MARC21) and by trying to add data in UNIMARC format you're missing out some required fields, or they're being parsed in quite a different fashion, such that it breaks. Even if you fixed that in Koha (which would be a huuuuge job), you'd still have to deal with the fact that Zebra would hate you forever. Robin. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 262 bytes Desc: OpenPGP digital signature URL: <http://lists.katipo.co.nz/pipermail/koha/attachments/20120103/f769e546/atta chment-0001.pgp> ------------------------------ Message: 4 Date: Mon, 2 Jan 2012 05:58:36 -0800 (PST) From: BWS Johnson <[email protected]> To: "[email protected]" <[email protected]> Subject: Re: [Koha] Software error Message-ID: <[email protected]> Content-Type: text/plain; charset=iso-8859-1 Kia ora! >> I would like try use MARC21 and Unimarc in the same system. So I do like >> this "1.MARC Bibliographic framework > > I'm fairly sure that's a bad idea and not possible. The differences > between them (in terms of Koha internals) is a lot more than just the > MARC type. My natural instinct from the bit quoted would have to be "run > away screaming" :) > > Probably not related to the error you're getting though. > > Most likely you've got your system set to something (say, MARC21) and by > trying to add data in UNIMARC format you're missing out some required > fields, or they're being parsed in quite a different fashion, such that > it breaks. > > Even if you fixed that in Koha (which would be a huuuuge job), you'd > still have to deal with the fact that Zebra would hate you forever. > ??? This was my initial reaction, too. Then I turned it over in my head a few times, and there are occasions where I could think having data in both MARC21 and Unimarc would be handy. Places in Europe, say for the UN, might want to have both with good reason. So this is proper thinking in terms of saving the time of the reader. ??? I think the sticking point isn't at having both, but at having both try to occupy a single Koha at a single point in time. I wonder if one might work about the very nasty logical and bibliographic errors that are bound to result in executing this idea by having parallel Koha servers. One could be twiddled to have the parameters for MARC21, one could hold Unimarc. The tricky bit, perhaps, might be synching patron data and item data so that folks knew when summat was out. It would be important to have this element so that folks didn't have to consult 2 catalogues to get their information. 2 records related to a single item is challenging, but I don't think I would pigeon hole it as impossible. Highly improbable and difficult (read costly) to execute, definitely. ??? From a cataloguing perspective, I'd imagine it might be useful someplace larger, so logistically, I can see having a Unimarc cataloguer and a MARC21 cataloguer and never the twain need meet. (Not that one couldn't do both of course.) Cheers, Brooke ------------------------------ Message: 5 Date: Mon, 2 Jan 2012 15:50:33 -0300 From: Tomas Cohen Arazi <[email protected]> To: BWS Johnson <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: [Koha] Software error Message-ID: <CABZfb=Wer3AsL_0RzWnnzc3ZtSDvqvaEY5GqgiwFgoOJ2j=z...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" I'd set two different Koha's and use vufind to replace the opac, and mix them both. For the patrons, an ldap database. Regards To+ El 02/01/2012 10:59, "BWS Johnson" <[email protected]> escribi?: > Kia ora! > > > >> I would like try use MARC21 and Unimarc in the same system. So I do > like > >> this "1.MARC Bibliographic framework > > > > I'm fairly sure that's a bad idea and not possible. The differences > > between them (in terms of Koha internals) is a lot more than just the > > MARC type. My natural instinct from the bit quoted would have to be "run > > away screaming" :) > > > > Probably not related to the error you're getting though. > > > > Most likely you've got your system set to something (say, MARC21) and by > > trying to add data in UNIMARC format you're missing out some required > > fields, or they're being parsed in quite a different fashion, such that > > it breaks. > > > > Even if you fixed that in Koha (which would be a huuuuge job), you'd > > still have to deal with the fact that Zebra would hate you forever. > > > > This was my initial reaction, too. Then I turned it over in my head a > few times, and there are occasions where I could think having data in both > MARC21 and Unimarc would be handy. Places in Europe, say for the UN, might > want to have both with good reason. So this is proper thinking in terms of > saving the time of the reader. > I think the sticking point isn't at having both, but at having both > try to occupy a single Koha at a single point in time. I wonder if one > might work about the very nasty logical and bibliographic errors that are > bound to result in executing this idea by having parallel Koha servers. One > could be twiddled to have the parameters for MARC21, one could hold > Unimarc. The tricky bit, perhaps, might be synching patron data and item > data so that folks knew when summat was out. It would be important to have > this element so that folks didn't have to consult 2 catalogues to get their > information. 2 records related to a single item is challenging, but I don't > think I would pigeon hole it as impossible. Highly improbable and difficult > (read costly) to execute, definitely. > From a cataloguing perspective, I'd imagine it might be useful > someplace larger, so logistically, I can see having a Unimarc cataloguer > and a MARC21 cataloguer and never the twain need meet. (Not that one > couldn't do both of course.) > > Cheers, > Brooke > > _______________________________________________ > Koha mailing list http://koha-community.org > [email protected] > http://lists.katipo.co.nz/mailman/listinfo/koha > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.katipo.co.nz/pipermail/koha/attachments/20120102/d875bc70/atta chment-0001.html> ------------------------------ Message: 6 Date: Mon, 02 Jan 2012 16:09:45 -0500 From: Paul <[email protected]> To: "[email protected]" <[email protected]> Subject: [Koha] Authorities lost during upgrade to 3.6.1 Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii"; format=flowed Hoping someone can help, please. We recently upgraded from 3.2 to 3.6.1 and nearly everything went well during import of ~15,000 biblios, but something has happened to the "authorities" -- only newly catalogued (i.e. using 3.6.1) authorities appear in the staff search from <http://koha-admin/cgi-bin/koha/authorities/authorities-home.pl>. All the others are still there: exportauth.pl finds all PERSO_NAME, TOPIC_TERM etc as expected, e.g.: 00389nz a2200133o 4500001000200000003000700002005001700009008003900026040001900065100001700084 6670040001016700099001419420015002408OPIACS20110310122059.0110310|||a||| ||| | ||| d aOPIACScOPIACS aAbbass, D.K. aMachine generated authority record. aWork cat.: (OPIACS)3: Abbass, D.K., Radeau Land Tortoise, North America's oldest warship, 1993 aPERSO_NAME but Koha no longer appears to "cross reference" them as far as staff is concerned. For example, when a cataloguer attempts to enter another title by Abbass, D.K. (the "authority" I quote above), she cannot find it in the drop-down for 100a I'm sure there's a simple fix, but at the moment I'm tearing my hair out -- thanks in advance. Paul ------------------------------ _______________________________________________ Koha mailing list [email protected] http://lists.katipo.co.nz/mailman/listinfo/koha End of Koha Digest, Vol 75, Issue 1 *********************************** _______________________________________________ Koha mailing list http://koha-community.org [email protected] http://lists.katipo.co.nz/mailman/listinfo/koha

