- Koha-devel - lists.koha-community.org

System groups patches
by Galen Charlton 21 Aug '08

21 Aug '08

Hi, A preliminary series of patches implementing part of the proposed system group functionality is available for review and comments at http://arwen.metavore.com/~gmc/patches/sysgroups/ The patches include: * adding parent/child relationships between libraries * allowing item types and patron categories to be "owned" by a specific library. * changes to the circ rule editor to show only the item types and categories that apply to the selected branch or are inherited from its ancestor libraries. * an option to restrict the locations a non-superlibrarian can log in for * an option to restrict the branches a staff operator is allowed to set circ rules for If you decide to apply the patches and test, please note that there are a couple schema changes, which for now can be installed by running installer/data/mysqlupdatedb_sysgroups.pl. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 0

Koha Error
by Abdou Youssef 21 Aug '08

21 Aug '08

Hello, plz i want a solution tothis problem that appeared when trying to run koha 3.00.00 Koha error The following fatal error has occurred:Access denied for user 'ukoha'@'localhost' to database 'kohadb' at /usr/share/perl/5.8/CGI/Carp.pm line 314. Compilation failed in require at C4/Circulation.pm line 25. BEGIN failed--compilation aborted at C4/Circulation.pm line 25. Compilation failed in require at C4/Overdues.pm line 24. BEGIN failed--compilation aborted at C4/Overdues.pm line 24. Compilation failed in require at C4/Members.pm line 27. BEGIN failed--compilation aborted at C4/Members.pm line 27. Compilation failed in require at C4/Auth.pm line 31. BEGIN failed--compilation aborted at C4/Auth.pm line 31. Compilation failed in require at /usr/lib/cgi-bin/koha/mainpage.pl line 24. BEGIN failed--compilation aborted at /usr/lib/cgi-bin/koha/mainpage.pl line 24.

2 1

Koha import problem
by Jason Macki 20 Aug '08

20 Aug '08

Hello, I've been able to import data from our old library system to Koha by uploading directly into the underlying mysql tables. That includes the marc data as well as the regular data tables. However, something about the ordering (I'm assuming) of the marc tags causes the search functions to not work properly. When I go into a record for editing and resave it through the web interface, the problem is corrected and the search functionality works. Does anyone know if there is a way to programmatically correct disordered Marc records, through a perl script or otherwise? Or do you have any other suggestions? My version of Koha is 2.2.9 running on Linux. Thanks for your time, Jason

1 0

Koha 3.00.00 debian install - a few minor observations
by Rick Welykochy 19 Aug '08

19 Aug '08

Hi all, I have completed a successful install of Koha/3.00.00 on Linux Deb (etch) running as a Linux vserver guest. My thanks and appreciation to all who contributed to making the installation process much easier and far more fool-proof than previous versions of Koha. I appreciated the final web-based configuration step. That allowed me (the sys admin) to hand over a completed install to the librarian and let her configure library thingies the way she wanted. My guess is that the deb-based install will be the easiest for the Linux crowd. Here are a few notes I made during the installation process. Note that the install was done on a *very* barebones instance of debian linux, with only a minimal number of packages installed to get the guest host to boot up. This is why there may have been some environmental differences from what one would normally expect in the base system. * debian package install is a good start and worked well, except libgd was not installed on my system: would be good to detect this and alert the sysadmin SOLUTION: sudo apt-get install libgd2-xpm-dev * cpan Perl package install worked except for 7 missing packages: SOLN: sudo cpan Email::Date GD HTML::Scrubber SMS::Send Text::CSV_XS Text::CSV Text::Iconv Of course, the GD problem was related to my not having libgb2 installed. * several attempts were made by debian apt to install and startup mysql 5 server, which we ignored since we already have a mysql 5 server that we can connect to * for the Koha install itself, the Perl method of make; make test seems wasteful: it copies some 145 MB of perl sources unnecessarily into blib then to /usr/share, and it takes a looooooong time. I suppose the upside is reproduceability and the ease of redoing parts of the make if required. * the instructions did not mention when to create the user 'koha': sudo adduser koha * we opt for having two domains (one for OPAC and one for admin) instead of using ports 80 and 8080. It was trivial to affect this change in the koha-httpd.conf file. Kudos on the Apache side of things :) All in all, a very good show. No hair pulling and minor issues easily resolved. thanks again, rickw -- ________________________________________________________________ Rick Welykochy || Praxis Services || Internet Driving Instructor The manual said Windows XP/SP2 or better so I installed Linux.

1 0

RFC 3.2: AJAX in the staff interface
by Jesse Weaver 18 Aug '08

18 Aug '08

(Full RFC at http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_ajax_in_the_s… ) Currently, in the svc/ directory and tagging tools, there are some cautious forays into using AJAX. However, many more areas of the staff (and possibly patron) interface could be improved using AJAX and well-structured web services. Towards this end, LibLime has made patches for AJAX usage on the circulation and issuing rules editor page. These patches make use of new Perl modules, and are based as much as possible on REST principles. MJ: Yes, the AJAX degrades. It even has its own system preference for the circulation screen.

1 0

Looking for KOHA Solution provider
by Noppadol Weerakitti 18 Aug '08

18 Aug '08

Hi, We have a KOHA project in Thailand and looking for an experienced KOHA solution provider who can spend time and resource here assisting us from planing, design, implement and train KOHA ILS. For more detail please contact directly to noppadol(a)tcdc.or.th Regards, Noppadol W. -- View this message in context: http://www.nabble.com/Looking-for-KOHA-Solution-provider-tp19027040p1902704… Sent from the Koha - Dev mailing list archive at Nabble.com.

1 0

RFC: setting up a test server
by Andrew Moore 15 Aug '08

15 Aug '08

Hi Koha Developers - I'm interested in setting up a system to run our test suite regularly and alert us of the results. You may know this as a smoke tester or a continuous integration server, but essentially, it's a thing that runs the test suite regularly and lets us know when things pass and fail. Here's how I picture it working, and please let me know if you have any suggestions or questions about it. I have set up a smolder server at <http://arwen.metavore.com:8000/app/public_projects/smoke_reports/1> that will accept test reports and display them with pretty red, yellow, and green boxes and other information. I expect my nightly test results to go in there, and if you or others would like to send test results there, that would be great. That's where we can look to make sure that stuff we added yesterday didn't break other features in other places in the code. To get the reports there, I just submitted a patch <http://markmail.org/message/upa6j34f6rwegsgr> for review that adds a few targets to the t/Makefile and a perl program to the t/ directory. These are so that you can run "make submit" from the t/ directory in the distribution to send your test results to the smolder server. I'll set up a cronjob to run the test suite on the latest git repository each night and submit the results to the smolder server. Based on any discussion that this email opens up, I may modify that patch and submit it intending for it to get applied. I've opened up bug 2498 <http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2498> to discuss this. There's also a page on the wiki that I started to describe these tools and how they can be used. <http://wiki.koha.org/doku.php?id=en:development:smoke_reports> You'll notice that none of this actually requires you or any other developers to change their behavior in any way. If you don't like this or have some kind of moral or religious objection to it, you can just ignore all of this smolder and smoke stuff and do just fine. So, let me know what you think, and expect the smoke test results to start showing up in smolder soon. Thanks, -Andy

1 1

RFC 3.2 - hold request targeting
by Galen Charlton 15 Aug '08

15 Aug '08

Hi, For 3.2, LibLime proposes to add a feature to target specific items to fill hold requests. This targeting, which would be done in conjunction with use of the holds queue batch job (build_holds_queue.pl) and its report, would allocate items that are sitting on the shelf to fill specific hold requests. The idea is that the library would run the holds queue report periodically, then use the report to pull items off the shelf in order to fill hold requests. When the report is generated, the batch job would also populate a new table (to be called hold_fill_targets) that recommends that specific items be used to fill specific hold requests. As items from the picklist are checked in, if the item is targeted to a specific hold, it would be used to fill that hold first instead of filling the request that happens to be at the top of the priority queue. Why do that? Suppose that a bib has two items, itemA and itemB, and suppose patron1 has a title-level request on the bib, and patron2 has an item-level request on itemB. Further, suppose that both items are available, meaning that both requests could be filled. At present, whether both requests are actually filled depends on the order in which the items are checked in. If itemA is checked in first, then patron1 gets it, and when itemB is checked in, patron2 gets it. Everybody is happy. However, if itemB is checked in first, patron1's request is filled, but patron2 is left waiting for the item. With the new targeting feature, the batch job will allocate items to fill particular requests, thus allowing all of the available items to be used to fill as many holds as possible, in priority order. The mechanism does assume that the library's workflow is to run the batch job, then *quickly* pull the items to put on the hold shelf or transfer to other branches. This mechanism will also be used to minimize the number of transfers by allocating items located at a branch to fill requests for that same branch. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 1

Email::Date module
by Clay Fouts 14 Aug '08

14 Aug '08

Hello, all. Can anyone tell me what sort of terrible events will transpire if I install libemail-date-perl version 1.101-1 Etch package instead of the 1.103 version recently specified as a Koha dependency? I like to avoid installing modules directly from CPAN, but of course avoiding breakage is a higher priority. Thanks, Clay

2 1

Missing results when searching OPAC
by Daniel Alejandro Benavides D. 14 Aug '08

14 Aug '08

Dear members: We have installed here Koha 3.0 RC1 and after succesful using we have encountered that when searching through OPAC or Intranet interface, we don't get any results that we have seen before. We have made some imports of MARC records but then we can search either those imported too. Looking at mysql server, database koha, table biblio, we have the saved records. The url of the OPCA interface is at: http://168.176.86.15 and the given url when searching for "pascal" the browser url is: http://168.176.86.15/cgi-bin/koha/opac-search.pl?q=pascal Is there any way of altering the database or the system to have direct access to the Database, or better, what could be wrong? Thanks in advance ______________________________________________ Enviado desde Correo Yahoo! La bandeja de entrada más inteligente.

4 3