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

koha-3.00.00 make fails
by Rick Welykochy 28 Dec '13

28 Dec '13

Hi all, I have downloaded http://download.koha.org/koha-3.00.00.tar.gz and began installing it on Debian/etch (in a Linux vserver environment). 0. FINE: cd koha-3.00.00 1. FINE: perl Makefile.PL 2. FAIL: make : : : Manifying blib/man3/C4::UploadedFile.3pm Manifying blib/man3/C4::BackgroundJob.3pm Manifying blib/man3/opac::opac-dictionary.3pm Manifying blib/man3/serials::member-search.3pm /usr/bin/perl "-Iblib/arch" "-Iblib/lib" fix-perl-path.PL blib /usr/bin/perl "-Iblib/arch" "-Iblib/lib" rewrite-config.PL blib/KOHA_CONF_DIR/koha-conf.xml Bad arg length for Socket::inet_ntoa, length is 0, should be 4 at rewrite-config.PL line 67. make: *** [blib/KOHA_CONF_DIR/koha-conf.xml] Error 255 Any ideas what went wrong and how to fix? Aside: there were a couple of other problems with this "out of the box" debian based install of Koha 3.0 which had to be fixed along the way, e.g. seven missing perl modules and libgd not found. I'll report on the entire process from unpacking to a running Koha/3.00.00 once I get to the end. cheers rickw -- ________________________________________________________________ Rick Welykochy || Praxis Services || Internet Driving Instructor The manual said Windows XP/SP2 or better so I installed Linux.

4 5

Adding items in Acquisition 3.2
by Marcel de Rooy 18 Mar '11

18 Mar '11

Hi, The new feature (in Koha 3.2) of adding items in Acquisitions with the framework display is quite promising. It appears however that the framework plugins cannot be activated there. Do I overlook something? Or is anyone still working on this functionality? Regards, Marcel

2 1

Solr Search use cases
by LAURENT Henri-Damien 05 Jan '11

05 Jan '11

Hi, we proposed in our solr meeting to gather the use cases that you would like to add and proove with the solr search. We wondered why nobody had added any yet.... And we realized that the document, though public, would not be editable. This has been fixed now. So all the persons who were longing to add usecases are now able to do so. The link is the same as previously publicised. https://spreadsheets.google.com/pub?key=0AuZF5Y_c4pIxdEVzTjUtUGFoQnFpSkpfbT… Please, enter whatever query you have success or problem with on zebra. We will try and do it with solr and then build the user interface for it. Hope that helps. -- Henri-Damien LAURENT

3 3

Ability to hide MARC documentation links
by Tomas Cohen Arazi 29 Dec '10

29 Dec '10

Hi, as those on koha-patches might have seen, I've created a bug and a patch implementing a feature that was on my original post on this enhancement: tha ability to hide links to MARC docs on the cataloguing interface. I implemented it via a syspref. Owen commented on the bug that it would be better (and I fully agree) to enable each user to hide/show the links using javascript and a checkbox. That info could also be saved on a cookie. My question is, do we aim to provide this enhancement for 3.2? It should wait for 3.4? I don't know what approach is more approval-prone for 3.2 and thus, here is an email rom me to koha-devel asking :-D. Thanks To+

2 1

Add lost/claims returned displays to patron record (Bug 4241)
by Owen Leonard 28 Dec '10

28 Dec '10

I have cherry-picked the changes from wip/koha-ptfs/Bug4241 into an up-to-date branch in my development repo: ip-bug-4241-lost-tab-2010-12-28 at http://gitorious.org/koha-dev/koha-dev. I've updated the bug report as well, including these comments: The new functionality seems to be working in that: - marking something lost adds a fine to patron's record - marking something lost does or does not check in the item following the MarkLostItemsReturned system preference. A couple of bugs/to-dos I see: - The template has markup intended to handle deleted items when displaying the list of lost items. From this I assume it is supposed to show "deleted item" in the list if the lost item is deleted." However, when I delete one of the lost items it disappears from the list. - There seems to have been no code added to Harley to properly handle the addition of the MarkLostItemsReturned preference to the database or the incrementation of the version number. I would appreciate testers and comments, especially from those involved in the original creation. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

1 0

Re: [Koha-devel] Circulation history anonymisation
by Thomas Dukleth 27 Dec '10

27 Dec '10

Reply inline: Original subject: Re: [Koha-devel] OPAC Enhancement in Koha 3.4 1. FEATURES BASED ON INDIVIDUAL CIRCULATION HISTORY. On Sun, December 26, 2010 18:03, David Schuster wrote: > These wold be great developments - The proposed features for using correlations of circulation history would produce some useful and interesting correlations which could have the advantage of using large passively acquired data sets. However, passive circulation or purchase history, is a weak basis to inform patron title choice relative to a proper recommendation system using active recommendations and various meta-data sets. Despite the weakness of correlations from circulation history for the purpose of recommendations, if someone is interested in working on developing such features for Koha, then Koha should have such features provided they are properly labelled in some form. "Patrons who borrowed this also borrowed those", would be an appropriate label for mere correlations from circulation history. "Patrons recommend those", would be an inappropriate label for mere correlations from circulation history. 2. PRIVACY USING CIRCULATION HISTORY. 2.1. CIRCULATION HISTORY ANONYMISATION. > but then some of us have issues with > patron privacy... We have parents and teachers asking for a "list of what > student X has checked out" we like to say this is not doable in Koha. Koha will need to constantly improve privacy to stay ahead of Big Brother and comply with privacy laws. Just say no to data retention requests or data retention laws which may be passed and consult appropriate legal advocates if facing data retention mandates from government. The Koha administration interface has a circulation data anonymisation feature in Home > Tools > Patrons (anonymize, bulk-delete). The tool calls C4::Circulation::AnonymiseIssueHistory from tools/cleanborrowers.pl, http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=tools/cleanborrow… . In 2009, Paul Poulain had submitted a patch to allow patrons to protect the privacy of their own circulation history by setting the AnonymousPatron system preference and calling C4::Circulation::AnonymiseIssueHistory from a new script opac/opac-privacy.pl, http://lists.koha-community.org/pipermail/koha-patches/2009-May/003486.html . Both tools/cleanborrowers.pl and opac/opac-privacy.pl require some user to actively actuate a script for circulation history anonymisation. A maintenance script run from cron is needed which would use a system preference for a period to keep circulation history which can be overridden by patrons as at least ether 'no preservation period' or 'preservation forever'. Backup files containing circulation history which has not been anonymised also need to be periodically erased and overwritten with multiple passes including a 'random' overwrite. You should presume that Big Brother might seize a dump of the database at some time in future against your protestations and perhaps without your knowledge. Effort should be taken to minimise the harm in case of such a possible seizure. 2.2. CIRCULATION HISTORY ANONYMISATION WITH CORRELATIONS TO TITLES. > So > if > there was a way to hide the data but use it analytically that would be > fantastic. The suggested circulation history correlation features would need something of a feature for preserving circulation history with correlations between anonymised patrons and titles borrowed instead of only anonymous circulation history with no correlations. Complete pseudonymous circulation history would be the equivalent to having no circulation history anonymisation for anyone with access to a full dump of the database and the source code. Only creating a new anonymous patron ID for holding circulation history as items are borrowed and/or each time patron circulation history is anonymised, would preserve any correlations between anonymised patrons and titles borrowed. Preserving correlations for works, expressions, or manifestations would preserve anonymity better than preserving correlations to individual item barcodes. Beware that even such anonymised correlations could be merely a thin veil of anonymity if the data set would be relatively small or the period between anonymisation actions relatively large. [...] Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com +1 212-674-3783

2 3

LDAP Integration
by Edward Allen 27 Dec '10

27 Dec '10

I currently have a ldap deployment that has object listed in an hierarchical manner. meaning i have multiple sub-level OU with user objects in those containers. eg "cn=John Tom,ou=purchasing,ou=accounting,ou=users,ou=people,dc=example,dc=org" eg 2 "cn=Mary Joe,ou=Wholesale,ou=Sales,ou=users,ou=people,dc=example,dc=org" in the example given in "Auth_with_ldap.pm" it would seem that koha's integration with ldap is expecting a flat structure. could you indicate how best to approach this type of integration?

4 4

Template::Toolkit Catalyst Work
by LAURENT Henri-Damien 24 Dec '10

24 Dec '10

Hi I have tested Template_test branch and it looks great (thanks catalyst) Yet, I have some issues with diacritics. Is it because of Koha, DBI, perl utf8 ? I donot know http://imagebin.org/129237 There is also a problem with hotkeys which prevents the load of the javascript. Hope that helps. -- Henri-Damien LAURENT

2 2

3.2.x Status and Schedule Update
by Chris Nighswonger 24 Dec '10

24 Dec '10

Hi all, Thanks again for all of the hard work toward making the 3.2.2 release happen on schedule. The 3.2.x branch is currently "thawed" and again receiving all applicable commits, so keep them coming! Here is what the 3.2.3 release schedule looks like: January 14, 2011 - 3.2.x enters string freeze in preparation for 3.2.3 release January 20, 2011 - Translation updates pulled January 22, 2011 - 3.2.3 released; 3.2.x thawed. Please note that I will be out of reach of all electronic communication for 7 days beginning on Dec. 27, 2010, for a bit of a holiday. Kind Regards, Chris

1 0

Failing test cases
by Robin Sheat 22 Dec '10

22 Dec '10

I've been attempting to build a new set of packages for 3.2.1, however part of building the packages is running tests. If you attempt to run "make -j1 test" on a system that doesn't have a koha database with the default account and password configured, they will fail. This seems to be because the modules that they're testing include C4::Auth or C4::Context, which tries to talk to the DB. What's the recommended solution to this? My thinking is that anything that requires a database connection should be moved to its own directory so that it won't be run by default (or, better, it should be designed in such a way to not require a database. But that's possibly significantly harder.) I can just move the problematic tests[0] out of the way for the sake of the packages, but that's definitely not the right solution. Robin. [0] 00-load, Auth_with_cas, External_BakerTaylor, Reports_Guided, Service, Tags, UploadedFile, and VirtualShelves.

2 1