[Koha] Search for "see also" records shows NO RESULTS FOUND

[Michael Kuhn]

Hi

After an update from Koha 3.20.4 we work on a new host with Debian 
GNU/Linux 8 and Koha 17.05.1.


Our catalog contains authority records with "see also" records. For 
example the subject "Buchkultur" has a "see also" record "Lesekultur".


On Koha 3.20 it was possible to search the OPAC for subject "Lesekultur" 
and thus finding the records with subject "Buchkultur".


In Koha 17.05 it will only find the main authority records, but not the 
"see also" records. Thus an OPAC search for "Lesekultur" will find NO 
RESULTS here.


Why is that so? We have tried to relink all authorities (using script 
"link_bibs_to_authorities.pl"). We have also tried to rebuild the Zebra 
index for the authorities, but to no avail.


Are we missing something?

Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Is this an error about Koha?

[Tomas Cohen Arazi]

Struts is a Java framework, unrelated to Koha.


El mié., 2 ago. 2017 a las 10:28, Luis Moises Rojas ()
escribió:

> Hello everybody,
>
> Our server only have Koha, this critical error: The "HTTP: Apache Struts 2
> Remote Code Execution (CVE-2017-5638)" .
>
> I said this, because struts (as you know) is for MVC programing structure.
>
> Thanks.
>
> --
> *Luis Moisés Rojas P.*
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Patron Club feature

[Michael Kuhn]

Hi


We recently upgraded to 17.05.01 from 16.11.05. When we try to use the
clubs feature by clicking on Tools-> Patron Clubs link, we are getting 404
error.


It sounds like there was a problem during the upgrade process, though
I don't know what it might have been. One solution would be to take a
full backup of your Koha database and reinstall 17.05.x from scratch.

Unfortunately it doesn't look like there is any documentation for the
patron clubs feature yet. :(


Features without documentation are almost like non-existing... :(

However, out of curiosity I tried to use the clubs feature in my own 
demo installation as well as in an installation that I recently updated 
from Koha 3.20 to 17.05.


Both of them will show no clubs feature but just a white screen saying 
"Not found" when click the "clubs" link which looks something like this


http://yourhost:yourport/cgi-bin/koha/clubs/clubs.pl

The file system of both hosts don't show no file called "clubs.pl" anywhere.

The output of the update process said only "Upgrade to 16.12.00.027 done 
(Bug 12461 - Add patron clubs feature)" which doesn't indicate any error.


So maybe the error is somewhere in the upgrade routine.

Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Impossible to renew items

[Marc Véron]

It seems that you defined rules for a library 'AbtSchil'. They take 
precedence over rules for 'All libraries'.


In staff client, can you see the rules for 'AbtSchil'? - You have to 
select the library in the drop down above the table to make them visible.


BTW: The wording 'All libraries' is a little bit confusing. It means 
something like: 'Rules that apply (to all libraries) if no matching rule 
for a specific library is found'.



Am 01.08.2017 um 17:09 schrieb mpw:

I'm groping around in the dark when it comes to SQL but I think I was able to
find that answers to your questions.

AllowRenewalIfOtherItemsAvailable is "Don't allow".

In Reports > Create from SQL I created a report as follows:

Report group:
   Select none
SQL:
   SELECT * FROM issuingrules;

I get the following results when I run the report:

categorycode;itemtype;restrictedtype;rentaldiscount;reservecharge;fine;finedays;maxsuspensiondays;firstremind;chargeperiod;chargeperiod_charge_at;accountsent;chargename;maxissueqty;maxonsiteissueqty;issuelength;lengthunit;hardduedate;hardduedatecompare;renewalsallowed;renewalperiod;norenewalbefore;auto_renew;no_auto_renewal_after;no_auto_renewal_after_hard_limit;reservesallowed;holds_per_record;branchcode;overduefinescap;cap_fine_to_replacement_price;onshelfholds;opacitemholds;article_requests
*;*;;0.00;;0.00;3;;0;0;0;;;10;10;14;days;;-1;10;7;;0;;;0;0;*;;0;1;N;no
M;*;;0.00;;0.00;0;;0;0;0;;days;;-1;0;0;;0;;;0;0;AbtSchil;;0;1;N;no
S;*;;0.00;;0.00;0;;0;0;0;;days;;-1;0;0;;0;;;0;0;AbtSchil;;0;1;N;no

Thus it looks like I have three rows in the table. The question now, I
guess, is how do I get rid of them?



--
View this message in context: 
http://koha.1045719.n5.nabble.com/Impossible-to-renew-items-tp5941578p5941789.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Impossible to renew items

[mpw]

OK, I figured it out. At first I wasn't able to see three circulation rules
even though the report showed there were three. I then discovered the 

*"Select a library" dropdown menu *

on the "Defining circulation rules ..." page. I was able to delete all three
of the old rules: one for all libraries, and two for my particular instance.
I then created a new rule and now everything is working.





--
View this message in context: 
http://koha.1045719.n5.nabble.com/Impossible-to-renew-items-tp5941578p5941885.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Is this an error about Koha?

[Luis Moises Rojas]

Hello everybody,

Our server only have Koha, this critical error: The "HTTP: Apache Struts 2
Remote Code Execution (CVE-2017-5638)" .

I said this, because struts (as you know) is for MVC programing structure.

Thanks.

-- 
*Luis Moisés Rojas P.*
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] [Important] Update your MySQL|MariaDB configuration to avoid data loss

[Jon Knight]

On Tue, 1 Aug 2017, Bortel, Gary wrote:

For a multi-tenant installation with multiple MySQL databases...

"The Solution" 
(https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix) 
recommends adding "init-file=/var/lib/mysql/init-file_kohadev.sql" in 
the my.cnf MySQL configuration file, then creating the appropriately 
configured "init-file_kohadev.sql" file. Where there are multiple Koha 
databases, should one add multiple "init-file=..." statements to my.cnf 
as well as multiple init-file_kohadev.sql files? Or will MySQL only 
accept one init-file directive in which case the .sql file would include 
multiple blocks of code...one for each database?


I'd say that its up to you really - both will work.  If you use just one 
"init-file_kohadev.sql" file you'll just have to repeat all the SQL, just 
changing the database in the "use" line. If you've got lots of Koha 
instances that file is going to be quite long.


Personally for tidiness and ease of maintenance I'd probably opt for one 
init file per Koha database, as those would be clearer and could then be 
maintained more easily using normal Linux command line tools and a few 
Perl scripts.  I assume people hosting lots of tenants are probably 
using tools like Ansible to set up provisioning of a new Koha instance so 
these files would be created from a template and just one line 
added/removed from the my.conf file.


Jon
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Searching capability dies every few days - Zebra problem?

[mpw]

Thanks, Mark, for your suggestion. It sounds like it could very well be the
source of my problem. I've followed your advice and will monitor to see if
that solves the problem.

Otherwise I came up with a quick-and-dirty, very non-elegant script that
I've set up to run every five minutes as a cronjob:


> #! /bin/sh
> 
> PATH=/usr/bin:/usr/sbin:/bin
> STR="zebra"
> restart=0
> 
> # See if koha/zebra running
> ps aux | grep $STR | grep -v grep | grep -v restart 2>&1 >/dev/null ||
> restart=1
> 
> if [ $restart -eq 1 ]; then
> echo "Restarting koha/zebra"
> invoke-rc.d koha-common restart
> fi 





--
View this message in context: 
http://koha.1045719.n5.nabble.com/Searching-capability-dies-every-few-days-Zebra-problem-tp5941587p5941853.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha