date:20160112

[Koha] Show analytics

2016-01-12 Thread Hugo Agud

Good morning

we have found a strange behaviour of show analytics in Koha, checking the
code it seems that OPAC shows the link 'Show analytics" based on position
leader 7 = s

In fact that position shows define the record as is a serial, but it can
include analytics or not.

For other instances we have modified the code to check another field, one
used when we add some analytics to the record, but it is a little weird.

I wish to ask you how other sites are mananing the link to analytics from
the hosting record, let koha shows always the link? or have you got any tip
to show only if analytics are catalogued.

We have checked this behaviour in version 3.14.7 and in 3.22.x, I guess it
is in all versions of koha.

Thanks you in advance
Hugo



-- 

*Hugo Agud - Orex Digital *

*www.orex.es *


  [image: http://orex.es] 



Director

Passatge de la Llançadera, 3 · 08338 Premià de Dalt - Tel: 93 539 40 70
ha...@orex.es · http://www.orex.es/



No imprima este mensaje a no ser que sea necesario. Una tonelada de papel
implica la tala de 15 árboles y el consumo de 250.000 litros de agua.



Aviso de confidencialidad
Este mensaje contiene información que puede ser CONFIDENCIAL y/o de USO
RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni
está autorizado a recibirlo por el remitente), no está autorizado a copiar,
reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje
por error, por favor, notifíquenoslo inmediatamente y bórrelo de su sistema.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] System treating patron secondary email as mandatory and complaining even with valid email address

2016-01-12 Thread Admire Mutsikiwa

 

Hi All

I have upgraded my Koha instance from version 3.18 to 3.22. Now when
updating patron records that have expired, the system is complaining if the
secondary email is empty and yet it is not mandatory. In addition, if there
is valid email, it is also complaining that it is invalid until you edit it
somehow, that is when it will save the record. Any pointers to resolve this.

 

 

 

Kind Regards,

 

Admire Mutsikiwa (Mr)

ICT Manager

Libraries

University of Zimbabwe

Tel:+263-4-303276

Mob:+26377111

 

"It is easy to dodge our responsibilities, but we cannot dodge the
consequences of dodging our responsibilities."  Josiah Charles Stamp
 

 

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

Re: [Koha] System treating patron secondary email as mandatory and complaining even with valid email address

2016-01-12 Thread Jonathan Druart

Hello Admire,
With "it's not mandatory", you mean you have checked the system
preference "BorrowerMandatoryField "?

2016-01-12 14:21 GMT+00:00 Admire Mutsikiwa :
>
>
> Hi All
>
> I have upgraded my Koha instance from version 3.18 to 3.22. Now when
> updating patron records that have expired, the system is complaining if the
> secondary email is empty and yet it is not mandatory. In addition, if there
> is valid email, it is also complaining that it is invalid until you edit it
> somehow, that is when it will save the record. Any pointers to resolve this.
>
>
>
>
>
>
>
> Kind Regards,
>
>
>
> Admire Mutsikiwa (Mr)
>
> ICT Manager
>
> Libraries
>
> University of Zimbabwe
>
> Tel:+263-4-303276
>
> Mob:+26377111
>
>
>
> "It is easy to dodge our responsibilities, but we cannot dodge the
> consequences of dodging our responsibilities."  Josiah Charles Stamp
> 
>
>
>
> ___
> 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] Issue Report

2016-01-12 Thread M Waqar Aslam

Thank you very  much Sir for your response on my query.  I am requesting to you 
  compile a complete SQL reports which are mostly using in Libraries.  Here is 
enough data available on  
http://wiki.koha-community.org/wiki/SQL_Reports_Library but mostly SQL queries 
is not working. Thanks

Muhammad Waqar Aslam
Air University

From: Sher Afzal 
Sent: Tuesday, January 12, 2016 7:52 AM
To: Chris Cormack; M Waqar Aslam
Cc: koha@lists.katipo.co.nz
Subject: Re: [Koha] Issue Report

Dear Mr Waqar Aslam

Please find below the Sql Reports as desired. As this version is too old i 
recommend to use the latest version of koha or please contact with me for the 
latest Full Stack Latest version koha live DVD.

Please copy and past the following command in SQL box.

SELECT statistics.datetime AS 'Issue Date', 
borrowers.surname,borrowers.firstname, borrowers.cardnumber, items.barcode, 
biblio.title FROM borrowers
LEFT JOIN statistics ON (statistics.borrowernumber=borrowers.borrowernumber)
LEFT JOIN items ON (items.itemnumber = statistics.itemnumber)
LEFT JOIN biblio ON (biblio.biblionumber = items.biblionumber)
WHERE statistics.type='issue'
AND date(statistics.datetime)
BETWEEN <>
AND <>
AND statistics.branch= <>
ORDER BY borrowers.surname ASC

Regards
SHER AFZAL
Chief Librarian
Bahria University

From: Koha  on behalf of Chris Cormack 

Sent: Saturday, January 9, 2016 12:42 AM
To: M Waqar Aslam
Cc: koha@lists.katipo.co.nz
Subject: Re: [Koha] Issue Report

On 9 January 2016 at 00:35, M Waqar Aslam  wrote:
> Dear Colleagues !
>
>  I hope all you are doing well. we are using KOHA version 3.04.02. We have  
> started for Circulation. Now i want to create issue report From 01-01-2015 to 
> 31-12-2015. Please if any have query about then please send. Thanks
>
>
>
Hi Waqar

Was that a typo? Are you really using 3.04.02? That was released in
Jun 2011 ... 4.5 years ago. I doubt anyone will be able to give you
much help for a version that old.
The database structure for circulation has changed quite a lot since then.

Chris
___
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] Koha upgrade 3.18.11 --> 3.20.07

2016-01-12 Thread Bortel, Gary

Hmmm...

>> The installation here is Ubuntu 14.04.3 with a multi-tenant package 
>> install of Koha. Mysql  Ver 14.14 Distrib 5.5.46, for 
>> debian-linux-gnu
>> (x86_64) using readline 6.3 

I updated to  Koha 3.20.07 this morning and the staff site is now exhibiting 
behavior related to Bug 15431 
(http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15431). After 
navigating to a patron with materials checked out, "Checkout(s)" at the bottom 
of the page shows "Loading..." indefinitely. Clicking on the "Check out" tab 
brings a pop-up message box " Loading…you may continue scanning.", but the 
checked out items never appear. 

I assume checkouts and returns continue to work. (There's no way to verify 
since the checkout information doesn't appear.) This does, however, make it 
difficult for them to renew materials for patrons.

Any suggestions?


gcb
__ 

Gary C. Bortel
Office of the Secretary of State, Washington State Library
gary.bor...@sos.wa.gov
360.570.5588

Washington State Library: Empowering 21st Century Washington

-Original Message-
From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Jonathan Druart
Sent: Monday, January 11, 2016 9:14 AM
To: koha@lists.katipo.co.nz
Subject: Re: [Koha] Koha upgrade 3.18.11 --> 3.20.07

http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=installer/data/mysql/updatedatabase.pl;h=950ed2067dac0edd51cf5e49ff25862c6f53ecdb;hb=refs/heads/3.20.x#l10576

It exploded because you already had the constraint (course_reserves_ibfk_2), so 
everything is fine.

2016-01-11 17:01 GMT+00:00 Bortel, Gary :
> Hmmm...
>
> Using "SHOW CREATE TABLE course_reserves" returns...
>
> .
> .
> .
>   PRIMARY KEY (`cr_id`),
>   UNIQUE KEY `pseudo_key` (`course_id`,`ci_id`),
>   KEY `course_id` (`course_id`),
>   KEY `course_reserves_ibfk_2` (`ci_id`),
>   CONSTRAINT `course_reserves_ibfk_1` FOREIGN KEY (`course_id`) REFERENCES 
> `courses` (`course_id`),
>   CONSTRAINT `course_reserves_ibfk_2` FOREIGN KEY (`ci_id`) REFERENCES 
> `course_items` (`ci_id`) ON DELETE CASCADE ON UPDATE CASCADE
> ) ENGINE=InnoDB DEFAULT CHARSET=utf8 |
>
> The course reserves function is not enabled on this instance and both 
> course_reserves and course_items are empty. Could it be updatedatabase.pl is 
> expecting that function to be enabled and those tables to contain at least 
> one item? I hate to admit it, but I don't see a line 10584 in 
> updatedatabase.pl so it's difficult for me to determine what is throwing the 
> error.
>
>
> gcb
> __
>
> Gary C. Bortel
> Office of the Secretary of State, Washington State Library 
> gary.bor...@sos.wa.gov
> 360.570.5588
>
> Washington State Library: Empowering 21st Century Washington
>
>
> -Original Message-
> From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of 
> Jonathan Druart
> Sent: Monday, January 11, 2016 8:24 AM
> To: koha@lists.katipo.co.nz
> Subject: Re: [Koha] Koha upgrade 3.18.11 --> 3.20.07
>
> Hi Gary,
>
>> DBD::mysql::db do failed: Can't create table 'koha_library.#sql-4b9_42' 
>> (errno: 121) at 
>> /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 
>> 10584.
>
> I would say that the foreign key on course_reserves has not been created.
> You should check the data in course_items (some don't have a correspondence 
> in course_reserves).
>
>> DBD::mysql::db do failed: Duplicate entry '1-self_checkout' for key 
>> 'PRIMARY' at 
>> /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 
>> 10614.
>
> You can forget this one, you already had the self_checkout syspref in your 
> database.
>
> Regards,
> Jonathan
>
> 2016-01-11 16:02 GMT+00:00 Bortel, Gary :
>> I am seeing two MySQL errors thrown when trying to update from 3.18.11 --> 
>> 3.20.07. Are these benign or something about which concern should be raised?
>>
>> The installation here is Ubuntu 14.04.3 with a multi-tenant package 
>> install of Koha. Mysql  Ver 14.14 Distrib 5.5.46, for 
>> debian-linux-gnu
>> (x86_64) using readline 6.3
>>
>> .
>> .
>> .
>> .
>> Upgrade to 3.20.00.002 done (Bug 5010: Fix OPACBaseURL to include
>> protocol) Upgrade to 3.20.01.000 done (Koha 3.20.1) Upgrade to
>> 3.20.01.001 done (Bug 9942: Privacy is correctly set) Upgrade to
>> 3.20.01.002 done (Bug 13993: Correct orderstatus for transferred
>> orders) Upgrade to 3.20.02.000 done (Koha 3.20.2) Upgrade to
>> 3.20.03.000 done (Koha 3.20.3) DBD::mysql::db do failed: Can't create 
>> table 'koha_library.#sql-4b9_42' (errno: 121) at 
>> /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 
>> 10584.
>> Upgrade to 3.20.03.001 done (Bug 14205: Deleting an Item/Record does 
>> not remove link to course reserve) Upgrade to 3.20.03.002 done (Bug
>> 14717: Prevent -00-00 dates in patron data) DBD::mysql::db do failed: 
>> Duplicate entry '1-self_checkout' for key 'PRIMARY' at 
>> /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 
>> 10614

Re: [Koha] Koha upgrade 3.18.11 --> 3.20.07

2016-01-12 Thread Liz Rea

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I've just done this exact same thing, and I used the patch from 15341
to patch the running system live. It should be fixed in 3.20.08.

Nasty little bug, that.

Liz

On 13/01/16 12:42, Bortel, Gary wrote:
> Hmmm...
> 
>>> The installation here is Ubuntu 14.04.3 with a multi-tenant 
>>> package install of Koha. Mysql  Ver 14.14 Distrib 5.5.46, for 
>>> debian-linux-gnu (x86_64) using readline 6.3
> 
> I updated to  Koha 3.20.07 this morning and the staff site is now 
> exhibiting behavior related to Bug 15431 
> (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15431). 
> After navigating to a patron with materials checked out, 
> "Checkout(s)" at the bottom of the page shows "Loading..." 
> indefinitely. Clicking on the "Check out" tab brings a pop-up 
> message box " Loading…you may continue scanning.", but the checked 
> out items never appear.
> 
> I assume checkouts and returns continue to work. (There's no way
> to verify since the checkout information doesn't appear.) This
> does, however, make it difficult for them to renew materials for 
> patrons.
> 
> Any suggestions?
> 
> 
> gcb __
> 
> Gary C. Bortel Office of the Secretary of State, Washington State 
> Library gary.bor...@sos.wa.gov 360.570.5588
> 
> Washington State Library: Empowering 21st Century Washington
> 
> -Original Message- From: Koha 
> [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Jonathan 
> Druart Sent: Monday, January 11, 2016 9:14 AM To: 
> koha@lists.katipo.co.nz Subject: Re: [Koha] Koha upgrade 3.18.11 
> --> 3.20.07
> 
> http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=installer/da
ta/mysql/updatedatabase.pl;h=950ed2067dac0edd51cf5e49ff25862c6f53ecdb;hb
=refs/heads/3.20.x#l10576
>
>
> 
It exploded because you already had the constraint
> (course_reserves_ibfk_2), so everything is fine.
> 
> 2016-01-11 17:01 GMT+00:00 Bortel, Gary :
>> Hmmm...
>> 
>> Using "SHOW CREATE TABLE course_reserves" returns...
>> 
>> . . . PRIMARY KEY (`cr_id`), UNIQUE KEY `pseudo_key` 
>> (`course_id`,`ci_id`), KEY `course_id` (`course_id`), KEY 
>> `course_reserves_ibfk_2` (`ci_id`), CONSTRAINT 
>> `course_reserves_ibfk_1` FOREIGN KEY (`course_id`) REFERENCES 
>> `courses` (`course_id`), CONSTRAINT `course_reserves_ibfk_2` 
>> FOREIGN KEY (`ci_id`) REFERENCES `course_items` (`ci_id`) ON 
>> DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT 
>> CHARSET=utf8 |
>> 
>> The course reserves function is not enabled on this instance and 
>> both course_reserves and course_items are empty. Could it be 
>> updatedatabase.pl is expecting that function to be enabled and 
>> those tables to contain at least one item? I hate to admit it, 
>> but I don't see a line 10584 in updatedatabase.pl so it's 
>> difficult for me to determine what is throwing the error.
>> 
>> 
>> gcb __
>> 
>> Gary C. Bortel Office of the Secretary of State, Washington
>> State Library gary.bor...@sos.wa.gov 360.570.5588
>> 
>> Washington State Library: Empowering 21st Century Washington
>> 
>> 
>> -Original Message- From: Koha 
>> [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Jonathan 
>> Druart Sent: Monday, January 11, 2016 8:24 AM To: 
>> koha@lists.katipo.co.nz Subject: Re: [Koha] Koha upgrade 3.18.11 
>> --> 3.20.07
>> 
>> Hi Gary,
>> 
>>> DBD::mysql::db do failed: Can't create table 
>>> 'koha_library.#sql-4b9_42' (errno: 121) at 
>>> /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase
.pl
>>>
>>> 
line 10584.
>> 
>> I would say that the foreign key on course_reserves has not been 
>> created. You should check the data in course_items (some don't 
>> have a correspondence in course_reserves).
>> 
>>> DBD::mysql::db do failed: Duplicate entry '1-self_checkout'
>>> for key 'PRIMARY' at 
>>> /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase
.pl
>>>
>>> 
line 10614.
>> 
>> You can forget this one, you already had the self_checkout 
>> syspref in your database.
>> 
>> Regards, Jonathan
>> 
>> 2016-01-11 16:02 GMT+00:00 Bortel, Gary 
>> :
>>> I am seeing two MySQL errors thrown when trying to update from 
>>> 3.18.11 --> 3.20.07. Are these benign or something about which 
>>> concern should be raised?
>>> 
>>> The installation here is Ubuntu 14.04.3 with a multi-tenant 
>>> package install of Koha. Mysql  Ver 14.14 Distrib 5.5.46, for 
>>> debian-linux-gnu (x86_64) using readline 6.3
>>> 
>>> . . . . Upgrade to 3.20.00.002 done (Bug 5010: Fix OPACBaseURL 
>>> to include protocol) Upgrade to 3.20.01.000 done (Koha 3.20.1) 
>>> Upgrade to 3.20.01.001 done (Bug 9942: Privacy is correctly 
>>> set) Upgrade to 3.20.01.002 done (Bug 13993: Correct 
>>> orderstatus for transferred orders) Upgrade to 3.20.02.000
>>> done (Koha 3.20.2) Upgrade to 3.20.03.000 done (Koha 3.20.3) 
>>> DBD::mysql::db do failed: Can't create table 
>>> 'koha_library.#sql-4b9_42' (errno: 121) at 
>>> /usr/share/koha/intranet/cgi-bin/insta

[Koha] Mail Configuration in Koha

2016-01-12 Thread Ganesha H

Hi Everyone,
 I am Ganesha working as Librarian in Pvt Corporate Company. I have
installed Live DVD of  koha 3.22 in Ubuntu 14.04. I have uploaded data and
i started circulation also , but am unable do the Mail configuration  we
have our own domain and official mail. how to configure it , I have
installed Exim4 & Postfix .


-- 
Regards

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

Re: [Koha] Koha upgrade 3.18.11 --> 3.20.07

2016-01-12 Thread Frédéric Demians

> I assume checkouts and returns continue to work. (There's no way to verify
> since the checkout information doesn't appear.) This does, however, make it
> difficult for them to renew materials for patrons.

Yes, no visual feedback but it works.

> Any suggestions?

The 3.20 package will be updated, fixing this bug, this week-end. In the
meantime, if you want, you can apply a quick fix following this procedure:

- Access your Koha server with shell.

- Locate the file 'checkouts' in your local Koha installation. It is in 'svc'
  subdirectory of the Koha home directory.

- Change your working directory to the directory containing 'checkouts'.

- Run this command:

  wget -O checkouts http://tinyurl.com/zg6ukte

  It retrieves a valid 'checkouts' program.

Kind regards,
-- 
Frédéric DEMIANS
http://www.tamil.fr/fdemians
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Reminder: General IRC meeting 13 January 2016

2016-01-12 Thread Katrin Fischer

Hi all,

just a quick reminder of the Koha General IRC meeting on

13 January 2016 at 20:00 UTC

http://wiki.koha-community.org/wiki/General_IRC_meeting_13_January_2016

Hope to see you there :)

Katrin


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

[Koha] Show analytics

[Koha] System treating patron secondary email as mandatory and complaining even with valid email address

Re: [Koha] System treating patron secondary email as mandatory and complaining even with valid email address

Re: [Koha] Issue Report

Re: [Koha] Koha upgrade 3.18.11 --> 3.20.07

Re: [Koha] Koha upgrade 3.18.11 --> 3.20.07

[Koha] Mail Configuration in Koha

Re: [Koha] Koha upgrade 3.18.11 --> 3.20.07

[Koha] Reminder: General IRC meeting 13 January 2016

9 matches

Site Navigation

Mail list logo

Footer information