Re: [Koha] Maraming salamat from KohaCon2017 organizers

2017-06-27 Thread schnydszch 
Dear all, I already have the numbers of registered participants for
KohaCon2017 and I am happy to inform you that we had a total 188
participants during the last KohaCon both for the Main Conference and the
hackfest (we had people attending only the Main Conference and some only
attending the hackfest). We had attendees coming from Malaysia, France,
Australia, U.S.A., Spain, Pakistan, Bhutan and Turkey. Again, Mabuhay at
Maraming Maraming Salamat!



--
View this message in context: 
http://koha.1045719.n5.nabble.com/Maraming-salamat-from-KohaCon2017-organizers-tp5938518p5938669.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Fwd: Unable to reindex after massive upgrade

2017-06-27 Thread Tim Young 

Great!  Thanks.  & Thanks for the sql.  Worked fine.

- Tim


On 6/27/2017 12:55 PM, Tomas Cohen Arazi wrote:

Tim, the authorised_values_branches table is not related.

The problem is that there are fields in your record(s) that are 
expected to contain a branchcode. And they don't. That's why 
Koha::Libraries->find() is returning an undefined value (undef in Perl).


When you removed the FK constraint, you did hide the basic problem of 
inconsistency.


I suggest that you find your only library's branchcode and make sure 
your items all have homebranch and holdingbranch set to that. Then 
reindex. You should do it like this:


# Enter to mysql
$ sudo koha-mysql lib
> UPDATE items SET homebranch='LIB', holdingbranch='LIB';
> \q
$ sudo koha-rebuild-zebra -f -a -b -v lib

Note: replace 'lib' for your instance name, and 'LIB' for your 
library's branchcode.


Regards.


El mar., 27 jun. 2017 a las 13:59, Tim Young (>) escribió:


Awesome. Thanks.  I may be able to figure it out (I am pretty good at
poking and prodding, and finally figuring it out).  I believe we only
have one branch, so I should be able to simply replace everything
in the
sql to match the correct branch... (Yikes! Branchcode is used all over
the place!)

BUT, I am a sysadmin, not a Koha admin.  This looks like it might be
easier to fix through the web interface... So excuse the dumb
questions.  :)

That particular error seems to stem from something be authorized by
branches.  My "authorised_values_branches" table is empty. Should
I set
up an authorized branch or something somewhere?

We do have a branch configured (I can see it in the branches table)...

The code seems to be looking at
Koha::Libraries->find($value)->branchname;

and (I have "value" being undefined, or defined improperly. But I do
not see a libraries table...)

But, at the same time:
$tagslib->{$tag}->{$subfield}->{'authorised_value'} eq
"branches".  So I
somewhere seem to be saying to authorize by branch, and I do not have
any authorized branches (or the authorised_values_branches is
empty)...

Is there a simple web area I should check out before I jump into the
mysql and make changes that might not be supported?

 - Tim


On 6/27/2017 9:26 AM, Tomas Cohen Arazi wrote:
> You need to fix your data, so fields linked to branch codes actually
> contain valid branchcodes. The band aid will work, but I think you
> need to fix your data for good.
>
> Koha got stricter regarding the data quality/completeness. This
> particular case could be saved by some tweak like the one you
propose.
> It is maybe worth filling a bug, because the previous behaviour
worked
> more gracefuly.
>

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

--
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F


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

Re: [Koha] Display output is not in order

2017-06-27 Thread Tomas Cohen Arazi 
Luis, my first uncommented line on zebra-biblios-dom.cfg is

profilePath:/etc/koha/sites/:/etc/koha/zebradb/biblios/etc:/etc/koha/zebradb/etc:/etc/koha/zebradb/marc_defs/marc21/biblios:/etc/koha/zebradb/lang_defs/es:/etc/koha/zebradb/xsl

Compare it.


El mar., 27 jun. 2017 a las 15:21, Tomas Cohen Arazi ()
escribió:

> In your /etc/koha/sites//zebra-biblios-dom.cfg file, there
> should be a reference to the 'lang_defs/es' dir on the path, first
> uncommented line.
>
> El mar., 27 jun. 2017 a las 15:18, Luis Moises Rojas (<
> lmoisesro...@gmail.com>) escribió:
>
>> Make sure you are using zebradb/lang_defs/es/sort-string-utf.chr: Well,
>> i change the file, but i do not know if i am using it.  How do i know?
>> Did you choose spanish when creating the instance?: Yes.
>>
>> On Tue, Jun 27, 2017 at 2:14 PM, Tomas Cohen Arazi 
>> wrote:
>>
>>> Make sure you are using zebradb/lang_defs/es/sort-string-utf.chr
>>> Did you choose spanish when creating the instance?
>>>
>>> El mar., 27 jun. 2017 a las 14:39, Luis Moises Rojas (<
>>> lmoisesro...@gmail.com>) escribió:
>>>
 Hello everybody,

 We have:
 OpacdefaultSortField/OpacdefaultSortOrder set to: A-Z (also we changed
 to
 ascendet)

 But when you enter in our OPAC (try it:
 www.catalogoenlinea.bijrd.gob.do),
 and type letter, A and try to search: this is the result:

 Ñam: el ñadu gloton...
 Ícaro...
 Églogan...
 El entre nosotros...
 Álbum

 And so on
 After some others titles, the order is missed again.

 We have changed the /etc/koha/zebradb/etc/word-phrase-utf.chr file in
 order
 to "map aÁ.. etc

 In help, pls?

 Thanks

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

>>> --
>>> Tomás Cohen Arazi
>>> Theke Solutions (https://theke.io )
>>> ✆ +54 9351 3513384 <+54%209%20351%20351-3384>
>>> GPG: B2F3C15F
>>>
>>
>>
>>
>> --
>> *Luis Moisés Rojas P.*
>>
>> --
> Tomás Cohen Arazi
> Theke Solutions (https://theke.io )
> ✆ +54 9351 3513384 <+54%209%20351%20351-3384>
> GPG: B2F3C15F
>
-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Display output is not in order

2017-06-27 Thread Tomas Cohen Arazi 
In your /etc/koha/sites//zebra-biblios-dom.cfg file, there should
be a reference to the 'lang_defs/es' dir on the path, first uncommented
line.

El mar., 27 jun. 2017 a las 15:18, Luis Moises Rojas (<
lmoisesro...@gmail.com>) escribió:

> Make sure you are using zebradb/lang_defs/es/sort-string-utf.chr: Well, i
> change the file, but i do not know if i am using it.  How do i know?
> Did you choose spanish when creating the instance?: Yes.
>
> On Tue, Jun 27, 2017 at 2:14 PM, Tomas Cohen Arazi 
> wrote:
>
>> Make sure you are using zebradb/lang_defs/es/sort-string-utf.chr
>> Did you choose spanish when creating the instance?
>>
>> El mar., 27 jun. 2017 a las 14:39, Luis Moises Rojas (<
>> lmoisesro...@gmail.com>) escribió:
>>
>>> Hello everybody,
>>>
>>> We have:
>>> OpacdefaultSortField/OpacdefaultSortOrder set to: A-Z (also we changed to
>>> ascendet)
>>>
>>> But when you enter in our OPAC (try it: www.catalogoenlinea.bijrd.gob.do
>>> ),
>>> and type letter, A and try to search: this is the result:
>>>
>>> Ñam: el ñadu gloton...
>>> Ícaro...
>>> Églogan...
>>> El entre nosotros...
>>> Álbum
>>>
>>> And so on
>>> After some others titles, the order is missed again.
>>>
>>> We have changed the /etc/koha/zebradb/etc/word-phrase-utf.chr file in
>>> order
>>> to "map aÁ.. etc
>>>
>>> In help, pls?
>>>
>>> Thanks
>>>
>>> --
>>> *Luis Moisés Rojas P.*
>>> ___
>>> Koha mailing list  http://koha-community.org
>>> Koha@lists.katipo.co.nz
>>> https://lists.katipo.co.nz/mailman/listinfo/koha
>>>
>> --
>> Tomás Cohen Arazi
>> Theke Solutions (https://theke.io )
>> ✆ +54 9351 3513384 <+54%209%20351%20351-3384>
>> GPG: B2F3C15F
>>
>
>
>
> --
> *Luis Moisés Rojas P.*
>
> --
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Display output is not in order

2017-06-27 Thread Luis Moises Rojas 
Make sure you are using zebradb/lang_defs/es/sort-string-utf.chr: Well, i
change the file, but i do not know if i am using it.  How do i know?
Did you choose spanish when creating the instance?: Yes.

On Tue, Jun 27, 2017 at 2:14 PM, Tomas Cohen Arazi 
wrote:

> Make sure you are using zebradb/lang_defs/es/sort-string-utf.chr
> Did you choose spanish when creating the instance?
>
> El mar., 27 jun. 2017 a las 14:39, Luis Moises Rojas (<
> lmoisesro...@gmail.com>) escribió:
>
>> Hello everybody,
>>
>> We have:
>> OpacdefaultSortField/OpacdefaultSortOrder set to: A-Z (also we changed to
>> ascendet)
>>
>> But when you enter in our OPAC (try it: www.catalogoenlinea.bijrd.gob.do
>> ),
>> and type letter, A and try to search: this is the result:
>>
>> Ñam: el ñadu gloton...
>> Ícaro...
>> Églogan...
>> El entre nosotros...
>> Álbum
>>
>> And so on
>> After some others titles, the order is missed again.
>>
>> We have changed the /etc/koha/zebradb/etc/word-phrase-utf.chr file in
>> order
>> to "map aÁ.. etc
>>
>> In help, pls?
>>
>> Thanks
>>
>> --
>> *Luis Moisés Rojas P.*
>> ___
>> Koha mailing list  http://koha-community.org
>> Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
>>
> --
> Tomás Cohen Arazi
> Theke Solutions (https://theke.io )
> ✆ +54 9351 3513384
> GPG: B2F3C15F
>



-- 
*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] Display output is not in order

2017-06-27 Thread Tomas Cohen Arazi 
Make sure you are using zebradb/lang_defs/es/sort-string-utf.chr
Did you choose spanish when creating the instance?

El mar., 27 jun. 2017 a las 14:39, Luis Moises Rojas (<
lmoisesro...@gmail.com>) escribió:

> Hello everybody,
>
> We have:
> OpacdefaultSortField/OpacdefaultSortOrder set to: A-Z (also we changed to
> ascendet)
>
> But when you enter in our OPAC (try it: www.catalogoenlinea.bijrd.gob.do),
> and type letter, A and try to search: this is the result:
>
> Ñam: el ñadu gloton...
> Ícaro...
> Églogan...
> El entre nosotros...
> Álbum
>
> And so on
> After some others titles, the order is missed again.
>
> We have changed the /etc/koha/zebradb/etc/word-phrase-utf.chr file in order
> to "map aÁ.. etc
>
> In help, pls?
>
> Thanks
>
> --
> *Luis Moisés Rojas P.*
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Fwd: Unable to reindex after massive upgrade

2017-06-27 Thread Tomas Cohen Arazi 
Tim, the authorised_values_branches table is not related.

The problem is that there are fields in your record(s) that are expected to
contain a branchcode. And they don't. That's why Koha::Libraries->find() is
returning an undefined value (undef in Perl).

When you removed the FK constraint, you did hide the basic problem of
inconsistency.

I suggest that you find your only library's branchcode and make sure your
items all have homebranch and holdingbranch set to that. Then reindex. You
should do it like this:

# Enter to mysql
$ sudo koha-mysql lib
> UPDATE items SET homebranch='LIB', holdingbranch='LIB';
> \q
$ sudo koha-rebuild-zebra -f -a -b -v lib

Note: replace 'lib' for your instance name, and 'LIB' for your library's
branchcode.

Regards.


El mar., 27 jun. 2017 a las 13:59, Tim Young ()
escribió:

> Awesome.  Thanks.  I may be able to figure it out (I am pretty good at
> poking and prodding, and finally figuring it out).  I believe we only
> have one branch, so I should be able to simply replace everything in the
> sql to match the correct branch... (Yikes! Branchcode is used all over
> the place!)
>
> BUT, I am a sysadmin, not a Koha admin.  This looks like it might be
> easier to fix through the web interface... So excuse the dumb questions.
> :)
>
> That particular error seems to stem from something be authorized by
> branches.  My "authorised_values_branches" table is empty. Should I set
> up an authorized branch or something somewhere?
>
> We do have a branch configured (I can see it in the branches table)...
>
> The code seems to be looking at Koha::Libraries->find($value)->branchname;
>
> and (I have "value" being undefined, or defined improperly.  But I do
> not see a libraries table...)
>
> But, at the same time:
> $tagslib->{$tag}->{$subfield}->{'authorised_value'} eq "branches".  So I
> somewhere seem to be saying to authorize by branch, and I do not have
> any authorized branches (or the authorised_values_branches is empty)...
>
> Is there a simple web area I should check out before I jump into the
> mysql and make changes that might not be supported?
>
>  - Tim
>
>
> On 6/27/2017 9:26 AM, Tomas Cohen Arazi wrote:
> > You need to fix your data, so fields linked to branch codes actually
> > contain valid branchcodes. The band aid will work, but I think you
> > need to fix your data for good.
> >
> > Koha got stricter regarding the data quality/completeness. This
> > particular case could be saved by some tweak like the one you propose.
> > It is maybe worth filling a bug, because the previous behaviour worked
> > more gracefuly.
> >
>
> ___
> 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] Display output is not in order

2017-06-27 Thread Luis Moises Rojas 
Hello everybody,

We have:
OpacdefaultSortField/OpacdefaultSortOrder set to: A-Z (also we changed to
ascendet)

But when you enter in our OPAC (try it: www.catalogoenlinea.bijrd.gob.do),
and type letter, A and try to search: this is the result:

Ñam: el ñadu gloton...
Ícaro...
Églogan...
El entre nosotros...
Álbum

And so on
After some others titles, the order is missed again.

We have changed the /etc/koha/zebradb/etc/word-phrase-utf.chr file in order
to "map aÁ.. etc

In help, pls?

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] Help please! we have problem after upgrading ubuntu from 11.10 up to 12.04

2017-06-27 Thread Tim Young 



On 6/27/2017 9:08 AM, "D DuD>DtD2DtD1 D'D,D+D>D,DtN,DuD0DoN N 
"@LightSys.org wrote:

Hi, Tim


It would be helpful to know if you upgraded using package or tarball.

[Николай Ластовка] I upgraded start command "do-upgrade-release", I have no 
mind is it package or tarball, sorry!
Ok.  Did you change versions of Koha during your upgrade?  Or just 
upgrade your operating system?  If Koha was not upgraded during your OS 
upgrade then you are probably using the tarball.

You should be able to run:

 dpkg-query -l | grep koha

That should list any "koha packages" you would have installed.  My guess 
is that you do not have any at this time.





It also helps to know what *nix distro you are using (Centos, Ubuntu, etc)


[Николай Ластовка] ok! We used Ubuntu Server 11.10, now we have 12.04
This one was my bad.  You specified your OS and version in your 
subject.  I just was not observant enough.



It looks like you may need to install a package?

You can usually see if the package is installed by running:
locate Cache/Memcached.pm

If you have it, it should show up something like:
/usr/share/perl5/Cache/Memcached.pm

In Ubuntu, you may need to install libcache-memcached-perl apt-get install
libcache-memcached-perl

If you are using a redhat derivative, you may need to yum install perl-Cache-
Memcached

[Николай Ластовка] we fixed problems, installed packages as you write. And in 
general Koha work.
Great!  Sadly, this is as far as my personal help can help you. From 
here, someone else who is better versed in Koha will need to jump in.  
But, I have a little bit of help then...

Now I have some questions:
- how start SIP server (our RFID selfbook don't work because not connected to 
database);

https://wiki.koha-community.org/wiki/Koha_SIP2_server_setup
Looks like:

 * koha-enable-sip
 * koha-start-sip
 * koha-stop-sip


- need I upgrade to next release of Ubuntu (up to 12.10);

I would start going to the LTS versions:
https://askubuntu.com/questions/514530/how-to-change-preferred-release-type-for-a-server-to-lts

   Edit /etc/update-manager/release-upgrades and set (in the [DEFAULT]
   section):

   Prompt=lts

There is very good support for migrating between LTS versions, and it 
will make your upgrade path much shorter.  I do not know how Koha is 
affected by these upgrades.  I am not a real koha guru; I do some work 
on a Koha machine once a year or every other year.  So if a real Koha 
person responds with a different answer, trust their answer above mine.  :)



- best version of Koha we can update (we have ver. 3.06.03.00) and what we must 
to control (we have some files in Russian lang);

Sorry, someone else will need to answer this question for you.  :)

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

Re: [Koha] Fwd: Unable to reindex after massive upgrade

2017-06-27 Thread Tim Young 
Awesome.  Thanks.  I may be able to figure it out (I am pretty good at 
poking and prodding, and finally figuring it out).  I believe we only 
have one branch, so I should be able to simply replace everything in the 
sql to match the correct branch... (Yikes! Branchcode is used all over 
the place!)


BUT, I am a sysadmin, not a Koha admin.  This looks like it might be 
easier to fix through the web interface... So excuse the dumb questions.  :)


That particular error seems to stem from something be authorized by 
branches.  My "authorised_values_branches" table is empty. Should I set 
up an authorized branch or something somewhere?


We do have a branch configured (I can see it in the branches table)...

The code seems to be looking at Koha::Libraries->find($value)->branchname;

and (I have "value" being undefined, or defined improperly.  But I do 
not see a libraries table...)


But, at the same time: 
$tagslib->{$tag}->{$subfield}->{'authorised_value'} eq "branches".  So I 
somewhere seem to be saying to authorize by branch, and I do not have 
any authorized branches (or the authorised_values_branches is empty)...


Is there a simple web area I should check out before I jump into the 
mysql and make changes that might not be supported?


- Tim


On 6/27/2017 9:26 AM, Tomas Cohen Arazi wrote:
You need to fix your data, so fields linked to branch codes actually 
contain valid branchcodes. The band aid will work, but I think you 
need to fix your data for good.


Koha got stricter regarding the data quality/completeness. This 
particular case could be saved by some tweak like the one you propose. 
It is maybe worth filling a bug, because the previous behaviour worked 
more gracefuly.




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

Re: [Koha] Add a branch, or not?

2017-06-27 Thread Elaine Bradtke 
Thank you for the pointers. We have a test site for just this sort of thing.

On Tue, Jun 27, 2017 at 1:49 AM, Tajoli Zeno  wrote:

> Hi Elaine
>
> Il 26/06/2017 20:37, Elaine Bradtke ha scritto:
>
>> What's the best way to do this with Koha?
>> ​Would setting up a branch work, or would it be better to set up a
>> different instance and somehow get them to link together for broader
>> searches?
>>
>
> if you setup a different instance you can't do this:
>
> and it might be easier to link their holdings to our
>> records instead of converting their database to MARC.​
>>
>
> As I see here [http://catalogue.efdss.org/] you are a mono branch install.
> You can add an other without problem then you need two new dns address.
> One for the new library and one for 'the general catalog'.
> You can mantain the present dns name [http://catalogue.efdss.org/] for
> your branch
> Read this pdf: http://www.koha.org/library/re
> sources/Documentation/OPAC-Customization.pdf
> To do good result you must done same magic in apache conf files:  in the
> different VirtualHost section you can insert different system preferences
> using SetEnv OVERRIDE_SYSPREF_PrefName Value
>
> . If it's a small bit of digital magic that needs doing, we might be able
>> to beg some help from a friendly IT wizard.
>>
>
> Is better that to ask him/here to read:
> http://www.koha.org/library/resources/Documentation/OPAC-Customization.pdf
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10325
>
> ATTENTION: before go to production, test the setup in a TEST server.
>
> Bye
> Zeno Tajoli
>
>
> --
> Zeno Tajoli
> /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche
> Email: z.taj...@cineca.it Fax: 051/6132198
> *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)
>



-- 
Elaine Bradtke
Data Wrangler
VWML
English Folk Dance and Song Society | http://www.efdss.org
Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
Tel+44 (0) 20 7485 2206 (This number is for the English Folk Dance and
Song Society in London, England. If you wish to phone me personally, send
an e-mail first. I work off site)
--
Registered Company No. 297142
Charity Registered in England and Wales No. 305999
---
"Writing about music is like dancing about architecture"
--Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Fwd: Unable to reindex after massive upgrade

2017-06-27 Thread Tomas Cohen Arazi 
You need to fix your data, so fields linked to branch codes actually
contain valid branchcodes. The band aid will work, but I think you need to
fix your data for good.

Koha got stricter regarding the data quality/completeness. This particular
case could be saved by some tweak like the one you propose. It is maybe
worth filling a bug, because the previous behaviour worked more gracefuly.


El mar., 27 jun. 2017 a las 10:25, Tim Young ()
escribió:

> Previously, I noted that I was not able to reindex.  I tracked it down
> to the following.
>
> My biblio_metadata file wasempty, and therefore my reindex could not
> retrieve any biblio information.
>
> Now that I know what to look for, there was this error during the upgrade:
>
>  [Thu Jun 22 22:29:11 2017] updatedatabase.pl: DBD::mysql::db do
> failed: *Cannot add or update a child row: a foreign key constraint
> fails* (`kohadb2015`.`biblio_metadata`, CONSTRAINT
> `biblio_metadata_fk_1` FOREIGN KEY (`biblionumber`) REFERENCES `biblio`
> (`biblionumber`) ON DELETE CASCADE ON UPDATE CASCADE) [for Statement "
>  [Thu Jun 22 22:29:11 2017] updatedatabase.pl: INSERT INTO
> biblio_metadata ( biblionumber, format, marcflavour, metadata ) SELECT
> biblionumber, 'marcxml', 'CHANGEME', marcxml FROM biblioitems;
>
> I think this is where the upgrade failed; the newly created
> biblio_metadata has a foreign key:
>
> *CONSTRAINT `biblio_metadata_fk_1` FOREIGN KEY (biblionumber)
> REFERENCES biblio (biblionumber) ON DELETE CASCADE ON UPDATE CASCADE*
>
>
> When doing the bulk migration, we probably need to turn off foreign key
> checks before doing the update:
>
> SET FOREIGN_KEY_CHECKS=0;
>
>
> And then put them back once it has been done:
>
> SET FOREIGN_KEY_CHECKS=1;
>
>
>
> [update having solved the problem]
> This glitch was caused primarily by a few different things:
> 1) a previous update to the mysql did not upgrade all the users. The
> debian-sys-maint user was somewhat broken.  Various things that depended
> on this user failed during the upgrade.
> 2) We have some broken data in our install.  At one time we had a number
> of records get corrupted, which resulted in records that do not have the
> records corresponding to their foreign keys.
> 3) I did not immediately notice the importance of the error logs (above)
> telling me that my data had not been copied over.
>
> To fix my mysql issues with debian-sys-maint, I ended up running
>
> #  mysql_upgrade --force -uroot -p
>
> This repaired the mysql users table.
>
>   Being a wise sysadmin, I had a backup database [kohadb2015] which had
> our original data.  To populate that table with the marc data, I ran the
> following sql:
>
> SET FOREIGN_KEY_CHECKS=0;
>
> INSERT INTO koha_opac.biblio_metadata ( biblionumber, format,
> marcflavour, metadata ) SELECT biblionumber, 'marcxml', 'CHANGEME', marcxml
> FROM kohadb2015.biblioitems;
>
> UPDATE biblio_metadata SET marcflavour = (SELECT value FROM
> systempreferences WHERE variable="marcflavour");
>
> SET FOREIGN_KEY_CHECKS=1;
>
> After that, I was able to reindex fine.
>
> When the reindex was complete, the pages would still not load.   I was
> getting an error rendering the page.
> Can't call method "branchname" on an undefined value at
> /usr/share/koha/lib/C4/Biblio.pm line 1627
>
> I am not entirely sure if this is yet another problem with my data, or
> if I have some odd setting somewhere.  What I did, however, was to
> modify the koha code to avoid it blowing up:
>
> vi /usr/share/koha/lib/C4/Biblio.pm +1627
>
> if ( $tagslib->{$tag}->{$subfield}->{'authorised_value'} eq "branches" ) {
>  *if(defined(Koha::Libraries->find($value)))*
> {
>   return Koha::Libraries->find($value)->branchname;
> }
>
>
>
>  - Tim Young
>
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Help please! we have problem after upgrading ubuntu from 11.10 up to 12.04

2017-06-27 Thread Деловой Библиотекарь 
Hi, Tim

> It would be helpful to know if you upgraded using package or tarball.

[Николай Ластовка] I upgraded start command "do-upgrade-release", I have no 
mind is it package or tarball, sorry!

> 
> It also helps to know what *nix distro you are using (Centos, Ubuntu, etc)
> 
[Николай Ластовка] ok! We used Ubuntu Server 11.10, now we have 12.04

> It looks like you may need to install a package?
> 
> You can usually see if the package is installed by running:
> locate Cache/Memcached.pm
> 
> If you have it, it should show up something like:
> /usr/share/perl5/Cache/Memcached.pm
> 
> In Ubuntu, you may need to install libcache-memcached-perl apt-get install
> libcache-memcached-perl
> 
> If you are using a redhat derivative, you may need to yum install perl-Cache-
> Memcached

[Николай Ластовка] we fixed problems, installed packages as you write. And in 
general Koha work. 
Now I have some questions: 
- how start SIP server (our RFID selfbook don't work because not connected to 
database);
- need I upgrade to next release of Ubuntu (up to 12.10);
- best version of Koha we can update (we have ver. 3.06.03.00) and what we must 
to control (we have some files in Russian lang);

Thanks fo answer, 
Good luck!

> 
>  - Tim Young
> 
> On 6/27/2017 4:39 AM, "D DuD>DtD2DtD1 D'D,D+D>D,DtN,DuD0DoN N
> "@LightSys.org wrote:
> > Hi there!
> >
> > My name is Nikolay, I'm from Moscow, Russia, we use Koha LS. Last time
> ago koha start working  very slow. We did upgrade ubuntu server  up to 12.04
> and new when we try connect to Koha we have next:
> >
> > Software error:
> > Can't locate Cache/Memcached.pm in @INC (@INC contains:
> /usr/share/koha/lib /etc/perl /usr/local/lib/perl/5.14.2
> /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 
> /usr/lib/perl/5.14
> /usr/share/perl/5.14 /usr/local/lib/site_perl .) at
> /usr/share/koha/lib/C4/Context.pm line 86.
> > BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Context.pm
> line 98.
> > Compilation failed in require at /usr/share/koha/lib/C4/Auth.pm line 28.
> > BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line
> 28.
> > Compilation failed in require at /usr/share/koha/opac/cgi-bin/opac/opac-
> main.pl line 22.
> > BEGIN failed--compilation aborted at /usr/share/koha/opac/cgi-
> bin/opac/opac-main.pl line 22.
> >
> > What we must to do to fix problem? I am VERY new in *nix, so please be
> > polite 
> >
> > Thanks for help!
> >
> > ___
> > 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] Fwd: Unable to reindex after massive upgrade

2017-06-27 Thread Tim Young 
Previously, I noted that I was not able to reindex.  I tracked it down 
to the following.


My biblio_metadata file wasempty, and therefore my reindex could not 
retrieve any biblio information.


Now that I know what to look for, there was this error during the upgrade:

[Thu Jun 22 22:29:11 2017] updatedatabase.pl: DBD::mysql::db do 
failed: *Cannot add or update a child row: a foreign key constraint 
fails* (`kohadb2015`.`biblio_metadata`, CONSTRAINT 
`biblio_metadata_fk_1` FOREIGN KEY (`biblionumber`) REFERENCES `biblio` 
(`biblionumber`) ON DELETE CASCADE ON UPDATE CASCADE) [for Statement "
[Thu Jun 22 22:29:11 2017] updatedatabase.pl: INSERT INTO 
biblio_metadata ( biblionumber, format, marcflavour, metadata ) SELECT 
biblionumber, 'marcxml', 'CHANGEME', marcxml FROM biblioitems;


I think this is where the upgrade failed; the newly created 
biblio_metadata has a foreign key:


   *CONSTRAINT `biblio_metadata_fk_1` FOREIGN KEY (biblionumber)
   REFERENCES biblio (biblionumber) ON DELETE CASCADE ON UPDATE CASCADE*


When doing the bulk migration, we probably need to turn off foreign key 
checks before doing the update:


   SET FOREIGN_KEY_CHECKS=0;


And then put them back once it has been done:

   SET FOREIGN_KEY_CHECKS=1;



[update having solved the problem]
This glitch was caused primarily by a few different things:
1) a previous update to the mysql did not upgrade all the users. The 
debian-sys-maint user was somewhat broken.  Various things that depended 
on this user failed during the upgrade.
2) We have some broken data in our install.  At one time we had a number 
of records get corrupted, which resulted in records that do not have the 
records corresponding to their foreign keys.
3) I did not immediately notice the importance of the error logs (above) 
telling me that my data had not been copied over.


To fix my mysql issues with debian-sys-maint, I ended up running

   #  mysql_upgrade --force -uroot -p

This repaired the mysql users table.

 Being a wise sysadmin, I had a backup database [kohadb2015] which had 
our original data.  To populate that table with the marc data, I ran the 
following sql:


   SET FOREIGN_KEY_CHECKS=0;

   INSERT INTO koha_opac.biblio_metadata ( biblionumber, format, marcflavour, 
metadata ) SELECT biblionumber, 'marcxml', 'CHANGEME', marcxml FROM 
kohadb2015.biblioitems;

   UPDATE biblio_metadata SET marcflavour = (SELECT value FROM systempreferences WHERE 
variable="marcflavour");

   SET FOREIGN_KEY_CHECKS=1;

After that, I was able to reindex fine.

When the reindex was complete, the pages would still not load.   I was 
getting an error rendering the page.
Can't call method "branchname" on an undefined value at 
/usr/share/koha/lib/C4/Biblio.pm line 1627


I am not entirely sure if this is yet another problem with my data, or 
if I have some odd setting somewhere.  What I did, however, was to 
modify the koha code to avoid it blowing up:


vi /usr/share/koha/lib/C4/Biblio.pm +1627

if ( $tagslib->{$tag}->{$subfield}->{'authorised_value'} eq "branches" ) {
*if(defined(Koha::Libraries->find($value)))*
   {
 return Koha::Libraries->find($value)->branchname;
   }



- Tim Young

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

Re: [Koha] Help please! we have problem after upgrading ubuntu from 11.10 up to 12.04

2017-06-27 Thread Tim Young 

Greetings,

It would be helpful to know if you upgraded using package or tarball.

It also helps to know what *nix distro you are using (Centos, Ubuntu, etc)

It looks like you may need to install a package?

You can usually see if the package is installed by running:
locate Cache/Memcached.pm

If you have it, it should show up something like:
/usr/share/perl5/Cache/Memcached.pm

In Ubuntu, you may need to install libcache-memcached-perl
apt-get install libcache-memcached-perl

If you are using a redhat derivative, you may need to
yum install perl-Cache-Memcached

- Tim Young

On 6/27/2017 4:39 AM, "D DuD>DtD2DtD1 D'D,D+D>D,DtN,DuD0DoN N 
"@LightSys.org wrote:

Hi there!

My name is Nikolay, I'm from Moscow, Russia, we use Koha LS. Last time ago koha 
start working  very slow. We did upgrade ubuntu server  up to 12.04 and new 
when we try connect to Koha we have next:

Software error:
Can't locate Cache/Memcached.pm in @INC (@INC contains: /usr/share/koha/lib 
/etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 
/usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 
/usr/local/lib/site_perl .) at /usr/share/koha/lib/C4/Context.pm line 86.
BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Context.pm line 98.
Compilation failed in require at /usr/share/koha/lib/C4/Auth.pm line 28.
BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 28.
Compilation failed in require at /usr/share/koha/opac/cgi-bin/opac/opac-main.pl 
line 22.
BEGIN failed--compilation aborted at 
/usr/share/koha/opac/cgi-bin/opac/opac-main.pl line 22.

What we must to do to fix problem? I am VERY new in *nix, so please be polite 

Thanks for help!

___
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] Z39.50 encoding problem (tested on 2 koha servers)

2017-06-27 Thread anjoze 
Hi Barton,
I've done some tests based on this page:
https://wiki.koha-community.org/wiki/Troubleshooting_Zebra
I will put the results here:
*yaz-client -c /etc/koha/zebradb/ccl.properties koha_test:9998/biblios*
/Connecting...OK.
Sent initrequest.
Connection accepted by v3 target.
ID : 81
Name   : Zebra Information Server/GFS/YAZ
Version: 4.2.30 98864b44c654645bc16b2c54f822dc2e45a93031
Options: search present delSet triggerResourceCtrl scan sort
extendedServices namedResultSets
Elapsed: 0.001579
Z>

Z> *f homem*
Sent searchRequest.
Received SearchResponse.
Search was a success.
Number of hits: 1, setno 1
SearchResult-1: term=homem cnt=1
records returned: 0
Elapsed: 0.003632
Z> 

*Z> format xml
Z> show 1*
Sent presentRequest (1+1).
Records: 1
[biblios]Record type: XML

http://www.w3.org/2001/XMLSchema-instance;
xmlns="http://www.loc.gov/MARC21/slim;
xsi:schemaLocation="http://www.loc.gov/MARC21/slim
http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd;>

   nam  224500
  2
  
978-989-628-078-9
  
  
PT
278876/08
  
  
2
  
  
por
  
  
PT
  
  
20100225d2008m||y0frey5003ba
  
  
Um homem de aluguer
Neus Arqués
trad. Helena Pitta
  
  
1ª ed
  
  
Matosinhos
QuidNovi
2008
  
  
175 p.
24 cm
  
  
Ficção estrangeira
  
  
Tít. orig.: Um hombre de pago
  
  
821.134.2-31"20"
BN
por
  
  
Arqués
Neus
1964-
1
  
  
Pitta
Helena
730
2
  
  
PT
BN
RPC
  
  
test
12-06-2017
  
  
MON
  
  
0
0
8231_ARQ
01
1
TESTE
01
82-31 ARQ
0
MON
Oferta
  

nextResultSetPosition = 2
Elapsed: 0.039125
/ 

As you can see, the results are OK, all the characters are OK.
The problem is on koha...

 
 
 
 




-
Koha version:   16.05.05
   - -
José Anjos
--
View this message in context: 
http://koha.1045719.n5.nabble.com/Z39-50-encoding-problem-tested-on-2-koha-servers-tp5938540p5938557.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Syspref itemBarcodeFallbackSearch

2017-06-27 Thread Pedro Amorim 
Hello Katrin,

Thank you for your reply.
Upon my research I was/am also leaning towards a solution like that:
assigning the copy number with the homebranch prefix.
It'll still be needed to reprint labels for the delta items, but at least
Koha will allow for checkin/checkout.

Thanks,

Pedro Amorim

2017-06-26 19:09 GMT+00:00 Katrin :

> Hi Pedro,
>
> you are right, at the moment a barcode in the item is still needed for
> checkouts to work. We have used another value as a replacement for the
> barcode in the past, duplicating the (unique) callnumber into the barcode
> field or assigning a number with a special prefix or something like that.
>
> Hope that helps,
>
> Katrin
>
>
> On 23.06.2017 13:11, Pedro Amorim wrote:
>
>> Hello everyone,
>>
>> I imported records with *dedupbarcode* option and some of them were
>> imported with no barcode, because there were already some items with the
>> same barcode, as expected.
>>
>> Now, I want to be able to check out some of the items that have no barcode
>> information, and tried the syspref *itemBarcodeFallbackSearch*. This is
>> nice because in the check out interface I can now input other information
>> (callnumber, copy number, record title) and still retrieve the item.
>> However, it seems that this search only provides the items that actually
>> have barcode information associated with it.
>>
>> In the code:
>> https://github.com/Koha-Community/Koha/blob/master/circ/
>> circulation.pl#L359
>>
>> It seems that the item is only added to the list of options if there is,
>> in
>> fact, bar code information.
>> After a couple of tests, it never returns the items with no barcode, only
>> the ones that have it. Has anyone tried this? Is this the expected
>> behaviour?
>>
>> Thanks,
>>
>> Pedro Amorim
>> ___
>> 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] Z39.50 encoding problem (tested on 2 koha servers)

2017-06-27 Thread Barton Chittenden 
On Tue, Jun 27, 2017 at 5:17 AM, anjoze  wrote:

> José


José,

Have you tried connecting via yaz-client? What about another z39.50 client?
It would be useful to know whether the encoding errors are in Koha or in
zebra.

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

[Koha] Help please! we have problem after upgrading ubuntu from 11.10 up to 12.04

2017-06-27 Thread Деловой Библиотекарь 
Hi there!

My name is Nikolay, I'm from Moscow, Russia, we use Koha LS. Last time ago koha 
start working  very slow. We did upgrade ubuntu server  up to 12.04 and new 
when we try connect to Koha we have next: 

Software error:
Can't locate Cache/Memcached.pm in @INC (@INC contains: /usr/share/koha/lib 
/etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 
/usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 
/usr/local/lib/site_perl .) at /usr/share/koha/lib/C4/Context.pm line 86.
BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Context.pm line 98.
Compilation failed in require at /usr/share/koha/lib/C4/Auth.pm line 28.
BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 28.
Compilation failed in require at /usr/share/koha/opac/cgi-bin/opac/opac-main.pl 
line 22.
BEGIN failed--compilation aborted at 
/usr/share/koha/opac/cgi-bin/opac/opac-main.pl line 22.

What we must to do to fix problem? I am VERY new in *nix, so please be polite 

Thanks for help!

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

[Koha] Z39.50 encoding problem (tested on 2 koha servers)

2017-06-27 Thread anjoze 
Hi again.
From always (3.2 --> 16.11) I could not get the right encoding when
searching with Z3950 on other servers.
I've tried with all the available encodings (utf8, EUC-KR, ISO_5426,
ISO_6937, ISO_8859-1, MARC-8 ) but always have strange characters on
results.
I alway thought the problem was the other servers that maybe have a strange
charset.
So, I've installed 2 koha servers *with the same options* then I enabled
Z39.50 on one and tested searching with z39.50 with the other one. The
problem persists!! :( Problems with accent characters (é, ã, í, ç)

Ubuntu Servers:
LANG=pt_PT.UTF-8
LANGUAGE=pt:pt_BR:en
LC_CTYPE="pt_PT.UTF-8"
LC_NUMERIC=pt_PT
LC_TIME=pt_PT
LC_COLLATE="pt_PT.UTF-8"
LC_MONETARY=pt_PT
LC_MESSAGES="pt_PT.UTF-8"
LC_PAPER=pt_PT
LC_NAME=pt_PT
LC_ADDRESS=pt_PT
LC_TELEPHONE=pt_PT
LC_MEASUREMENT=pt_PT
LC_IDENTIFICATION=pt_PT
LC_ALL=

Koha with UNIMARC

I've checked some configuration files like:
/etc/koha/sites/koha/koha-conf.xml
/etc/koha/zebradb/retrieval-info-bib-dom.xml
/etc/koha/unimarc-retrieval-info-bib-grs1.xml 
/usr/share/koha/intranet/cgi-bin/cataloguing/z3950_search.pl

Everything is set with:
syntax="unimarc" name="F">


Thanks for any help



-
Koha version:   16.05.05
   - -
José Anjos
--
View this message in context: 
http://koha.1045719.n5.nabble.com/Z39-50-encoding-problem-tested-on-2-koha-servers-tp5938540.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Add a branch, or not?

2017-06-27 Thread Tajoli Zeno 

Hi Elaine

Il 26/06/2017 20:37, Elaine Bradtke ha scritto:

What's the best way to do this with Koha?
​Would setting up a branch work, or would it be better to set up a
different instance and somehow get them to link together for broader
searches?


if you setup a different instance you can't do this:


and it might be easier to link their holdings to our
records instead of converting their database to MARC.​


As I see here [http://catalogue.efdss.org/] you are a mono branch install.
You can add an other without problem then you need two new dns address.
One for the new library and one for 'the general catalog'.
You can mantain the present dns name [http://catalogue.efdss.org/] for 
your branch
Read this pdf: 
http://www.koha.org/library/resources/Documentation/OPAC-Customization.pdf
To do good result you must done same magic in apache conf files:  in the 
different VirtualHost section you can insert different system 
preferences using SetEnv OVERRIDE_SYSPREF_PrefName Value



. If it's a small bit of digital magic that needs doing, we might be able
to beg some help from a friendly IT wizard.


Is better that to ask him/here to read:
http://www.koha.org/library/resources/Documentation/OPAC-Customization.pdf
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10325

ATTENTION: before go to production, test the setup in a TEST server.

Bye
Zeno Tajoli


--
Zeno Tajoli
/SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche
Email: z.taj...@cineca.it Fax: 051/6132198
*CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha