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

RFC: Multiple hold requests (revisited)
by Stephen G. Edwards 12 Feb '09

12 Feb '09

I am a new developer working on some 3.2 items for the Howard County Library. I'm trying to tackle an RFC that was published a while ago. It specifies the ability to request holds on multiple items at one time. I have just updated the wiki with new details: http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_place_hold_mu… After studying the code a while, I think I have a handle on an approach. I wanted to give the community the opportunity to offer warnings, advice, or ridicule, as warranted. As the wiki implies, these are the things I thought I would need to change to implement the biggest piece, which is to allow multiple holds from the search results page: 1. Add a "Place Hold" button to the search results page. I did this in my sandbox by tweaking "opac-results.tmpl" and "basket.js" (trying to mirror the flow of the "Save" button's functionality). Use this to pass the list of checked biblio numbers to the "opac-reserve.pl" script. 2. Redesign the "opac-reserve.tmpl" template to allow for a list of biblio items, rather than just one. For each biblio, allow the selection of "next available" or "particular item" (if allowed). 3. Update "opac-reserve.pl" to handle multiple biblio numbers and the new template. Is there any reason I shouldn't proceed (carefully) along these lines? I've also noticed what appear to be some irregularities in the behavior of this feature as it is currently implemented in 3.2. I don't know if it is due to the code or my lack of understanding. First, when selecting a "Place Hold" link on the results page, the "opac-reserve.pl" script appears to get called twice on the server with the same arguments. I understand that several round trips are made through the same script to implement the overall flow, but I cannot figure out why just one click causes it to be called twice. The second call appears to be redundant, unless I'm missing something. Also, the end of the "opac-reserve.tmpl" template has a section that appears to be dead code. It is guarded by a check for the "item_types_selected" template variable, but I can't find anyplace that this could be set. The second official trip through the perl script results in a redirect to "opac-user.pl", so the "opac- reserve.tmpl" never even gets used more than once during the flow (at least as far as I can see). Any thoughts on all this are appreciated. -Steve --- Stephen Edwards Alloy Computing, LLC sedwards(a)alloycomputing.com

2 1

syspref maxItemsinSearchResults ?
by Michael Hafen 12 Feb '09

12 Feb '09

While poking around C4/Search.pm I noticed this sys pref being used. But it isn't in the System Preferences. Since it's not there Search.pm ends up with a value of 1 every time. If this sys pref is there it gets used. Will someone please comment on this sys pref. It seems like a nice feature. I'd like to get it in the System Preferences. To do it properly though I'll have to touch the updatedatabase.pl. I don't want to do that unless there's enough interest for the patch to be accepted. ( I've already claimed one db version for a patch that seems to have fallen through the cracks.) Please let me know if you would like this to show in the System Preferences. -- Michael Hafen Systems Analyst and Programmer Washington County School District Utah, USA for Koha checkout http://koha-dev.washk12.org or git://koha-dev.washk12.org/koha

2 2

Item Type Images have various sizes
by Michael Hafen 12 Feb '09

12 Feb '09

Some of my librarians have complained about the item type images on the staff search results page. ( I like the ones that don't complain ;) ) In looking at the css I see a 30px padding to make room for the item type image (which is pulled as a background). This is fine for the npl set, where all the images are 32x32. It's not so good for the bridge set where they are 40x40. It's really not good for the liblime-kids set where the size is 60x60, 62x62, or 90x90. I think it would be best to standardize on a size for these images, so that the css can be set once and look right. I intend to this email to start conversation to that end. All comments welcome. -- Michael Hafen Systems Analyst and Programmer Washington County School District Utah, USA for Koha checkout http://koha-dev.washk12.org or git://koha-dev.washk12.org/koha

2 1

RFC - 3.2 Question - Guided Reports
by David Schuster 11 Feb '09

11 Feb '09

I am wondering if we will see this in the 3.2 release or not??? - Dealing with Guided Reports http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_guided_reports Thanks for any feedback! David Schuster -- View this message in context: http://www.nabble.com/RFC---3.2-Question---Guided-Reports-tp21956057p219560… Sent from the Koha - Dev mailing list archive at Nabble.com.

2 1

A solution to add debugger functionality most koha *.pl scripts, thoughts please?
by Mason James 11 Feb '09

11 Feb '09

Hi Koha developers, I have been talking with John and Paul at BibLibre for some months now about a correct way to add Data::Dumper, Smart::Comments, insert::your::favorite::debugger stuff to the Koha perl files *once and for all* After a few false starts and some googling - this is the method I have used and tested... use C4::Debug; use if $debug, 'Data::Dumper' ; use if $debug, 'Smart::Comments' ; # use if $debug, 'YAML::Dumper; # etc.... It's short, sweet and works a treat ;) I currently waste much time every day adding/removing 'use Data::Dumper/use Smart::Comments' from my files when debugging and then committing patches to koha.org Can we agree to add this code (or something similar) to most *.pm and *.pl files? Is there a better way than this? Is this a bad way? Any improvements or corrections i don't realize? What do other developers do to get around this laborious issue? FYI: this small fix (should it be accepted), will resolve one of my biggest pet-annoyances of the Koha project! Cheers, Mason.

2 6

Re: [Koha-devel] Koha-devel Digest, Vol 39, Issue 9
by Krishnan M 07 Feb '09

07 Feb '09

i had posted this sometime back in response to another thread...i guess this should be in permanent documentation... 1) Ensure your server's hostname is set correctly. Try the command 'hostname' and if it seems incorrect, or reset your hostname as follows: Put your hostname in a file like: /etc/hostname Run the command /bin/hostname -F /etc/hostname Verify again using the command hostname 2) Ensure your /etc/hosts file has the correct entries. In general, it must contain at the minimum: one line with the IP address assigned to your network interface (usually eth0) and hostname that you just assigned one line with the loopback address (127.0.0.1) and the special name 'localhost' If you want to find the IP address that is currently assigned to your network interface, try /sbin/ifconfig The IP addresses and names must be separated by at least a space (usually a tab) You can add other hostnames to the hosts file, but for now, keep it simple. Once you save your hosts file, try a simple ping for the hostnames within this file to see if your server "resolves" them to the assigned IP addresses 3) Lastly, in your virtual hosts entries replace any IP addresses that Koha may have used when generating these files during installation with your hostname. Be consistent across entries and files. 4) Re-start Apache and check if it reports any errors during startup. Remember that the command '/usr/sbin/apachectl -t' reports any errors with Apache configuration, so you may want to do that before re-starting Apache. In the same vein, '/usr/sbin/apachectl -S' lists your virtual host entries and these should have the ones for Koha INTRANET and OPAC. Generally, try these commands before re-starting Apache, so you can fix errors first. If all is fine, you should be able to open up a browser (or telnet session) on your server itself first and check whether you can reach Koha, using just the hostname and port in the URL 5) If this works, move to another computer on the network. Before you do so, you may have to open up firewall ports on your server to let traffic through on the ports for Koha 6) If you use a DNS server on the network, enter the hostname and the IP address for your Koha server and ensure that the DNS has picked up the new records. 7) If not, you will need to enter the hostname and IP address into the hosts file of the PC that you are trying to access Koha from (yes, even Windows machines have one, typically at C:\WINDOWS\system32\drivers\etc). The test of entries made to hosts file is always to try and see if the machine can "resolve" the hostname to the IP address you assigned. 8) Once this is done, fire up the browser on the computer and access the Koha server over the network using the hostname. i know this should be somewhere in documentation, i am planning to submit a HOW-TO for Fedora install soon that does contain this information. The HOW-TO will have information about firewall changes such as iptables configuration as well. regards, krishnan --- On Sat, 7/2/09, koha-devel-request(a)lists.koha.org <koha-devel-request(a)lists.koha.org> wrote: From: koha-devel-request(a)lists.koha.org <koha-devel-request(a)lists.koha.org> Subject: Koha-devel Digest, Vol 39, Issue 9 To: koha-devel(a)lists.koha.org Date: Saturday, 7 February, 2009, 11:00 AM Send Koha-devel mailing list submissions to koha-devel(a)lists.koha.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.koha.org/mailman/listinfo/koha-devel or, via email, send a message with subject or body 'help' to koha-devel-request(a)lists.koha.org You can reach the person managing the list at koha-devel-owner(a)lists.koha.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha-devel digest..." Today's Topics: 1. Re: Trouble using Koha (Partha Mukhopadhyay) 2. Results of library automation survey ... (Krishnan M) ---------------------------------------------------------------------- Message: 1 Date: Fri, 6 Feb 2009 21:17:27 +0800 From: "Partha Mukhopadhyay" <psm_vu(a)india.com> Subject: Re: [Koha-devel] Trouble using Koha To: "Nahuel ANGELINETTI" <nahuel.angelinetti(a)biblibre.com> Cc: koha-devel(a)lists.koha.org Message-ID: <20090206131727.42392CBBD2(a)ws5-11.us4.outblaze.com> Content-Type: text/plain; charset="utf-8" Try http://<ip address of your machine>:8080 partha > ----- Original Message ----- > From: "Nahuel ANGELINETTI" <nahuel.angelinetti(a)biblibre.com> > To: koha-devel(a)lists.koha.org > Subject: Re: [Koha-devel] Trouble using Koha > Date: Thu, 5 Feb 2009 12:18:47 +0100 > > Hi, > > Le Tue, 27 Jan 2009 12:07:05 +0430, > Reza Payandehnik <rpayandehnik(a)auaf.edu.af> a ?crit : > > > Dear Koha Developers > > > > This is Reza Payandehnik, the IT officer in American University of > > Afghanistan. I am really facing a problem with KOHA 3.00 installation > > over the network. Recently, I installed koha on Linux Debian 2.14, > > Apache 2.2, MySQL 5.0 and Perl 2.0. I used a KOHA installation manual > > to install all requirements and dependencies and then I installed > > KOHA. Everything is ok and Koha is working properly on the linux > > machine. > > > > There is no problem on working with KOHA on local linux machine. The > > problem is that KOHA is not accessible through the network. I mean > > windows machines can not get access to it, when someone browses to the > > http://koha:8080/cgi-bin/koha/mainpage.pl , Apache says that the URL > > can not be found on the server. Apache is working properly, becuase I > > installed other applications which they are accessible via the > > network easily, only KOHA can not work on the network. > > I mean, you have a mistake in your apache virtual host configuration, > you should check it. > > bests, > > -- > Nahuel ANGELINETTI > > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.koha.org > http://lists.koha.org/mailman/listinfo/koha-devel > Parthasarathi Mukhopadhyay Department of Library and Information Science University of Burdwan, Burdwan, West Bengal, India -- _______________________________________________ Search for products and services at: http://search.mail.com ------------------------------ Message: 2 Date: Sat, 7 Feb 2009 12:35:25 +0530 (IST) From: Krishnan M <kmlist(a)yahoo.in> Subject: [Koha-devel] Results of library automation survey ... To: koha-devel <koha-devel(a)lists.koha.org>, koha-user <Koha(a)lists.katipo.co.nz> Message-ID: <374460.11699.qm(a)web95106.mail.in2.yahoo.com> Content-Type: text/plain; charset="utf-8" Sorry if this has already been posted to the list, don't remember seeing it....interesting reading... Marshall Breeding has published the results of a library automation survey for 2008. See http://www.librarytechnology.org/perceptions2008.pl As a participant, i was notified, and perhaps others were too. regards, krishnan From Chandigarh to Chennai - find friends all over India. Go to http://in.promos.yahoo.com/groups/citygroups/

1 0

Results of library automation survey ...
by Krishnan M 07 Feb '09

07 Feb '09

Sorry if this has already been posted to the list, don't remember seeing it....interesting reading... Marshall Breeding has published the results of a library automation survey for 2008. See http://www.librarytechnology.org/perceptions2008.pl As a participant, i was notified, and perhaps others were too. regards, krishnan From Chandigarh to Chennai - find friends all over India. Go to http://in.promos.yahoo.com/groups/citygroups/

1 0

Re: [Koha-devel] Trouble using Koha
by Partha Mukhopadhyay 06 Feb '09

06 Feb '09

Try http://<ip address of your machine>:8080 partha > ----- Original Message ----- > From: "Nahuel ANGELINETTI" <nahuel.angelinetti(a)biblibre.com> > To: koha-devel(a)lists.koha.org > Subject: Re: [Koha-devel] Trouble using Koha > Date: Thu, 5 Feb 2009 12:18:47 +0100 > > Hi, > > Le Tue, 27 Jan 2009 12:07:05 +0430, > Reza Payandehnik <rpayandehnik(a)auaf.edu.af> a écrit : > > > Dear Koha Developers > > > > This is Reza Payandehnik, the IT officer in American University of > > Afghanistan. I am really facing a problem with KOHA 3.00 installation > > over the network. Recently, I installed koha on Linux Debian 2.14, > > Apache 2.2, MySQL 5.0 and Perl 2.0. I used a KOHA installation manual > > to install all requirements and dependencies and then I installed > > KOHA. Everything is ok and Koha is working properly on the linux > > machine. > > > > There is no problem on working with KOHA on local linux machine. The > > problem is that KOHA is not accessible through the network. I mean > > windows machines can not get access to it, when someone browses to the > > http://koha:8080/cgi-bin/koha/mainpage.pl , Apache says that the URL > > can not be found on the server. Apache is working properly, becuase I > > installed other applications which they are accessible via the > > network easily, only KOHA can not work on the network. > > I mean, you have a mistake in your apache virtual host configuration, > you should check it. > > bests, > > -- > Nahuel ANGELINETTI > > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.koha.org > http://lists.koha.org/mailman/listinfo/koha-devel > Parthasarathi Mukhopadhyay Department of Library and Information Science University of Burdwan, Burdwan, West Bengal, India -- _______________________________________________ Search for products and services at: http://search.mail.com

1 0

Postgres 8.2 Support for koha 3.0
by Dinesh 06 Feb '09

06 Feb '09

3 2

value_builder plugins (security hole)
by Joe Atzberger 05 Feb '09

05 Feb '09

Koha Devs -- I've been looking at fixing the autopopulation of fields (dateaccessioned, barcode, etc) in cataloging. The architecture is a bit screwy. Some of the scripts in cataloguing/value_builder/ are designed to run as stand-alones and others are called by a "do" statement in additem.pl. Anyway, that's just background. There are two scripts that break security by passing authnotrequired => 1 to get_template_and_user: - cataloguing/value_builder/labs_theses.pl - cataloguing/value_builder/unimarc_field_4XX.pl I defer on updating them myself because they may be obsolete entirely. Can anyone at BibLibre comment on the status of these scripts? --Joe Atzberger, LibLime

2 1