Re: [Koha] Patron Club feature

[Katrin]

Hi Krishna,

I think this bug is the reason why the patron clubs didn't install properly:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19067

It's on his way into the next stable releases.

For DBMS, see here: 
https://wiki.koha-community.org/wiki/Koha_on_Debian#Debian_Packages_on_Koha


'Koha does not work well with MySQL 5.7 which is shipped with Ubuntu 
16.04. use MariaDB instead'


Hope this helps,

Katrin

On 09.08.2017 17:41, Krishna K wrote:

Hi Michael,

The below link has a reference to using MariaDB. It says - Koha does not
work well with MySQL 5.7 which is shipped with Ubuntu 16.04. use MariaDB
instead.

https://wiki.koha-community.org/wiki/Koha_on_Debian#MySQL.7CMariaDB

I agree with your view in Bug 18962. Now I have the following queries.
Looking forward to help from the Koha community on these

Why Patron Clubs feature didnt get installed when we upgraded to 17.05 ? Is
it because we are having MySql 5.7 ?
Why the upgrade didnt give any error ?
What we should do now to install this feature ?
And should we be moving to MariaDB ? How do we do it ?



On Wed, Aug 9, 2017 at 2:07 PM Michael Kuhn  wrote:


Hi Krishna

You wrote:



The other open bugs in patron clubs feature all relate to using MySQL.
Looks like the clubs feature will get installed properly only if MariaDB
is used.Mark Alexander and Michael Kuhn, are you using MySQL ? Have you
tried the clubs feature using Maria DB ?


Yes, we are using MySQL 5.5.55.

No, we didn't try MariaDB. On the Koha Community page
https://koha-community.org/download-koha/ MySQL is given as the
recommended database management system. MariaDB does not seem to be an
officially supported DBMS or someone forgot to add it there.

Concerning this matter I still support what I already have said in Bug
18962 (Including valid system requirements in Koha manual)
* https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18962

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] Patron Club feature

[Krishna K]

Hi Michael,

The below link has a reference to using MariaDB. It says - Koha does not
work well with MySQL 5.7 which is shipped with Ubuntu 16.04. use MariaDB
instead.

https://wiki.koha-community.org/wiki/Koha_on_Debian#MySQL.7CMariaDB

I agree with your view in Bug 18962. Now I have the following queries.
Looking forward to help from the Koha community on these

Why Patron Clubs feature didnt get installed when we upgraded to 17.05 ? Is
it because we are having MySql 5.7 ?
Why the upgrade didnt give any error ?
What we should do now to install this feature ?
And should we be moving to MariaDB ? How do we do it ?



On Wed, Aug 9, 2017 at 2:07 PM Michael Kuhn  wrote:

> Hi Krishna
>
> You wrote:
>
>
> > The other open bugs in patron clubs feature all relate to using MySQL.
> > Looks like the clubs feature will get installed properly only if MariaDB
> > is used.Mark Alexander and Michael Kuhn, are you using MySQL ? Have you
> > tried the clubs feature using Maria DB ?
>
>
> Yes, we are using MySQL 5.5.55.
>
> No, we didn't try MariaDB. On the Koha Community page
> https://koha-community.org/download-koha/ MySQL is given as the
> recommended database management system. MariaDB does not seem to be an
> officially supported DBMS or someone forgot to add it there.
>
> Concerning this matter I still support what I already have said in Bug
> 18962 (Including valid system requirements in Koha manual)
> * https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18962
>
> 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
>
-- 
Regards,
Krishna
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha giving frequent software errors

[ILOBWeb]

Hi, 

I forget to mention before that I got connection reset error when I clicked on 
Help. At that time, following message was logged in error logs file. 

[Wed Aug 09 14:05:20.165528 2017] [cgi:error] [pid 13318] [client 
199.116.173.196:43345] AH01215: [Wed Aug  9 
14:05:20 2017] help.pl: Use of uninitialized value $url in 
pattern match (m//) at /usr/share/koha/intranet/cgi-bin/help.pl 
line 31.: /usr/share/koha/intranet/cgi-bin/help.pl

Regards,
Gurpreet Kaur Saran
Assistant Web Developer / Assistant développeur web
Official Languages and Bilingualism Institute (OLBI) / Institut des langues 
officielles et du bilinguisme (ILOB)
University of Ottawa / Université d’Ottawa

-Original Message-
From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of ILOBWeb
Sent: August-09-17 13:55
To: Jonathan Druart ; 
koh...@bywatersolutions.com; koha list 
Subject: Re: [Koha] Koha giving frequent software errors

Hello Jonathan,

Yes, error 2(connection error) occurs randomly when we work on Koha. There is 
no particular scenario in which it happens.

We are using Koha 17.05.

How can I differentiate between a warning and a bug?

Regards,
Gurpreet

From: Jonathan Druart [mailto:jonathan.dru...@bugs.koha-community.org]
Sent: August-09-17 12:14
To: ILOBWeb ; koh...@bywatersolutions.com; koha list 

Subject: Re: [Koha] Koha giving frequent software errors

Hello Gurpreet,

Answers inline:
On Wed, 9 Aug 2017 at 11:26 ILOBWeb 
> wrote:
Hello everyone,

We are using Koha for our resource centre and we are getting frequent software 
errors while working on it. Errors are like -

Error 1 :
Software error:

Wrong CSRF token at 
/usr/share/koha/intranet/cgi-bin/members/memberentry.pl 
line 291.

For help, please send mail to the webmaster ([no address 
given]), giving this error message and the time 
and date of the error.

When do you get this error? This error appears when you are submitting a form 
without coming from the form. That should not happen.

Error 2:

This site can't be reached

The connection was reset.

Try:

  *   Checking the connection
  *   Checking the proxy and the firewall
  *   Running Windows Network Diagnostics
ERR_CONNECTION_RESET

Well, you do not reach the website you are trying to access.
Does it happens randomly?

Today, I got error when was working on Koha and to check something I clicked on 
'Help'. I checked the Intranet error logs file and a snapshot of the same is 
below. The highlighted error is the error which was logged today when I clicked 
'Help'.

[Mon Aug 07 15:24:18.684124 2017] [cgi:error] [pid 46288] [client 
72.141.68.213:49598] AH01215: [Mon Aug  7 15:24:18 
2017] manage-marc-import.pl: Can't call method 
"results" on an undefined value at 
/usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl
 line 347.: 
/usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl,
 referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/tools/manage-marc-import.pl

This looks like a bug, what did you do?
Which version of Koha are you using?

[Mon Aug 07 17:01:11.388667 2017] [cgi:error] [pid 46753] [client 
72.141.68.213:51047] AH01215: [Mon Aug  7 17:01:11 
2017] additem.pl: 
DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.  
SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/usr/share/koha/lib/Koha/Objects.pm line 83: 
/usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl, 
referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/cataloguing/additem.pl?op=edititem=55=60=
[Mon Aug 07 17:01:42.857633 2017] [cgi:error] [pid 46763] [client 
72.141.68.213:51057] AH01215: [Mon Aug  7 17:01:42 
2017] additem.pl: 
DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.  
SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/usr/share/koha/lib/Koha/Objects.pm line 83: 
/usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl, 
referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/cataloguing/additem.pl?op=edititem=55=59=
[Tue Aug 08 03:39:01.311411 2017] [cgi:error] [pid 52495] [client 
72.141.68.213:49809] AH01215: [Tue Aug  8 03:39:01 
2017] detail.pl: Use of uninitialized value in concatenation 
(.) or string at /usr/share/koha/lib/C4/Biblio.pm line 1410.: 

Re: [Koha] Patron Club feature

[Michael Kuhn]

Hi Krishna

You wrote:


The other open bugs in patron clubs feature all relate to using MySQL. 
Looks like the clubs feature will get installed properly only if MariaDB 
is used.Mark Alexander and Michael Kuhn, are you using MySQL ? Have you 
tried the clubs feature using Maria DB ?



Yes, we are using MySQL 5.5.55.

No, we didn't try MariaDB. On the Koha Community page 
https://koha-community.org/download-koha/ MySQL is given as the 
recommended database management system. MariaDB does not seem to be an 
officially supported DBMS or someone forgot to add it there.


Concerning this matter I still support what I already have said in Bug 
18962 (Including valid system requirements in Koha manual)

* https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18962

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] Spam from BestBookBuddies (OpenLX)

[Sudhir Gandotra @ Kalculate]

Thanks Jonathan, for pointing out that link on lislinks.com - it was a
un-intended mistake - not knowing that replying to different people would
get consolidated on one page. I have now deleted them, and will take care
of such things in future.

My new request for registration can be the consolidation of earlier
listings.

Best wishes,

Sudhir Gandotra
www.bestbookbuddies.com



On Wed, Aug 9, 2017 at 12:15 AM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> This is spam:
> http://www.lislinks.com/forum/topics/how-to-import-data-
> from-libsys-to-koha
>
> Moreover the request you made got an answer: https://lists.katipo.
> co.nz/pipermail/koha/2016-November/046546.html
> => OpenLX is already listed.
> By the way the link to the demo is down.
>
> On Tue, 8 Aug 2017 at 15:26 Sudhir Gandotra @ Kalculate <
> sud...@kalculate.com> wrote:
>
>> Well Chris Cormack,  It will be very interesting to note that a Koha
>> Service Provider with over 400 Libraries to his credit, will be removed
>> from the official list, because he sent a mail to a Library informing about
>> his Koha Services.
>>
>> It will be an interesting standard to be fixed for this community and to
>> be watched closely by many in the future.
>>
>> It is interesting to note that while you do not rightly want to be part
>> of the trouble between some service providers, you seem to be influenced by
>> some of them. I hope I will be proven wrong on this point, which seems to
>> be clear conclusion from what you wrote.
>>
>> *By the way, how do we decide that my mail to a library, a direct mail
>> sent to them, can be termed as a spam ?*
>>
>> *Since when, did people start talking of their services only when someone
>> asks for them ?*
>>
>> I trust the common sense will prevail and all of us will remain promoting
>> Koha and not the fears of some people around here.
>>
>> By the way, my request for being listed as a Koha service provider
>> (BestBook Buddies.com) is still not approved and I have resent the request
>> today.
>>
>> Sudhir Gandotra
>>
>> On Tue, Aug 8, 2017 at 11:42 PM, Chris Cormack 
>> wrote:
>>
>>> Just a quick note, unsolicited emails, or spam as it is commonly known
>>> is indeed a crime in some jurisdictions. And in almost every one it is
>>> against convention.
>>>
>>> I'm not going to respond to the rest of your email which reads as a
>>> personal fight between you and other Indian Koha developers/companies.
>>> Please leave this kind of email off the list in future.
>>>
>>> And if you plan to continue to send unsolicited emails to people then I
>>> think the request to remove the listing should stand
>>>
>>> Chris
>>>
>>> On 9 August 2017 5:58:37 AM NZST, "Sudhir Gandotra @ Kalculate" <
>>> sud...@kalculate.com> wrote:

 Dear Jonathan Druart,

 I am rather surprised to note this mail.

 The only mail that I see from you to me was as below :

 --

 Jonathan Druart 
 May 17
 to koha

 Dear Sudhir Gandotra,

 You are receiving this email because you are listed as a paid support
 company on the Koha community website (https://koha-community.org/su
 pport/paid-support).

 We are updating the list of paid support companies for Koha on our
 community website. Please, after reading this email, either hit reply or
 complete the form mentioned below to confirm you are still an active
 support company.

 The next development cycle of Koha (17.11) is going to start before the
 month of May is out.
 Over the next 6 months we will be building the latest, even more awesome,
 release of Koha.  We strongly believe that having everybody involved is
 fundamental to achieving this.

 We want to build a task force and for that, we need to know who can commit
 time and effort that we can count on, in order to estimate the goals we can
 reach.
 Even if you have never been involved in the Koha community but are using
 Koha, you can help us by committing just a few hours each month:
 library workers or support companies can contribute massively by providing
 feedback, testing patches, contributing to the documentation or by getting
 involved in other specific tasks. Even if you do not know how to code you
 can help shape the next release and improve Koha.
 If you want to help, or if you have specific requests for this release,
 please let us know by completing this form:

  https://framaforms.org/ready-to-help-the-koha-community-1493918217 <
>

 Just a couple of hours per month dedicated to the project is a huge help!

 Best regards,
 Jonathan Druart on behalf of the Koha community

 --


 I have not replied to it, as I am usually been travelling extensively for
 the last 12 months, but, within our 

Re: [Koha] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[Chris Cormack]

* BWS Johnson (abesottedphoe...@yahoo.com) wrote:

Kia ora!
 I still hold the firm opinion that deleting the list is a cop out. The 
listing is one of the best ways that new Libraries find support if they are 
reluctant to do things themselves. Folks might want to think about linking Hea 
to this page so that people that are considering Koha can find like minded 
institutions nearby. It would be awesome if there were some way for existing 
libraries to signal that they are open to providing feedback about vendors.


I think in that case, someone else could volunteer (yourself perhaps)
to take this 'cop out' off the people who currently have to deal with
the multiple offlist emails about it. And maintain the list, maybe on the wiki
where it can be done by anyone.



 The suggested name change might help, and I would support that. I would 
also support removing any spammers.
 I feel strongly that Liz improved on the old list substantially.

 It is very easy for companies that are now happily established to want to 
scrap this list. That action punishes startups and the optics are trash. 
Pulling the ladder up after yourself is not attractive.


I find this remark quite offensive. Just FYI. In case you didn't intend
it to be.

Chris


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


--
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand


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

Re: [Koha] Register can not be saved

[Dimitris Antonakis]

Probably you need to rebuild the zebra index. Is the indexer daemon enabled?

On Aug 9, 2017 21:58, "Luis Moises Rojas"  wrote:

> Sorry it is: EDIT RECORD.
> When you modify any things, and saved it: nothing change.
>
> On Wed, Aug 9, 2017 at 2:54 PM, Katrin  wrote:
>
> > Hi Luis,
> >
> > there is no 'edit register' in the english version. Is this maybe a
> > translation?
> >
> > Katrin
> >
> >
> > On 09.08.2017 20:46, Luis Moises Rojas wrote:
> >
> >> Hello everybody,
> >>
> >> If we call a book, and selected EDIT REGISTER, we changed some data
> (i.e,
> >> the title), when we saved it: NOTHING happen.
> >>
> >> Changes are not saved and without any error.
> >>
> >> Any idea?
> >>
> >>
> > ___
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
> >
>
>
>
> --
> *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
>
-- 

Dimitris Antonakis Systems Librarian

mobile: +30 6973306184
email: dimanto...@gmail.com

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

Re: [Koha] Reminder: Internet broadcast of Koha-US

[Christopher Davis]

Lennon,

Thank you for your message. Try again to connecting again- it should be
working now.

Cordially,


Christopher Davis
Systems & E-Services Librarian
Uintah County Library
cgda...@uintah.utah.gov
(435) 789-0091 <14357890091> ext.261
uintahlibrary.org
basinlibraries.org
facebook.com/uintahcountylibrary
instagram.com/uintahcountylibrary


On Wed, Aug 9, 2017 at 2:26 PM, Lennon Mazonde  wrote:

> Hi Christopher,
>
> I tried joining the meetings but couldn't connect. Are there any
> recordings of the events, and will they be made public at some point?
>
> Regards,
>
> Lennon Mazonde
>
>
>
> On 08/08/2017 21:57, Christopher Davis wrote:
>
>> Dear Colleagues,
>>
>> I am excited about the Koha-US conference beginning tomorrow morning. For
>> those of us who cannot make it up to Coeur d'Alene to attend this
>> conference in person, don't worry...the conference can come to you. Look
>> for the "Broadcast" hyperlinks on the webpage found at
>> http://koha-us.net/index.php/2017_Koha-US_Conference. Please note that
>> since there are two concurrent sessions during each time slot, you will
>> need to select one of the two "Broadcast" links (one for the Community
>> Room
>> and one for the Story Room). There is a limited number of seats open for
>> these broadcasts, so connect early before the seats are taken.
>>
>> Please feel free to contact me with your related comments and/or
>> questions.
>>
>> All the best,
>>
>> Christopher Davis
>> Secretary, Koha-US
>> cgda...@uintah.utah.gov
>> ___
>> 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
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Reminder: Internet broadcast of Koha-US

[Lennon Mazonde]

Hi Christopher,

I tried joining the meetings but couldn't connect. Are there any 
recordings of the events, and will they be made public at some point?


Regards,

Lennon Mazonde


On 08/08/2017 21:57, Christopher Davis wrote:

Dear Colleagues,

I am excited about the Koha-US conference beginning tomorrow morning. For
those of us who cannot make it up to Coeur d'Alene to attend this
conference in person, don't worry...the conference can come to you. Look
for the "Broadcast" hyperlinks on the webpage found at
http://koha-us.net/index.php/2017_Koha-US_Conference. Please note that
since there are two concurrent sessions during each time slot, you will
need to select one of the two "Broadcast" links (one for the Community Room
and one for the Story Room). There is a limited number of seats open for
these broadcasts, so connect early before the seats are taken.

Please feel free to contact me with your related comments and/or questions.

All the best,

Christopher Davis
Secretary, Koha-US
cgda...@uintah.utah.gov
___
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] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[BWS Johnson]

Kia ora!
 I still hold the firm opinion that deleting the list is a cop out. The 
listing is one of the best ways that new Libraries find support if they are 
reluctant to do things themselves. Folks might want to think about linking Hea 
to this page so that people that are considering Koha can find like minded 
institutions nearby. It would be awesome if there were some way for existing 
libraries to signal that they are open to providing feedback about vendors.

 The suggested name change might help, and I would support that. I would 
also support removing any spammers.
 I feel strongly that Liz improved on the old list substantially. 

 It is very easy for companies that are now happily established to want to 
scrap this list. That action punishes startups and the optics are trash. 
Pulling the ladder up after yourself is not attractive.
Cheers,Brooke
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Register can not be saved

[Katrin]

Hi Luis,

there is no error message? Can you check the koha-error-log or 
plack-error-log?


Katrin

On 09.08.2017 20:58, Luis Moises Rojas wrote:

Sorry it is: EDIT RECORD.
When you modify any things, and saved it: nothing change.

On Wed, Aug 9, 2017 at 2:54 PM, Katrin > wrote:


Hi Luis,

there is no 'edit register' in the english version. Is this maybe
a translation?

Katrin


On 09.08.2017 20:46, Luis Moises Rojas wrote:

Hello everybody,

If we call a book, and selected EDIT REGISTER, we changed some
data (i.e,
the title), when we saved it: NOTHING happen.

Changes are not saved and without any error.

Any idea?


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





--
/*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] Register can not be saved

[Luis Moises Rojas]

Sorry it is: EDIT RECORD.
When you modify any things, and saved it: nothing change.

On Wed, Aug 9, 2017 at 2:54 PM, Katrin  wrote:

> Hi Luis,
>
> there is no 'edit register' in the english version. Is this maybe a
> translation?
>
> Katrin
>
>
> On 09.08.2017 20:46, Luis Moises Rojas wrote:
>
>> Hello everybody,
>>
>> If we call a book, and selected EDIT REGISTER, we changed some data (i.e,
>> the title), when we saved it: NOTHING happen.
>>
>> Changes are not saved and without any error.
>>
>> Any idea?
>>
>>
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>



-- 
*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] Register can not be saved

[Katrin]

Hi Luis,

there is no 'edit register' in the english version. Is this maybe a 
translation?


Katrin


On 09.08.2017 20:46, Luis Moises Rojas wrote:

Hello everybody,

If we call a book, and selected EDIT REGISTER, we changed some data (i.e,
the title), when we saved it: NOTHING happen.

Changes are not saved and without any error.

Any idea?



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

[Koha] Register can not be saved

[Luis Moises Rojas]

Hello everybody,

If we call a book, and selected EDIT REGISTER, we changed some data (i.e,
the title), when we saved it: NOTHING happen.

Changes are not saved and without any error.

Any idea?

-- 
*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] Koha giving frequent software errors

[ILOBWeb]

Hello Jonathan,

Yes, error 2(connection error) occurs randomly when we work on Koha. There is 
no particular scenario in which it happens.

We are using Koha 17.05.

How can I differentiate between a warning and a bug?

Regards,
Gurpreet

From: Jonathan Druart [mailto:jonathan.dru...@bugs.koha-community.org]
Sent: August-09-17 12:14
To: ILOBWeb ; koh...@bywatersolutions.com; koha list 

Subject: Re: [Koha] Koha giving frequent software errors

Hello Gurpreet,

Answers inline:
On Wed, 9 Aug 2017 at 11:26 ILOBWeb 
> wrote:
Hello everyone,

We are using Koha for our resource centre and we are getting frequent software 
errors while working on it. Errors are like -

Error 1 :
Software error:

Wrong CSRF token at 
/usr/share/koha/intranet/cgi-bin/members/memberentry.pl 
line 291.

For help, please send mail to the webmaster ([no address 
given]), giving this error message and the time 
and date of the error.

When do you get this error? This error appears when you are submitting a form 
without coming from the form. That should not happen.

Error 2:

This site can't be reached

The connection was reset.

Try:

  *   Checking the connection
  *   Checking the proxy and the firewall
  *   Running Windows Network Diagnostics
ERR_CONNECTION_RESET

Well, you do not reach the website you are trying to access.
Does it happens randomly?

Today, I got error when was working on Koha and to check something I clicked on 
'Help'. I checked the Intranet error logs file and a snapshot of the same is 
below. The highlighted error is the error which was logged today when I clicked 
'Help'.

[Mon Aug 07 15:24:18.684124 2017] [cgi:error] [pid 46288] [client 
72.141.68.213:49598] AH01215: [Mon Aug  7 15:24:18 
2017] manage-marc-import.pl: Can't call method 
"results" on an undefined value at 
/usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl
 line 347.: 
/usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl,
 referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/tools/manage-marc-import.pl

This looks like a bug, what did you do?
Which version of Koha are you using?

[Mon Aug 07 17:01:11.388667 2017] [cgi:error] [pid 46753] [client 
72.141.68.213:51047] AH01215: [Mon Aug  7 17:01:11 
2017] additem.pl: 
DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.  
SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/usr/share/koha/lib/Koha/Objects.pm line 83: 
/usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl, 
referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/cataloguing/additem.pl?op=edititem=55=60=
[Mon Aug 07 17:01:42.857633 2017] [cgi:error] [pid 46763] [client 
72.141.68.213:51057] AH01215: [Mon Aug  7 17:01:42 
2017] additem.pl: 
DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.  
SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/usr/share/koha/lib/Koha/Objects.pm line 83: 
/usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl, 
referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/cataloguing/additem.pl?op=edititem=55=59=
[Tue Aug 08 03:39:01.311411 2017] [cgi:error] [pid 52495] [client 
72.141.68.213:49809] AH01215: [Tue Aug  8 03:39:01 
2017] detail.pl: Use of uninitialized value in concatenation 
(.) or string at /usr/share/koha/lib/C4/Biblio.pm line 1410.: 
/usr/share/koha/intranet/cgi-bin/catalogue/detail.pl, 
referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=1
[Tue Aug 08 03:39:50.095831 2017] [cgi:error] [pid 52517] [client 
72.141.68.213:49813] AH01215: [Tue Aug  8 03:39:50 
2017] detail.pl: Use of uninitialized value in concatenation 
(.) or string at /usr/share/koha/lib/C4/Biblio.pm line 1410.: 
/usr/share/koha/intranet/cgi-bin/catalogue/detail.pl, 
referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/tools/upload-cover-image.pl
[Tue Aug 08 18:53:48.745776 2017] [cgi:error] [pid 63052] [client 
137.122.64.13:16643] AH01215: [Tue Aug  8 18:53:48 
2017] detail.pl: Use of uninitialized value in concatenation 
(.) or string at /usr/share/koha/lib/C4/Biblio.pm line 1410.: 
/usr/share/koha/intranet/cgi-bin/catalogue/detail.pl, 
referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/tools/manage-marc-import.pl?import_batch_id=1
[Tue Aug 

Re: [Koha] How to return from version 17.05 to 16.05

[Luis Moises Rojas]

Hello everybody,

Everything was ok.
We restore the database (of course, we were wrong, and we restore a 16.05
database)
We are working again, after 4 days.

Thanks to all

On Wed, Aug 9, 2017 at 11:54 AM, Luis Moises Rojas 
wrote:

> Now we are going to restore a new backup (two weeks ago)
>
> El 9 ago. 2017 11:39 AM, "Luis Moises Rojas" 
> escribió:
>
>> Hello,
>>
>> Backup database was still 16.05.
>>
>>
>> On Wed, Aug 9, 2017 at 11:37 AM, Katrin  wrote:
>>
>>> Hi Luis,
>>>
>>> did you use the database that was updated to 17.05 before or a backup
>>> database that was still 16.05?
>>>
>>> koha-upgrade-schema only works 'upwards', it won't be able to downgrade
>>> a database to the old structure. In 17.05 there was one major change in
>>> moving the marcxml from biblioitems to a new separate table. Other changes
>>> would also be problematic.  So using a 17.05 database with 16.05 code WON'T
>>> WORK.
>>>
>>> The init script and how to install it is described on the wiki page:
>>>
>>> https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix
>>>
>>> If you can't use a database backup from before the attempted update to
>>> 17.05, I strongly recommend returning ot 17.05 and trying to fix the errors
>>> you have seen there.
>>>
>>> Katrin
>>>
>>> On 09.08.2017 16:16, Luis Moises Rojas wrote:
>>>
>>> Hello,
>>>
>>> Finally we have reinstalled 16.05
>>> We ran:
>>> sudo koha-upgrade-schema libraryname
>>> sudo koha-rebuild-zebra -v -f libraryname
>>> sudo koha-rebuild-zebra -a -f  libraryname
>>>
>>> In sudo koha-upgrade-schema we have severals "Select" errors.
>>> When you try to find a BOOK it says: No found
>>> If we search an author says: IN REPOSITORY.
>>>
>>> Why?
>>>
>>> Maybe is because we have to do this: "You need to fix your data in order
>>> to get around this and implement the init script"
>>>
>>> But where is init script and how to used it?
>>>
>>>
>>> On Mon, Aug 7, 2017 at 5:32 PM, Katrin  wrote:
>>>
 Please note, that you will need to use your backup from before updating
 to 17.05, because you can't undo the changes to the database structure
 easily.

 From reading one of your earlier emails - is it possible that you are
 using MySQL 5.7  instead of MariaDB?

 https://wiki.koha-community.org/wiki/Koha_on_Debian#Debian_P
 ackages_on_Koha

 The problem with returning items will probably remain, as we have
 implemented a block on returning items when the issue_id already exists in
 old_issues in 17.05, 16.11, and 16.05. Please see here:

 https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix

 You need to fix your data in order to get around this and implement the
 init script.

 Hope this helps,

 Katrin


 On 07.08.2017 20:50, Luis Moises Rojas wrote:

> We are reinstalling previous version 16.05 with 17.05 is was
> impossible to
> work.
> We can not return book.
> All books where in Reserver
> We can not Catalog.
> And much more.
>
>
> On Mon, Aug 7, 2017 at 2:25 PM, Popoola 
> wrote:
>
> Did you have koha image of your previous version, i mean your previous
>> installation version on your external hard drive or cloud backup?
>> --
>> From: Luis Moises Rojas 
>> Sent: ‎8/‎7/‎2017 19:20
>> To: Popoola 
>> Cc: Comunidad Koha 
>> Subject: RE: [Koha] How to return from version 17.05 to 16.05
>>
>> Yes, I did.
>>
>> El 7 ago. 2017 2:16 PM, "Popoola"  escribió:
>>
>> Hello Luis, when you are performing your upgrading did you backup your
>>> database? or did you export your bibliographic?.If you did any,you
>>> can
>>> restore your previous version. But the best practices is to figure
>>> out the
>>> error you encountered during the upgrade and post it to forum, so
>>> that
>>> members can shares their experience with you
>>> --
>>> From: Luis Moises Rojas 
>>> Sent: ‎8/‎7/‎2017 16:51
>>> To: Comunidad Koha 
>>> Subject: [Koha] How to return from version 17.05 to 16.05
>>>
>>> Hello everybody,
>>>
>>> We upgrade from 16.05 to 17.05.
>>> Now we are having at lot of problems.
>>> We can not work at all.
>>>
>>> Is there is a way to get back?
>>> Previous version where everything was ok?
>>>
>>> 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] Unknown column 'metadata' in 'field list'

[Jonathan Druart]

Vimal,

Koha 17.05 has been released with bug 17898.
With it you should see a new "Update" column on the report list if you have
reports using the biblioitems.marcxml columns.
There is a "Update SQL" button, when clicked a script will update the query
to use the new biblio_metadata column. This will not work in all cases but
if your query is simple it should work.

Regards,
Jonathan

On Wed, 9 Aug 2017 at 02:06 Vimal Kumar V.  wrote:

> Dear Friends,
> I am trying to generate a book list with keywords from 650$a using the
> following SQL query,
>
> SELECT ExtractValue( metadata,
> '//datafield[@tag="650"]/subfield[@code="a"]' ) AS Keyword, items.barcode,
> items.dateaccessioned, items.itemcallnumber, biblio.author, biblio.title,
> biblioitems.pages, biblioitems.publishercode, biblioitems.place,
> biblio.copyrightdate
> FROM items
> LEFT JOIN biblioitems ON
> (items.biblioitemnumber=biblioitems.biblioitemnumber)
> LEFT JOIN biblio ON (biblioitems.biblionumber=biblio.biblionumber)
> ORDER BY LPAD(items.barcode,40,' ') ASC
>
> After running the report, I got the following error message,
>
> The database returned the following error:
> Unknown column 'metadata' in 'field list'
> Please check the log for further details.
>
> Please review the SQL query and help me to solve the problem.
>
>
> Regards,
> --
> Vimal Kumar V.
> Librarian
> School of Indian Legal Thought
> Mahatma Gandhi University
> Kottayam, Kerala
> Web: http://www.vimalkumar.info
> Blogs: http://linuxhalwa.blogspot.com http://kohageek.blogspot.in
> http://dspacegeek.blogspot.in
> http://moovandan.blogspot.in  
> ---
> "I forget what I was taught. I only remember what I have learnt"
> -Patrick White
> ___
> 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] Possibilities and Help in Translation

[Jonathan Druart]

Hello,

It depends on which version of Koha you are going to use, but I would
suggest to translate the latest (17.05).

Regards,
Jonathan

On Wed, 9 Aug 2017 at 10:14 Balaji Ravichandran 
wrote:

> Hi Jonathan,
> I have started Translating Koha to தமிழ்(Tamil) for the version 17.05.
> There is also a version of Koha 3.22 and many other versions. Can you
> please provide suggestions on how to select versions for translating? Some
> are marked as obsolete. Kindly help is selecting versions.
>
> On 3 August 2017 at 19:51, Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> wrote:
>
>> Hi Balaji,
>>
>> Welcome! :)
>>
>> This language already exists on our translation server (
>> http://translate.koha-community.org/ta/).
>> You should take a look at
>> https://wiki.koha-community.org/wiki/Translating_Koha to know how to
>> translate Koha.
>> I am not a translator so I cannot help you more. The language is only 1%
>> translated, you will have a lot of work to translate it completely. Good
>> luck! :)
>>
>> Regards,
>> Jonathan
>>
>>
>> On Thu, 3 Aug 2017 at 09:20 Balaji Ravichandran 
>> wrote:
>>
>> > Hi,
>> > I am new to Koha Community. I have done 4 Koha Setup across TamilNadu,
>> > India. Our Koha Community here has decided to translate Koha into our
>> > native language.
>> >
>> >- Action - Translation
>> >- Language - தமிழ் (Tamil)
>> >
>> > Is Translation possible in Koha? If so, suggest some methods or getting
>> > started docs for it to be useful to the Community here. Also suggest
>> what
>> > needs to be taken care of and important measures to be taken.
>> >
>> > Waiting for feedback from the Community :-)
>> >
>> > --
>> > Best Regards,
>> > Balaji Ravichandran
>> > ___
>> > 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
>>
>
>
>
> --
> Best Regards,
> Balaji Ravichandran
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha giving frequent software errors

[Jonathan Druart]

Hello Gurpreet,

Answers inline:

On Wed, 9 Aug 2017 at 11:26 ILOBWeb  wrote:

> Hello everyone,
>
> We are using Koha for our resource centre and we are getting frequent
> software errors while working on it. Errors are like -
>
> Error 1 :
> Software error:
>
> Wrong CSRF token at /usr/share/koha/intranet/cgi-bin/members/
> memberentry.pl line 291.
>
> For help, please send mail to the webmaster ([no address 
> given]),
> giving this error message and the time and date of the error.
>

When do you get this error? This error appears when you are submitting a
form without coming from the form. That should not happen.

Error 2:
>
> This site can't be reached
>
> The connection was reset.
>
> Try:
>
>   *   Checking the connection
>   *   Checking the proxy and the
> firewall
>   *   Running Windows Network Diagnostics
> ERR_CONNECTION_RESET
>

Well, you do not reach the website you are trying to access.
Does it happens randomly?


> Today, I got error when was working on Koha and to check something I
> clicked on 'Help'. I checked the Intranet error logs file and a snapshot of
> the same is below. The highlighted error is the error which was logged
> today when I clicked 'Help'.
>
> [Mon Aug 07 15:24:18.684124 2017] [cgi:error] [pid 46288] [client
> 72.141.68.213:49598] AH01215: [Mon Aug  7 15:24:18 2017]
> manage-marc-import.pl: Can't call method "results" on an undefined value
> at /usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl line
> 347.: /usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl,
> referer:
> http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/tools/manage-marc-import.pl


This looks like a bug, what did you do?
Which version of Koha are you using?


> [Mon Aug 07 17:01:11.388667 2017] [cgi:error] [pid 46753] [client
> 72.141.68.213:51047] AH01215: [Mon Aug  7 17:01:11 2017] additem.pl:
> DBIx::Class::Storage::DBI::select_single(): Query returned more than one
> row.  SQL that returns multiple rows is DEPRECATED for ->find and ->single
> at /usr/share/koha/lib/Koha/Objects.pm line 83:
> /usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl, referer:
> http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/cataloguing/additem.pl?op=edititem=55=60=
> [Mon Aug 07 17:01:42.857633 2017] [cgi:error] [pid 46763] [client
> 72.141.68.213:51057] AH01215: [Mon Aug  7 17:01:42 2017] additem.pl:
> DBIx::Class::Storage::DBI::select_single(): Query returned more than one
> row.  SQL that returns multiple rows is DEPRECATED for ->find and ->single
> at /usr/share/koha/lib/Koha/Objects.pm line 83:
> /usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl, referer:
> http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/cataloguing/additem.pl?op=edititem=55=59=
> [Tue Aug 08 03:39:01.311411 2017] [cgi:error] [pid 52495] [client
> 72.141.68.213:49809] AH01215: [Tue Aug  8 03:39:01 2017] detail.pl: Use
> of uninitialized value in concatenation (.) or string at
> /usr/share/koha/lib/C4/Biblio.pm line 1410.:
> /usr/share/koha/intranet/cgi-bin/catalogue/detail.pl, referer:
> http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=1
> [Tue Aug 08 03:39:50.095831 2017] [cgi:error] [pid 52517] [client
> 72.141.68.213:49813] AH01215: [Tue Aug  8 03:39:50 2017] detail.pl: Use
> of uninitialized value in concatenation (.) or string at
> /usr/share/koha/lib/C4/Biblio.pm line 1410.:
> /usr/share/koha/intranet/cgi-bin/catalogue/detail.pl, referer:
> http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/tools/upload-cover-image.pl
> [Tue Aug 08 18:53:48.745776 2017] [cgi:error] [pid 63052] [client
> 137.122.64.13:16643] AH01215: [Tue Aug  8 18:53:48 2017] detail.pl: Use
> of uninitialized value in concatenation (.) or string at
> /usr/share/koha/lib/C4/Biblio.pm line 1410.:
> /usr/share/koha/intranet/cgi-bin/catalogue/detail.pl, referer:
> http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/tools/manage-marc-import.pl?import_batch_id=1
> [Tue Aug 08 18:57:20.166232 2017] [cgi:error] [pid 63135] [client
> 137.122.64.13:16842] AH01215: [Tue Aug  8 18:57:20 2017] detail.pl: Use
> of uninitialized value in concatenation (.) or string at
> /usr/share/koha/lib/C4/Biblio.pm line 1410.:
> /usr/share/koha/intranet/cgi-bin/catalogue/detail.pl, referer:
> http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/tools/upload-cover-image.pl
> [Tue Aug 08 19:12:33.214782 2017] [cgi:error] [pid 63456] [client
> 8.28.16.254:2289] AH01215: [Tue Aug  8 19:12:33 2017]
> batch_records_ajax.pl: Use of uninitialized value in array element at
> /usr/share/koha/intranet/cgi-bin/tools/batch_records_ajax.pl line 50.:
> /usr/share/koha/intranet/cgi-bin/tools/batch_records_ajax.pl
> [Tue Aug 08 19:12:33.215002 2017] [cgi:error] [pid 63456] [client
> 8.28.16.254:2289] AH01215: [Tue Aug  8 19:12:33 2017]
> batch_records_ajax.pl: Use of 

Re: [Koha] How to return from version 17.05 to 16.05

[Luis Moises Rojas]

Now we are going to restore a new backup (two weeks ago)

El 9 ago. 2017 11:39 AM, "Luis Moises Rojas" 
escribió:

> Hello,
>
> Backup database was still 16.05.
>
>
> On Wed, Aug 9, 2017 at 11:37 AM, Katrin  wrote:
>
>> Hi Luis,
>>
>> did you use the database that was updated to 17.05 before or a backup
>> database that was still 16.05?
>>
>> koha-upgrade-schema only works 'upwards', it won't be able to downgrade a
>> database to the old structure. In 17.05 there was one major change in
>> moving the marcxml from biblioitems to a new separate table. Other changes
>> would also be problematic.  So using a 17.05 database with 16.05 code WON'T
>> WORK.
>>
>> The init script and how to install it is described on the wiki page:
>>
>> https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix
>>
>> If you can't use a database backup from before the attempted update to
>> 17.05, I strongly recommend returning ot 17.05 and trying to fix the errors
>> you have seen there.
>>
>> Katrin
>>
>> On 09.08.2017 16:16, Luis Moises Rojas wrote:
>>
>> Hello,
>>
>> Finally we have reinstalled 16.05
>> We ran:
>> sudo koha-upgrade-schema libraryname
>> sudo koha-rebuild-zebra -v -f libraryname
>> sudo koha-rebuild-zebra -a -f  libraryname
>>
>> In sudo koha-upgrade-schema we have severals "Select" errors.
>> When you try to find a BOOK it says: No found
>> If we search an author says: IN REPOSITORY.
>>
>> Why?
>>
>> Maybe is because we have to do this: "You need to fix your data in order
>> to get around this and implement the init script"
>>
>> But where is init script and how to used it?
>>
>>
>> On Mon, Aug 7, 2017 at 5:32 PM, Katrin  wrote:
>>
>>> Please note, that you will need to use your backup from before updating
>>> to 17.05, because you can't undo the changes to the database structure
>>> easily.
>>>
>>> From reading one of your earlier emails - is it possible that you are
>>> using MySQL 5.7  instead of MariaDB?
>>>
>>> https://wiki.koha-community.org/wiki/Koha_on_Debian#Debian_P
>>> ackages_on_Koha
>>>
>>> The problem with returning items will probably remain, as we have
>>> implemented a block on returning items when the issue_id already exists in
>>> old_issues in 17.05, 16.11, and 16.05. Please see here:
>>>
>>> https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix
>>>
>>> You need to fix your data in order to get around this and implement the
>>> init script.
>>>
>>> Hope this helps,
>>>
>>> Katrin
>>>
>>>
>>> On 07.08.2017 20:50, Luis Moises Rojas wrote:
>>>
 We are reinstalling previous version 16.05 with 17.05 is was impossible
 to
 work.
 We can not return book.
 All books where in Reserver
 We can not Catalog.
 And much more.


 On Mon, Aug 7, 2017 at 2:25 PM, Popoola 
 wrote:

 Did you have koha image of your previous version, i mean your previous
> installation version on your external hard drive or cloud backup?
> --
> From: Luis Moises Rojas 
> Sent: ‎8/‎7/‎2017 19:20
> To: Popoola 
> Cc: Comunidad Koha 
> Subject: RE: [Koha] How to return from version 17.05 to 16.05
>
> Yes, I did.
>
> El 7 ago. 2017 2:16 PM, "Popoola"  escribió:
>
> Hello Luis, when you are performing your upgrading did you backup your
>> database? or did you export your bibliographic?.If you did any,you can
>> restore your previous version. But the best practices is to figure
>> out the
>> error you encountered during the upgrade and post it to forum, so that
>> members can shares their experience with you
>> --
>> From: Luis Moises Rojas 
>> Sent: ‎8/‎7/‎2017 16:51
>> To: Comunidad Koha 
>> Subject: [Koha] How to return from version 17.05 to 16.05
>>
>> Hello everybody,
>>
>> We upgrade from 16.05 to 17.05.
>> Now we are having at lot of problems.
>> We can not work at all.
>>
>> Is there is a way to get back?
>> Previous version where everything was ok?
>>
>> 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
>>
>>

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

Re: [Koha] How are authority records connected with biblio records ?

[Katrin]

Hi Dave,

I think for migrations something like this would work:

- Import your authorities. Koha will force 001 to match auth_header.authid.
- Create a file with the auth_header.authid and your old authority 
number if there is one

- Add $9 to your authority controlled fields in your MARC records
- Import bibliographic records

AFAIK auth_header.authid must be the same as 001 in the authority 
record. Koha will enforce this on import, so if your records already 
have an authority id used in your data, you might want to store it in 
035 with a unique prefix to differentiate between IDs.


Hope this makes sense,

Katrin


On 09.08.2017 16:23, David Holoshka wrote:

Hi Micheal,

I originally tried the script link_bibs_to_authorities.pl but there 
were two issues with it:


1.  After running for days it would use up all available memory and 
stop working


2. It does not preserve the links we have today between auths and 
biblios but does its best to connect records based on various pattern 
matching algorithms.


Best Regards,

Dave

On 08/09/2017 02:59 PM, Michael Kuhn wrote:

Hi David


I am migrating several million records from an existing vtls system 
to koha.  We are using mariadb, koha 17.05 (have pulled from master 
yesterday ), elastic search 5.4 and plack on debian systems.  As I 
wanted to preserve all the authority to biblio record links  I wrote 
my own migration script based on the relevant koha source.


Searching in the koha authorities intra will find the authority 
record but usually lists the number of biblio records having the 
auth as zero, but not always.  If I check the biblio index in ES the 
items have the correct auth id in the "an" field.  I can find no 
difference between the biblio records in the ES index that are 
reported as linked to the auth record to the ones that are not.  I 
connect the biblio recs to the authorities in the marc21 structure 
by putting the  koha auth id in field 100 sub field 9 (if it is a 
name auth).  These marc records are now in the new biblio_metadata 
table.


How does koha find the biblio records connected to a paticular auth 
record ?


Is this done dynamically by searching the ES indexes ?

Is this an issue with the zebra database?  Is it still required ?  I 
haven't been loading data into it since we switched to ES.



I don't really know about the differences between Zebra and 
Elasticsearch. Also I don't know how you're exactly massaging your 
data, of course.


However, using Zebra it is necessary to use Perl script 
"link_bibs_to_authorities.pl" to check each bibliographic record in 
the Koha database and attempting to link each of its headings to the 
matching authority record. The script is also able to do a test run.


Also note the system preferences in Koha menu "Administration > 
authorities" as well as "IncludeSeeFromInSearches".


Hope this helps. Someone may correct me if I'm wrong.

Best wishes: Michael


___
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] How to return from version 17.05 to 16.05

[Luis Moises Rojas]

Hello,

Backup database was still 16.05.


On Wed, Aug 9, 2017 at 11:37 AM, Katrin  wrote:

> Hi Luis,
>
> did you use the database that was updated to 17.05 before or a backup
> database that was still 16.05?
>
> koha-upgrade-schema only works 'upwards', it won't be able to downgrade a
> database to the old structure. In 17.05 there was one major change in
> moving the marcxml from biblioitems to a new separate table. Other changes
> would also be problematic.  So using a 17.05 database with 16.05 code WON'T
> WORK.
>
> The init script and how to install it is described on the wiki page:
>
> https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix
>
> If you can't use a database backup from before the attempted update to
> 17.05, I strongly recommend returning ot 17.05 and trying to fix the errors
> you have seen there.
>
> Katrin
>
> On 09.08.2017 16:16, Luis Moises Rojas wrote:
>
> Hello,
>
> Finally we have reinstalled 16.05
> We ran:
> sudo koha-upgrade-schema libraryname
> sudo koha-rebuild-zebra -v -f libraryname
> sudo koha-rebuild-zebra -a -f  libraryname
>
> In sudo koha-upgrade-schema we have severals "Select" errors.
> When you try to find a BOOK it says: No found
> If we search an author says: IN REPOSITORY.
>
> Why?
>
> Maybe is because we have to do this: "You need to fix your data in order
> to get around this and implement the init script"
>
> But where is init script and how to used it?
>
>
> On Mon, Aug 7, 2017 at 5:32 PM, Katrin  wrote:
>
>> Please note, that you will need to use your backup from before updating
>> to 17.05, because you can't undo the changes to the database structure
>> easily.
>>
>> From reading one of your earlier emails - is it possible that you are
>> using MySQL 5.7  instead of MariaDB?
>>
>> https://wiki.koha-community.org/wiki/Koha_on_Debian#Debian_P
>> ackages_on_Koha
>>
>> The problem with returning items will probably remain, as we have
>> implemented a block on returning items when the issue_id already exists in
>> old_issues in 17.05, 16.11, and 16.05. Please see here:
>>
>> https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix
>>
>> You need to fix your data in order to get around this and implement the
>> init script.
>>
>> Hope this helps,
>>
>> Katrin
>>
>>
>> On 07.08.2017 20:50, Luis Moises Rojas wrote:
>>
>>> We are reinstalling previous version 16.05 with 17.05 is was impossible
>>> to
>>> work.
>>> We can not return book.
>>> All books where in Reserver
>>> We can not Catalog.
>>> And much more.
>>>
>>>
>>> On Mon, Aug 7, 2017 at 2:25 PM, Popoola  wrote:
>>>
>>> Did you have koha image of your previous version, i mean your previous
 installation version on your external hard drive or cloud backup?
 --
 From: Luis Moises Rojas 
 Sent: ‎8/‎7/‎2017 19:20
 To: Popoola 
 Cc: Comunidad Koha 
 Subject: RE: [Koha] How to return from version 17.05 to 16.05

 Yes, I did.

 El 7 ago. 2017 2:16 PM, "Popoola"  escribió:

 Hello Luis, when you are performing your upgrading did you backup your
> database? or did you export your bibliographic?.If you did any,you can
> restore your previous version. But the best practices is to figure out
> the
> error you encountered during the upgrade and post it to forum, so that
> members can shares their experience with you
> --
> From: Luis Moises Rojas 
> Sent: ‎8/‎7/‎2017 16:51
> To: Comunidad Koha 
> Subject: [Koha] How to return from version 17.05 to 16.05
>
> Hello everybody,
>
> We upgrade from 16.05 to 17.05.
> Now we are having at lot of problems.
> We can not work at all.
>
> Is there is a way to get back?
> Previous version where everything was ok?
>
> 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
>
>
>>>
>> ___
>> Koha mailing list  http://koha-community.org
>> Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
>>
>
>
>
> --
> *Luis Moisés Rojas P.*
>
>
>


-- 
*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] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[Jonathan Druart]

Just to cross the topics, we already had this discussion earlier:
https://lists.katipo.co.nz/public/koha/2015-July/043138.html
"Proposal to remove the 'Paid support' list"

On Wed, 9 Aug 2017 at 12:17 Mark Tompsett  wrote:

> Greetings,
>
> Nathan A. Curulla suggested:
> > Maybe we should change the listing to “contributing support companies” or
> > something like that.
>
> While I think that is a good idea, and then companies without community
> participation get removed, the problem still remains: people don't read.
> We've put a nice disclaimer that this is not an official list and has no
> official seal of approval meaning to the list, and yet people still use it
> that way. It is impossible to educate people who refuse to read, even
> though
> the preamble write up is a rather good explanation of how to look for a
> Koha
> support provider. As such, the only reasonable course of action is to
> delete
> the list, otherwise it will continue to be used that way, no matter what we
> put on the page(s).
>
>
> Owen Leonard wrote:
> > It would be a duplicate listing ... and should be rejected.
>
> Who determines it is a duplicate listing? Because last time I looked some
> other entries looked like duplicates to me, much like OpenLX/BBB. And
> cleaning up duplicates is a pain. Yet another reason to just delete the
> list
> already.
>
> GPML,
> Mark Tompsett
>
> ___
> 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] How to return from version 17.05 to 16.05

[Katrin]

Hi Luis,

did you use the database that was updated to 17.05 before or a backup 
database that was still 16.05?


koha-upgrade-schema only works 'upwards', it won't be able to downgrade 
a database to the old structure. In 17.05 there was one major change in 
moving the marcxml from biblioitems to a new separate table. Other 
changes would also be problematic.  So using a 17.05 database with 16.05 
code WON'T WORK.


The init script and how to install it is described on the wiki page:

https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix 



If you can't use a database backup from before the attempted update to 
17.05, I strongly recommend returning ot 17.05 and trying to fix the 
errors you have seen there.


Katrin


On 09.08.2017 16:16, Luis Moises Rojas wrote:

Hello,

Finally we have reinstalled 16.05
We ran:
sudo koha-upgrade-schema libraryname
sudo koha-rebuild-zebra -v -f libraryname
sudo koha-rebuild-zebra -a -f  libraryname

In sudo koha-upgrade-schema we have severals "Select" errors.
When you try to find a BOOK it says: No found
If we search an author says: IN REPOSITORY.

Why?

Maybe is because we have to do this: "You need to fix your data in 
order to get around this and implement the init script"


But where is init script and how to used it?


On Mon, Aug 7, 2017 at 5:32 PM, Katrin > wrote:


Please note, that you will need to use your backup from before
updating to 17.05, because you can't undo the changes to the
database structure easily.

From reading one of your earlier emails - is it possible that you
are using MySQL 5.7  instead of MariaDB?

https://wiki.koha-community.org/wiki/Koha_on_Debian#Debian_Packages_on_Koha



The problem with returning items will probably remain, as we have
implemented a block on returning items when the issue_id already
exists in old_issues in 17.05, 16.11, and 16.05. Please see here:

https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix


You need to fix your data in order to get around this and
implement the init script.

Hope this helps,

Katrin


On 07.08.2017 20:50, Luis Moises Rojas wrote:

We are reinstalling previous version 16.05 with 17.05 is was
impossible to
work.
We can not return book.
All books where in Reserver
We can not Catalog.
And much more.


On Mon, Aug 7, 2017 at 2:25 PM, Popoola
> wrote:

Did you have koha image of your previous version, i mean
your previous
installation version on your external hard drive or cloud
backup?
--
From: Luis Moises Rojas >
Sent: ‎8/‎7/‎2017 19:20
To: Popoola >
Cc: Comunidad Koha >
Subject: RE: [Koha] How to return from version 17.05 to 16.05

Yes, I did.

El 7 ago. 2017 2:16 PM, "Popoola" > escribió:

Hello Luis, when you are performing your upgrading did
you backup your
database? or did you export your bibliographic?.If you
did any,you can
restore your previous version. But the best practices
is to figure out the
error you encountered during the upgrade and post it
to forum, so that
members can shares their experience with you
--
From: Luis Moises Rojas >
Sent: ‎8/‎7/‎2017 16:51
To: Comunidad Koha >
Subject: [Koha] How to return from version 17.05 to 16.05

Hello everybody,

We upgrade from 16.05 to 17.05.
Now we are having at lot of problems.
We can not work at all.

Is there is a way to get back?
Previous version where everything was ok?

Thanks

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

Re: [Koha] Patron Club feature

[Tomas Cohen Arazi]

Please check this bug I filed:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19067

Regards

El mié., 9 ago. 2017 a las 12:13, Mark Alexander ()
escribió:

> Excerpts from Krishna K's message of 2017-07-30 06:02:15 +:
> > 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. We dont seem to be having the clubs.pl file. What should we do ?
> > Appreciate your inputs.
>
> [Apologies if this is a dupe message; my previous reply seems to
> have been rejected by the list server.]
>
> I think there may be problem with the koha-common package.  I don't
> see clubs.pl in there:
>
>   % dpkg -L koha-common | egrep clubs
>   /usr/share/koha/opac/cgi-bin/opac/clubs
>   /usr/share/koha/opac/cgi-bin/opac/clubs/clubs-tab.pl
>   /usr/share/koha/opac/cgi-bin/opac/clubs/enroll.pl
>   /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/clubs
>   /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/clubs/
> clubs-tab.tt
>   /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/clubs/
> enroll.tt
>   /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs
>   /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/
> templates-add-modify.tt
>   /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/
> clubs.tt
>   /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/
> clubs-add-modify.tt
>   /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/
> patron-enroll.tt
>   /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/
> patron-clubs-tab.tt
>   /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/
> club-enrollments.tt
>
> But I do see clubs.pl in the git repository:
>
>   % pwd
>   /home/marka/shared/tools/kohaclone
>   % ls -laF clubs
>   total 36
>   drwxr-xr-x  2 marka marka 4096 Jul 19 16:00 ./
>   drwxr-xr-x 47 marka marka 4096 Aug  9 11:07 ../
>   -rwxr-xr-x  1 marka marka 1267 Jul 19 16:00 club-enrollments.pl*
>   -rwxr-xr-x  1 marka marka 3575 Jul 19 16:00 clubs-add-modify.pl*
>   -rwxr-xr-x  1 marka marka 1740 Jul 19 16:00 clubs.pl*
>   -rwxr-xr-x  1 marka marka 1504 Jul 19 16:00 patron-clubs-tab.pl*
>   -rwxr-xr-x  1 marka marka 1358 Jul 19 16:00 patron-enroll.pl*
>   -rwxr-xr-x  1 marka marka 5524 Jul 19 16:00 templates-add-modify.pl*
> ___
> 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

[Koha] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[Mark Tompsett]

Greetings,

Nathan A. Curulla suggested:
> Maybe we should change the listing to “contributing support companies” or 
> something like that.

While I think that is a good idea, and then companies without community 
participation get removed, the problem still remains: people don't read. 
We've put a nice disclaimer that this is not an official list and has no 
official seal of approval meaning to the list, and yet people still use it 
that way. It is impossible to educate people who refuse to read, even though 
the preamble write up is a rather good explanation of how to look for a Koha 
support provider. As such, the only reasonable course of action is to delete 
the list, otherwise it will continue to be used that way, no matter what we 
put on the page(s).


Owen Leonard wrote:
> It would be a duplicate listing ... and should be rejected.

Who determines it is a duplicate listing? Because last time I looked some 
other entries looked like duplicates to me, much like OpenLX/BBB. And 
cleaning up duplicates is a pain. Yet another reason to just delete the list 
already.

GPML,
Mark Tompsett

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

Re: [Koha] How to return from version 17.05 to 16.05

[Luis Moises Rojas]

Hello,
This is the error: DBD::mysql::st fetchrow_hashref failed: fetch() without
execute() [for Statement
  "SELECT biblioitemnumber, marcxml
FROM biblioitems WHERE biblionumber=? " with
  ParamValues:
0='27382'] at /usr/share/koha/lib/C4/Biblio.pm line 1327.

Maybe is because the database is in one version and koha in other?

On Wed, Aug 9, 2017 at 10:16 AM, Luis Moises Rojas 
wrote:

> Hello,
>
> Finally we have reinstalled 16.05
> We ran:
> sudo koha-upgrade-schema libraryname
> sudo koha-rebuild-zebra -v -f libraryname
> sudo koha-rebuild-zebra -a -f  libraryname
>
> In sudo koha-upgrade-schema we have severals "Select" errors.
> When you try to find a BOOK it says: No found
> If we search an author says: IN REPOSITORY.
>
> Why?
>
> Maybe is because we have to do this: "You need to fix your data in order
> to get around this and implement the init script"
>
> But where is init script and how to used it?
>
>
> On Mon, Aug 7, 2017 at 5:32 PM, Katrin  wrote:
>
>> Please note, that you will need to use your backup from before updating
>> to 17.05, because you can't undo the changes to the database structure
>> easily.
>>
>> From reading one of your earlier emails - is it possible that you are
>> using MySQL 5.7  instead of MariaDB?
>>
>> https://wiki.koha-community.org/wiki/Koha_on_Debian#Debian_P
>> ackages_on_Koha
>>
>> The problem with returning items will probably remain, as we have
>> implemented a block on returning items when the issue_id already exists in
>> old_issues in 17.05, 16.11, and 16.05. Please see here:
>>
>> https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix
>>
>> You need to fix your data in order to get around this and implement the
>> init script.
>>
>> Hope this helps,
>>
>> Katrin
>>
>>
>> On 07.08.2017 20:50, Luis Moises Rojas wrote:
>>
>>> We are reinstalling previous version 16.05 with 17.05 is was impossible
>>> to
>>> work.
>>> We can not return book.
>>> All books where in Reserver
>>> We can not Catalog.
>>> And much more.
>>>
>>>
>>> On Mon, Aug 7, 2017 at 2:25 PM, Popoola  wrote:
>>>
>>> Did you have koha image of your previous version, i mean your previous
 installation version on your external hard drive or cloud backup?
 --
 From: Luis Moises Rojas 
 Sent: ‎8/‎7/‎2017 19:20
 To: Popoola 
 Cc: Comunidad Koha 
 Subject: RE: [Koha] How to return from version 17.05 to 16.05

 Yes, I did.

 El 7 ago. 2017 2:16 PM, "Popoola"  escribió:

 Hello Luis, when you are performing your upgrading did you backup your
> database? or did you export your bibliographic?.If you did any,you can
> restore your previous version. But the best practices is to figure out
> the
> error you encountered during the upgrade and post it to forum, so that
> members can shares their experience with you
> --
> From: Luis Moises Rojas 
> Sent: ‎8/‎7/‎2017 16:51
> To: Comunidad Koha 
> Subject: [Koha] How to return from version 17.05 to 16.05
>
> Hello everybody,
>
> We upgrade from 16.05 to 17.05.
> Now we are having at lot of problems.
> We can not work at all.
>
> Is there is a way to get back?
> Previous version where everything was ok?
>
> 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
>
>
>>>
>> ___
>> Koha mailing list  http://koha-community.org
>> Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
>>
>
>
>
> --
> *Luis Moisés Rojas P.*
>
>


-- 
*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] Patron Club feature

[Mark Alexander]

Excerpts from Krishna K's message of 2017-07-30 06:02:15 +:
> 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. We dont seem to be having the clubs.pl file. What should we do ?
> Appreciate your inputs.

[Apologies if this is a dupe message; my previous reply seems to
have been rejected by the list server.]

I think there may be problem with the koha-common package.  I don't
see clubs.pl in there:

  % dpkg -L koha-common | egrep clubs
  /usr/share/koha/opac/cgi-bin/opac/clubs
  /usr/share/koha/opac/cgi-bin/opac/clubs/clubs-tab.pl
  /usr/share/koha/opac/cgi-bin/opac/clubs/enroll.pl
  /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/clubs
  /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/clubs/clubs-tab.tt
  /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/clubs/enroll.tt
  /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs
  
/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/templates-add-modify.tt
  /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/clubs.tt
  
/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/clubs-add-modify.tt
  
/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/patron-enroll.tt
  
/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/patron-clubs-tab.tt
  
/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/clubs/club-enrollments.tt

But I do see clubs.pl in the git repository:

  % pwd
  /home/marka/shared/tools/kohaclone
  % ls -laF clubs
  total 36
  drwxr-xr-x  2 marka marka 4096 Jul 19 16:00 ./
  drwxr-xr-x 47 marka marka 4096 Aug  9 11:07 ../
  -rwxr-xr-x  1 marka marka 1267 Jul 19 16:00 club-enrollments.pl*
  -rwxr-xr-x  1 marka marka 3575 Jul 19 16:00 clubs-add-modify.pl*
  -rwxr-xr-x  1 marka marka 1740 Jul 19 16:00 clubs.pl*
  -rwxr-xr-x  1 marka marka 1504 Jul 19 16:00 patron-clubs-tab.pl*
  -rwxr-xr-x  1 marka marka 1358 Jul 19 16:00 patron-enroll.pl*
  -rwxr-xr-x  1 marka marka 5524 Jul 19 16:00 templates-add-modify.pl*
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How are authority records connected with biblio records ?

[Michael Kuhn]

Hi David


I originally tried the script link_bibs_to_authorities.pl but there were 
two issues with it:


1.  After running for days it would use up all available memory and stop 
working



In my case I used this script for a maximum of around 200'000 
bibliographic records. I see in your original e-mail you wrote of 
"several million records"...


Did you see the script offers the following options? Maybe using them 
can change the observed behaviour:


--auth-limit=S ... Only process those headings which match an authority 
record that matches the user-specified WHERE clause.


--bib-limit=S ... Only process those bib records that match the 
user-specified WHERE clause.


--commit=N ... Commit the results to the database after every N records 
are processed.



2. It does not preserve the links we have today between auths and 
biblios but does its best to connect records based on various pattern 
matching algorithms.


Unfortunately the manpage of this script (and other scripts...) are not 
very explicit about what they are really doing. Thanks for pointing this 
out!


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] How are authority records connected with biblio records ?

[David Holoshka]

Hi ,

Thanks for your answer Chris.  Is there some kind of plan / road map to 
get it working or should I just go ahead and try to fix it in a side 
branch of my own ?


Is anyone coordinating the work for this ?

Best Regards,

Dave


On 08/03/2017 10:42 PM, Chris Cormack wrote:

* David Holoshka (david.holos...@ub.lu.se) wrote:

Hi,

I am migrating several million records from an existing vtls system 
to koha.  We are using mariadb, koha 17.05 (have pulled from master 
yesterday ), elastic search 5.4 and plack on debian systems.  As I 
wanted to preserve all the authority to biblio record links  I wrote 
my own migration script based on the relevant koha source.


Hi David

Did you really mean master, or did you pull from the 17.05.x branch?
If you meant master you aren't running 17.05 but the unreleased code
that will be 17.11.0 eventually.

The ES authority support is still a work in progress.

Chris



Searching in the koha authorities intra will find the authority 
record but usually lists the number of biblio records having the auth 
as zero, but not always.  If I check the biblio index in ES the items 
have the correct auth id in the "an" field.  I can find no difference 
between the biblio records in the ES index that are reported as 
linked to the auth record to the ones that are not.  I connect the 
biblio recs to the authorities in the marc21 structure by putting 
the  koha auth id in field 100 sub field 9 (if it is a name auth).  
These marc records are now in the new biblio_metadata table.



How does koha find the biblio records connected to a paticular auth 
record ?


Is this done dynamically by searching the ES indexes ?


Is this an issue with the zebra database?  Is it still required ?  I 
haven't been loading data into it since we switched to ES.


Best Regards,

Dave

___
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

[Koha] Koha giving frequent software errors

[ILOBWeb]

Hello everyone,

We are using Koha for our resource centre and we are getting frequent software 
errors while working on it. Errors are like -

Error 1 :
Software error:

Wrong CSRF token at /usr/share/koha/intranet/cgi-bin/members/memberentry.pl 
line 291.

For help, please send mail to the webmaster ([no address 
given]), giving this error message and the time 
and date of the error.
Error 2:

This site can't be reached

The connection was reset.

Try:

  *   Checking the connection
  *   Checking the proxy and the firewall
  *   Running Windows Network Diagnostics
ERR_CONNECTION_RESET


Today, I got error when was working on Koha and to check something I clicked on 
'Help'. I checked the Intranet error logs file and a snapshot of the same is 
below. The highlighted error is the error which was logged today when I clicked 
'Help'.

[Mon Aug 07 15:24:18.684124 2017] [cgi:error] [pid 46288] [client 
72.141.68.213:49598] AH01215: [Mon Aug  7 15:24:18 2017] manage-marc-import.pl: 
Can't call method "results" on an undefined value at 
/usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl line 347.: 
/usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl, referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/tools/manage-marc-import.pl
[Mon Aug 07 17:01:11.388667 2017] [cgi:error] [pid 46753] [client 
72.141.68.213:51047] AH01215: [Mon Aug  7 17:01:11 2017] additem.pl: 
DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.  
SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/usr/share/koha/lib/Koha/Objects.pm line 83: 
/usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl, referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/cataloguing/additem.pl?op=edititem=55=60=
[Mon Aug 07 17:01:42.857633 2017] [cgi:error] [pid 46763] [client 
72.141.68.213:51057] AH01215: [Mon Aug  7 17:01:42 2017] additem.pl: 
DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.  
SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/usr/share/koha/lib/Koha/Objects.pm line 83: 
/usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl, referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/cataloguing/additem.pl?op=edititem=55=59=
[Tue Aug 08 03:39:01.311411 2017] [cgi:error] [pid 52495] [client 
72.141.68.213:49809] AH01215: [Tue Aug  8 03:39:01 2017] detail.pl: Use of 
uninitialized value in concatenation (.) or string at 
/usr/share/koha/lib/C4/Biblio.pm line 1410.: 
/usr/share/koha/intranet/cgi-bin/catalogue/detail.pl, referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=1
[Tue Aug 08 03:39:50.095831 2017] [cgi:error] [pid 52517] [client 
72.141.68.213:49813] AH01215: [Tue Aug  8 03:39:50 2017] detail.pl: Use of 
uninitialized value in concatenation (.) or string at 
/usr/share/koha/lib/C4/Biblio.pm line 1410.: 
/usr/share/koha/intranet/cgi-bin/catalogue/detail.pl, referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/tools/upload-cover-image.pl
[Tue Aug 08 18:53:48.745776 2017] [cgi:error] [pid 63052] [client 
137.122.64.13:16643] AH01215: [Tue Aug  8 18:53:48 2017] detail.pl: Use of 
uninitialized value in concatenation (.) or string at 
/usr/share/koha/lib/C4/Biblio.pm line 1410.: 
/usr/share/koha/intranet/cgi-bin/catalogue/detail.pl, referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/tools/manage-marc-import.pl?import_batch_id=1
[Tue Aug 08 18:57:20.166232 2017] [cgi:error] [pid 63135] [client 
137.122.64.13:16842] AH01215: [Tue Aug  8 18:57:20 2017] detail.pl: Use of 
uninitialized value in concatenation (.) or string at 
/usr/share/koha/lib/C4/Biblio.pm line 1410.: 
/usr/share/koha/intranet/cgi-bin/catalogue/detail.pl, referer: 
http://ilob-olbi-intra.juliencouturecentre.ca:/cgi-bin/koha/tools/upload-cover-image.pl
[Tue Aug 08 19:12:33.214782 2017] [cgi:error] [pid 63456] [client 
8.28.16.254:2289] AH01215: [Tue Aug  8 19:12:33 2017] batch_records_ajax.pl: 
Use of uninitialized value in array element at 
/usr/share/koha/intranet/cgi-bin/tools/batch_records_ajax.pl line 50.: 
/usr/share/koha/intranet/cgi-bin/tools/batch_records_ajax.pl
[Tue Aug 08 19:12:33.215002 2017] [cgi:error] [pid 63456] [client 
8.28.16.254:2289] AH01215: [Tue Aug  8 19:12:33 2017] batch_records_ajax.pl: 
Use of uninitialized value $results_per_page in numeric eq (==) at 
/usr/share/koha/intranet/cgi-bin/tools/batch_records_ajax.pl line 53.: 
/usr/share/koha/intranet/cgi-bin/tools/batch_records_ajax.pl
[Tue Aug 08 19:46:24.299851 2017] [cgi:error] [pid 64346] [client 
137.122.64.13:16448] AH01215: [Tue Aug  8 19:46:24 2017] additem.pl: 
DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.  
SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/usr/share/koha/lib/Koha/Objects.pm line 

Re: [Koha] How are authority records connected with biblio records ?

[David Holoshka]

Hi Micheal,

I originally tried the script link_bibs_to_authorities.pl but there were 
two issues with it:


1.  After running for days it would use up all available memory and stop 
working


2. It does not preserve the links we have today between auths and 
biblios but does its best to connect records based on various pattern 
matching algorithms.


Best Regards,

Dave

On 08/09/2017 02:59 PM, Michael Kuhn wrote:

Hi David


I am migrating several million records from an existing vtls system 
to koha.  We are using mariadb, koha 17.05 (have pulled from master 
yesterday ), elastic search 5.4 and plack on debian systems.  As I 
wanted to preserve all the authority to biblio record links  I wrote 
my own migration script based on the relevant koha source.


Searching in the koha authorities intra will find the authority 
record but usually lists the number of biblio records having the auth 
as zero, but not always.  If I check the biblio index in ES the items 
have the correct auth id in the "an" field.  I can find no difference 
between the biblio records in the ES index that are reported as 
linked to the auth record to the ones that are not.  I connect the 
biblio recs to the authorities in the marc21 structure by putting 
the  koha auth id in field 100 sub field 9 (if it is a name auth).  
These marc records are now in the new biblio_metadata table.


How does koha find the biblio records connected to a paticular auth 
record ?


Is this done dynamically by searching the ES indexes ?

Is this an issue with the zebra database?  Is it still required ?  I 
haven't been loading data into it since we switched to ES.



I don't really know about the differences between Zebra and 
Elasticsearch. Also I don't know how you're exactly massaging your 
data, of course.


However, using Zebra it is necessary to use Perl script 
"link_bibs_to_authorities.pl" to check each bibliographic record in 
the Koha database and attempting to link each of its headings to the 
matching authority record. The script is also able to do a test run.


Also note the system preferences in Koha menu "Administration > 
authorities" as well as "IncludeSeeFromInSearches".


Hope this helps. Someone may correct me if I'm wrong.

Best wishes: Michael


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

Re: [Koha] How to return from version 17.05 to 16.05

[Luis Moises Rojas]

Hello,

Finally we have reinstalled 16.05
We ran:
sudo koha-upgrade-schema libraryname
sudo koha-rebuild-zebra -v -f libraryname
sudo koha-rebuild-zebra -a -f  libraryname

In sudo koha-upgrade-schema we have severals "Select" errors.
When you try to find a BOOK it says: No found
If we search an author says: IN REPOSITORY.

Why?

Maybe is because we have to do this: "You need to fix your data in order to
get around this and implement the init script"

But where is init script and how to used it?


On Mon, Aug 7, 2017 at 5:32 PM, Katrin  wrote:

> Please note, that you will need to use your backup from before updating to
> 17.05, because you can't undo the changes to the database structure easily.
>
> From reading one of your earlier emails - is it possible that you are
> using MySQL 5.7  instead of MariaDB?
>
> https://wiki.koha-community.org/wiki/Koha_on_Debian#Debian_
> Packages_on_Koha
>
> The problem with returning items will probably remain, as we have
> implemented a block on returning items when the issue_id already exists in
> old_issues in 17.05, 16.11, and 16.05. Please see here:
>
> https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix
>
> You need to fix your data in order to get around this and implement the
> init script.
>
> Hope this helps,
>
> Katrin
>
>
> On 07.08.2017 20:50, Luis Moises Rojas wrote:
>
>> We are reinstalling previous version 16.05 with 17.05 is was impossible to
>> work.
>> We can not return book.
>> All books where in Reserver
>> We can not Catalog.
>> And much more.
>>
>>
>> On Mon, Aug 7, 2017 at 2:25 PM, Popoola  wrote:
>>
>> Did you have koha image of your previous version, i mean your previous
>>> installation version on your external hard drive or cloud backup?
>>> --
>>> From: Luis Moises Rojas 
>>> Sent: ‎8/‎7/‎2017 19:20
>>> To: Popoola 
>>> Cc: Comunidad Koha 
>>> Subject: RE: [Koha] How to return from version 17.05 to 16.05
>>>
>>> Yes, I did.
>>>
>>> El 7 ago. 2017 2:16 PM, "Popoola"  escribió:
>>>
>>> Hello Luis, when you are performing your upgrading did you backup your
 database? or did you export your bibliographic?.If you did any,you can
 restore your previous version. But the best practices is to figure out
 the
 error you encountered during the upgrade and post it to forum, so that
 members can shares their experience with you
 --
 From: Luis Moises Rojas 
 Sent: ‎8/‎7/‎2017 16:51
 To: Comunidad Koha 
 Subject: [Koha] How to return from version 17.05 to 16.05

 Hello everybody,

 We upgrade from 16.05 to 17.05.
 Now we are having at lot of problems.
 We can not work at all.

 Is there is a way to get back?
 Previous version where everything was ok?

 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


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



-- 
*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] Possibilities and Help in Translation

[Balaji Ravichandran]

Hi Jonathan,
I have started Translating Koha to தமிழ்(Tamil) for the version 17.05.
There is also a version of Koha 3.22 and many other versions. Can you
please provide suggestions on how to select versions for translating? Some
are marked as obsolete. Kindly help is selecting versions.

On 3 August 2017 at 19:51, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> Hi Balaji,
>
> Welcome! :)
>
> This language already exists on our translation server (
> http://translate.koha-community.org/ta/).
> You should take a look at
> https://wiki.koha-community.org/wiki/Translating_Koha to know how to
> translate Koha.
> I am not a translator so I cannot help you more. The language is only 1%
> translated, you will have a lot of work to translate it completely. Good
> luck! :)
>
> Regards,
> Jonathan
>
>
> On Thu, 3 Aug 2017 at 09:20 Balaji Ravichandran 
> wrote:
>
> > Hi,
> > I am new to Koha Community. I have done 4 Koha Setup across TamilNadu,
> > India. Our Koha Community here has decided to translate Koha into our
> > native language.
> >
> >- Action - Translation
> >- Language - தமிழ் (Tamil)
> >
> > Is Translation possible in Koha? If so, suggest some methods or getting
> > started docs for it to be useful to the Community here. Also suggest what
> > needs to be taken care of and important measures to be taken.
> >
> > Waiting for feedback from the Community :-)
> >
> > --
> > Best Regards,
> > Balaji Ravichandran
> > ___
> > 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
>



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

Re: [Koha] Spam from BestBookBuddies (OpenLX)

[Owen Leonard]

> Maybe we should change the listing to “contributing support companies” or 
> something like that.

I think that's an interesting idea, but the larger problem remains:
There will always be contention around how the support companies list
is made, no matter what. I think we've done pretty well with the very
basic requirements we've set for for listing. I'm inclined to either
stick with it or, if it's agreed that the current system is too
contentious, eliminate it altogether.

The immediate question, about a listing for BestBookBuddies, is best
answered as it already was: It would be a duplicate listing of OpenLX
and should be rejected.

 -- Owen

-- 
Web Developer
Athens County Public Libraries
http://www.myacpl.org
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How are authority records connected with biblio records ?

[Michael Kuhn]

Hi David


I am migrating several million records from an existing vtls system to 
koha.  We are using mariadb, koha 17.05 (have pulled from master 
yesterday ), elastic search 5.4 and plack on debian systems.  As I 
wanted to preserve all the authority to biblio record links  I wrote my 
own migration script based on the relevant koha source.


Searching in the koha authorities intra will find the authority record 
but usually lists the number of biblio records having the auth as zero, 
but not always.  If I check the biblio index in ES the items have the 
correct auth id in the "an" field.  I can find no difference between the 
biblio records in the ES index that are reported as linked to the auth 
record to the ones that are not.  I connect the biblio recs to the 
authorities in the marc21 structure by putting the  koha auth id in 
field 100 sub field 9 (if it is a name auth).  These marc records are 
now in the new biblio_metadata table.


How does koha find the biblio records connected to a paticular auth 
record ?


Is this done dynamically by searching the ES indexes ?

Is this an issue with the zebra database?  Is it still required ?  I 
haven't been loading data into it since we switched to ES.



I don't really know about the differences between Zebra and 
Elasticsearch. Also I don't know how you're exactly massaging your data, 
of course.


However, using Zebra it is necessary to use Perl script 
"link_bibs_to_authorities.pl" to check each bibliographic record in the 
Koha database and attempting to link each of its headings to the 
matching authority record. The script is also able to do a test run.


Also note the system preferences in Koha menu "Administration > 
authorities" as well as "IncludeSeeFromInSearches".


Hope this helps. Someone may correct me if I'm wrong.

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] Spam from BestBookBuddies (OpenLX)

[Nathan Curulla]

Greetings all,

I personally agree that work needs to be done on this list. Maybe we should 
change the listing to “contributing support companies” or something like that. 
If you want to get listed in the Koha Yellow Pages, pony up some time on bug 
testing, dev submittals etc.. Invest in the community and you can put your 
company on the community site. We can even put up a disclaimer stating that 
there are many more companies out there, these are just the ones that give back 
in a significant way… This will encourage participation and reward those who 
already participate (which includes the vast majority of those already on the 
list). 

In my humble opinion, giving Koha services away for free in order to get a foot 
in the door to sell your primary offering (such as books) does not count as a 
contribution to the community. In fact, if the system is not properly supported 
because it is used as a peripheral marketing technique, it could end up hurting 
the community, as poor support translates into poor software in the eyes of the 
users. Not saying this is the case here, just some hypothetical contemplation :)


> Nathan A. Curulla
> Owner, CRO
> ByWater Solutions



> --
> 
> Message: 1
> Date: Wed, 9 Aug 2017 10:21:44 +1000
> From: Bob Birchall 
> To: koha@lists.katipo.co.nz
> Subject: Re: [Koha] Spam from BestBookBuddies (OpenLX)
> Message-ID: <835ba28d-0b9e-cba3-c6e4-15285e78a...@calyx.net.au>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> There we go again - 'official list' as if it has some status other than 
> as a yellow pages directory. I suspect the noise from the sub-continent 
> particularly will increase, whilst very little comes back to the 
> project. I think we should just get rid of that page from the website.
> My 2 cents,
> Bob Birchall
> Calyx
> 
> 
> *

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

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

[Michael Kuhn]

Hi

On 3 August 2017 I wrote:

 # # #

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" (MARC 150 $a) has a "see also" record 
"Lesekultur" (MARC 450 $a).


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?

 # # #

Unfortunately I haven't found the solution until now. I only have found 
out the following:


1. No system preferences were changed after the update. This means the 
following system preferences haven't been changed during or since the 
update:


* IncludeSeeFromInSearches: Include
* CatalogModuleRelink: Do not
* KinkerKeepStale: Do not
* Linker module: Default
* LinkerOptions: (empty)
* LinkerRelink: Do

2. In Koha 3.20.4 the search for "see from (non-preferred form) 
headings" showed all the expected results. After the update to Koha 
17.05 these searches do find nothing anymore. (Even though we relinked 
all authorities and also have rebuilt the Zebra index for the authorities).


3. In my own Koha 17.05.1 demo installation with the same system 
preferences set I entered a new authority record with MARC 150 $a 
"Buchkultur" and MARC 450 $a "Lesekultur" (as existing in the productive 
system). Then I added this authority record into the bibliographic 
record MARC 650 $a. Neither in the productive system nor in my demo 
installation the search for "Lesekultur" will show a result.


4. Can anyone positively CONFIRM that in his installation of Koha 
17.05.1 the search for "see from (non-preferred form) headings" does 
show results?


I will appreciate any kind of hint regarding this problem.

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] Confusion over "item type"

[Marcel de Rooy]

Chris,


You should look for the pref item-level_itypes and its documentation.


Marcel



Van: Koha  namens Chris Brown 

Verzonden: woensdag 9 augustus 2017 13:12
Aan: koha@lists.katipo.co.nz
Onderwerp: [Koha] Confusion over "item type"

Hello,

MARC records 942$c and 952$y both appear to specify an "item type". They
appear to be mapped to koha fields biblio.itemtype and items.itype
respectively. Please could someone explain to me the difference between
them? In particular when I define a circulation rule for a specific item
type, which one does it use?

I am using Koha 17.05

Thanks!

Chris Brown (still a newbie, but getting there ...)
___
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

[Koha] Confusion over "item type"

[Chris Brown]

Hello,

MARC records 942$c and 952$y both appear to specify an "item type". They
appear to be mapped to koha fields biblio.itemtype and items.itype
respectively. Please could someone explain to me the difference between
them? In particular when I define a circulation rule for a specific item
type, which one does it use?

I am using Koha 17.05

Thanks!

Chris Brown (still a newbie, but getting there ...)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Unknown column 'metadata' in 'field list'

[Shivendra]

Dear Vimal,

Please try with this query

SELECT biblio.biblionumber, biblio.author, biblio.title,
biblioitems.editionstatement, biblioitems.publishercode,
SUBSTRING(biblioitems.marcxml, LOCATE('',
   biblioitems.marcxml, LOCATE('', biblioitems.marcxml, LOCATE('',
   biblioitems.marcxml, LOCATE('',
biblioitems.marcxml,
   LOCATE('https://www.researchgate.net/profile/Shivendra_Singh3/contributions

On 9 August 2017 at 10:36, Vimal Kumar V.  wrote:

> Dear Friends,
> I am trying to generate a book list with keywords from 650$a using the
> following SQL query,
>
> SELECT ExtractValue( metadata,
> '//datafield[@tag="650"]/subfield[@code="a"]' ) AS Keyword, items.barcode,
> items.dateaccessioned, items.itemcallnumber, biblio.author, biblio.title,
> biblioitems.pages, biblioitems.publishercode, biblioitems.place,
> biblio.copyrightdate
> FROM items
> LEFT JOIN biblioitems ON
> (items.biblioitemnumber=biblioitems.biblioitemnumber)
> LEFT JOIN biblio ON (biblioitems.biblionumber=biblio.biblionumber)
> ORDER BY LPAD(items.barcode,40,' ') ASC
>
> After running the report, I got the following error message,
>
> The database returned the following error:
> Unknown column 'metadata' in 'field list'
> Please check the log for further details.
>
> Please review the SQL query and help me to solve the problem.
>
>
> Regards,
> --
> Vimal Kumar V.
> Librarian
> School of Indian Legal Thought
> Mahatma Gandhi University
> Kottayam, Kerala
> Web: http://www.vimalkumar.info
> Blogs: http://linuxhalwa.blogspot.com http://kohageek.blogspot.in
> http://dspacegeek.blogspot.in
> http://moovandan.blogspot.in  
> 
> ---
> "I forget what I was taught. I only remember what I have learnt"
> -Patrick White
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>



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