Re: [Koha] Koha Ldap Auth

[Hector Gonzalez]

> On Jun 25, 2019, at 8:28 AM, Daniele Piccoli  
> wrote:
> 
> Il 24/06/19 21:30, Hector Gonzalez ha scritto:
>> Hi Daniele
> 
> Hi
> 
>>> On Jun 24, 2019, at 4:22 AM, Daniele Piccoli  
>>> wrote:
>>> 
>>> Software error:
>>> Error reading file /etc/koha/sites/biblioname/koha-conf.xml.
>>> Try running this again as the koha instance user (or use the koha-shell
>>> command in debian)
>> 
>> 
>> Is the file readable by koha?  Permissions should be 640, with user root and 
>> biblioname-koha as the group (if that is the group that owns koha).
> 
> The file is readable by Koha and in fact it has the correct permission
> as you said.

Ok, then try making these changes:


*IP-OF-DC* >
ou=Users,dc=*sub*,dc=*domain*,dc=*tld*
1
1
1
0
uid=%s@*sub*.*domain*.*tld*
 record field names -->
  
  
  
  YOURLIBRARYCODEinKoha
STUDENT
 


1. change the hostname to the actual hostname of the ldap server, if it is 
using ldaps, it might want to check the certificate, and that is based on the 
name.
2. remove the  and  tags, as you are using auth_by_bind.  (I don´t 
know if they are needed for  so you might want to leave that there).
3. Add a line that says: 0  which is needed 
with AD logins when you are using auth_by_bind  (sounds weird, but it works 
that way)
4. Change principal_name, the format is 
%s@*your.domain.name* which is needed with AD 
too.  It looks like an email address.
5. Add a mapping for "categorycode" with the text of the main user category 
(staff, students, faculty...)  It IS required for login, and is assigned to the 
user automatically.
6. Add the branchcode for the library.

Also, I would change the userid mapping to   which is a unique name for every user with AD.
If it still gives you trouble, check the tags above and below your ldap 
configuration, and be sure those were not affected by editing the file.

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

--
Héctor González
ca...@genac.org

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

Re: [Koha] Unwanted e-mail about UseTransportCostMatrix

[Jonathan Druart]

Hi Michael,
Restart memcached and plack to make sure the pref's value is not
fetched from the cache.
The code raising this warning is pretty trivial:

189 my $use_transport_cost_matrix =
C4::Context->preference("UseTransportCostMatrix");
190 if ($use_transport_cost_matrix) {
191 $transport_cost_matrix = TransportCostMatrix();
192 unless (keys %$transport_cost_matrix) {
193 warn "UseTransportCostMatrix set to yes, but matrix
not populated";

Le mar. 25 juin 2019 à 03:30, Michael Kuhn  a écrit :
>
> Hi
>
> Since two days I am receiving the following unwanted e-mail from my demo
> installation (running Koha 19.05.00) every hour:
>
> ##
>
> Subject: Cron cd / && run-parts --report /etc/cron.hourly
>
>
> /etc/cron.hourly/koha-common:
> UseTransportCostMatrix set to yes, but matrix not populated at
> /usr/share/koha/lib/C4/HoldsQueue.pm line 193.
>
> ##
>
> But in fact system preference "UseTransportCostMatrix" is NOT set to yes:
>
> mysql> select value from systempreferences where
> variable="UseTransportCostMatrix";
> +---+
> | value |
> +---+
> | 0 |
> +---+
> 1 row in set (0.00 sec)
>
>
> What does it mean and how can I prevent getting this unwanted e-mail?
>
> 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
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Need advice regarding removal of deleted biblio records

[Andy Boze]

Thanks, Joel.

I've been considering that. We do have a backup from immediately before 
the failed import. There have been some records added by our catalogers 
since then, but I think I can pretty easily identify them. I was just 
hoping there'd be an easy way to purge the deleted biblio records.


Andy

On 6/25/19 5:47 PM, Coehoorn, Joel wrote:

To clarify the "Go back to previous backup" idea... assuming you have a
backup that will work, the normal challenge here is circulation
transactions that took place since the bad import. This often means running
and printing an issues report before restoring, and then manually
re-entering the circulation from the impacted period, with correct due
dates, etc. If there's a lot of traffic through the library, this can be a
real pain, but it shouldn't be a problem at all for a non-circulating
library. If you don't have backups, this is the reminder that you should be
taking them.

Joel Coehoorn
Director of Information Technology
402.363.5603
*jcoeho...@york.edu *

*Please contact helpd...@york.edu  for technical
assistance.*


The mission of York College is to transform lives through
Christ-centered education and to equip students for lifelong service to
God, family, and society


On Tue, Jun 25, 2019 at 4:28 PM Paul A 
wrote:


On 2019-06-25 4:43 p.m., Andy Boze wrote:

Dear all,

I'm hoping someone can give me a bit of direction. We have a large
number of deleted biblio records (due to a failed MARC records import).
We'd like to remove the deleted records from the database as there are
somewhat more deleted records (401,000) than active records.


Why not go back to your previous backup? Quick, simple, painless.

Best -- Paul


Is there a script than can clean up deleted records? I've seen this
"Clean up database" script <


https://koha-community.org/manual/18.11/en/html/cron_jobs.html#clean-up-database

  >, but it's not what we're looking for.

If there's no script, can we safely use the MySQL TRUNCATE command on
the deletedbiblio, deletedbiblio_metadata, deletedbiblioitems and
deleteditems tables? This is a non-circulating library, so I don't think
the biblionumber would be tied to any other tables.

I'll appreciate any guidance. We're using Koha 18.11 and MariaDB 5.5.60.



___
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



--
Andy Boze, Associate Librarian
University of Notre Dame
271H Hesburgh Library
(574) 631-8708
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Need advice regarding removal of deleted biblio records

[Coehoorn, Joel]

To clarify the "Go back to previous backup" idea... assuming you have a
backup that will work, the normal challenge here is circulation
transactions that took place since the bad import. This often means running
and printing an issues report before restoring, and then manually
re-entering the circulation from the impacted period, with correct due
dates, etc. If there's a lot of traffic through the library, this can be a
real pain, but it shouldn't be a problem at all for a non-circulating
library. If you don't have backups, this is the reminder that you should be
taking them.

Joel Coehoorn
Director of Information Technology
402.363.5603
*jcoeho...@york.edu *

*Please contact helpd...@york.edu  for technical
assistance.*


The mission of York College is to transform lives through
Christ-centered education and to equip students for lifelong service to
God, family, and society


On Tue, Jun 25, 2019 at 4:28 PM Paul A 
wrote:

> On 2019-06-25 4:43 p.m., Andy Boze wrote:
> > Dear all,
> >
> > I'm hoping someone can give me a bit of direction. We have a large
> > number of deleted biblio records (due to a failed MARC records import).
> > We'd like to remove the deleted records from the database as there are
> > somewhat more deleted records (401,000) than active records.
>
> Why not go back to your previous backup? Quick, simple, painless.
>
> Best -- Paul
> >
> > Is there a script than can clean up deleted records? I've seen this
> > "Clean up database" script <
> >
> https://koha-community.org/manual/18.11/en/html/cron_jobs.html#clean-up-database
> >  >, but it's not what we're looking for.
> >
> > If there's no script, can we safely use the MySQL TRUNCATE command on
> > the deletedbiblio, deletedbiblio_metadata, deletedbiblioitems and
> > deleteditems tables? This is a non-circulating library, so I don't think
> > the biblionumber would be tied to any other tables.
> >
> > I'll appreciate any guidance. We're using Koha 18.11 and MariaDB 5.5.60.
> >
>
> ___
> 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] Need advice regarding removal of deleted biblio records

[Paul A]

On 2019-06-25 4:43 p.m., Andy Boze wrote:

Dear all,

I'm hoping someone can give me a bit of direction. We have a large 
number of deleted biblio records (due to a failed MARC records import). 
We'd like to remove the deleted records from the database as there are 
somewhat more deleted records (401,000) than active records.


Why not go back to your previous backup? Quick, simple, painless.

Best -- Paul


Is there a script than can clean up deleted records? I've seen this 
"Clean up database" script < 
https://koha-community.org/manual/18.11/en/html/cron_jobs.html#clean-up-database 
 >, but it's not what we're looking for.


If there's no script, can we safely use the MySQL TRUNCATE command on 
the deletedbiblio, deletedbiblio_metadata, deletedbiblioitems and 
deleteditems tables? This is a non-circulating library, so I don't think 
the biblionumber would be tied to any other tables.


I'll appreciate any guidance. We're using Koha 18.11 and MariaDB 5.5.60.



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

Re: [Koha] Need advice regarding removal of deleted biblio records

[Andy Boze]

Actually we did use the import tool. The server (it's running on AWS) 
choked and we had to restart it. We bumped up its capacity and 
restarted, and Koha looked like it continued to process the import where 
it left off. Unfortunately we ended up with lots of duplicate records 
(with different biblio numbers).


We tried reverting the import, but that still left a lot of records to 
delete. We deleted the records and tried importing from the previously 
staged records. Doing that, nearly all the records were duplicated. We 
reverted those imports and deleted duplicate records.


Then we uploaded the records again to stage them, rather than reusing 
the previously staged records. From the newly staged records, the import 
went smoothly. We had previously imported the same records in our test 
environment and everything had gone flawlessly. In any case, we've got a 
huge number of deleted records we'd like to eliminate from the database.


Andy

On 6/25/19 4:49 PM, Alvaro Cornejo wrote:

Hi

If you do a Marc import through the koha importing tool, you can remove the
records through the same process. You just need to check which import
process you want to remove and that's it.

Regards,

Alvaro
|-|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS
y GPRS online
   Visitenos en www.perusms.com


Le mar. 25 juin 2019 à 15:44, Andy Boze  a écrit :


Dear all,

I'm hoping someone can give me a bit of direction. We have a large
number of deleted biblio records (due to a failed MARC records import).
We'd like to remove the deleted records from the database as there are
somewhat more deleted records (401,000) than active records.

Is there a script than can clean up deleted records? I've seen this
"Clean up database" script <

https://koha-community.org/manual/18.11/en/html/cron_jobs.html#clean-up-database
  >, but it's not what we're looking for.

If there's no script, can we safely use the MySQL TRUNCATE command on
the deletedbiblio, deletedbiblio_metadata, deletedbiblioitems and
deleteditems tables? This is a non-circulating library, so I don't think
the biblionumber would be tied to any other tables.

I'll appreciate any guidance. We're using Koha 18.11 and MariaDB 5.5.60.

--
Andy Boze, Associate Librarian
University of Notre Dame
271H Hesburgh Library
(574) 631-8708
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha





--
Andy Boze, Associate Librarian
University of Notre Dame
271H Hesburgh Library
(574) 631-8708

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

Re: [Koha] Need advice regarding removal of deleted biblio records

[Alvaro Cornejo]

Hi

If you do a Marc import through the koha importing tool, you can remove the
records through the same process. You just need to check which import
process you want to remove and that's it.

Regards,

Alvaro
|-|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS
y GPRS online
  Visitenos en www.perusms.com


Le mar. 25 juin 2019 à 15:44, Andy Boze  a écrit :

> Dear all,
>
> I'm hoping someone can give me a bit of direction. We have a large
> number of deleted biblio records (due to a failed MARC records import).
> We'd like to remove the deleted records from the database as there are
> somewhat more deleted records (401,000) than active records.
>
> Is there a script than can clean up deleted records? I've seen this
> "Clean up database" script <
>
> https://koha-community.org/manual/18.11/en/html/cron_jobs.html#clean-up-database
>  >, but it's not what we're looking for.
>
> If there's no script, can we safely use the MySQL TRUNCATE command on
> the deletedbiblio, deletedbiblio_metadata, deletedbiblioitems and
> deleteditems tables? This is a non-circulating library, so I don't think
> the biblionumber would be tied to any other tables.
>
> I'll appreciate any guidance. We're using Koha 18.11 and MariaDB 5.5.60.
>
> --
> Andy Boze, Associate Librarian
> University of Notre Dame
> 271H Hesburgh Library
> (574) 631-8708
> ___
> 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] Need advice regarding removal of deleted biblio records

[Andy Boze]

Dear all,

I'm hoping someone can give me a bit of direction. We have a large 
number of deleted biblio records (due to a failed MARC records import). 
We'd like to remove the deleted records from the database as there are 
somewhat more deleted records (401,000) than active records.


Is there a script than can clean up deleted records? I've seen this 
"Clean up database" script < 
https://koha-community.org/manual/18.11/en/html/cron_jobs.html#clean-up-database 
>, but it's not what we're looking for.


If there's no script, can we safely use the MySQL TRUNCATE command on 
the deletedbiblio, deletedbiblio_metadata, deletedbiblioitems and 
deleteditems tables? This is a non-circulating library, so I don't think 
the biblionumber would be tied to any other tables.


I'll appreciate any guidance. We're using Koha 18.11 and MariaDB 5.5.60.

--
Andy Boze, Associate Librarian
University of Notre Dame
271H Hesburgh Library
(574) 631-8708
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Education meeting

[Caroline Cyr-La-Rose]

Hello everyone!

Just a quick reminder that the community education meeting is taking 
place THIS Thursday, June 27, at 14 UTC.


ByWater Solutions offered their Zoom room so that we can all meet. Click 
on this link to access it: https://zoom.us/j/545232903 You can try it in 
advance to make sure it works for you.


Here is the agenda again. And again, I invite you to email me or the 
list if you want to add points to it. :)


1. Presentation
2. Collaboration for training, propositions
 * Wiki?
 * Mailing list?
 * other means?
 * Are there things that we can share? Or things we should develop
   as a community?
3. Best practices
 * If anyone wants to share one thing that they do that works
   wonderfully, go ahead :)

See you then!

Caroline

--
Caroline Cyr La Rose, M.L.I.S.
Librarian | Product Manager

Phone: 1-833-465-4276, ext. 221
caroline.cyr-la-r...@inlibro.com 

INLiBRO | Document Technologies Specialists | www.inLibro.com 


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

Re: [Koha] Koha Ldap Auth

[Daniele Piccoli]

Il 24/06/19 21:30, Hector Gonzalez ha scritto:
> Hi Daniele

Hi

>> On Jun 24, 2019, at 4:22 AM, Daniele Piccoli  
>> wrote:
>>
>> Software error:
>> Error reading file /etc/koha/sites/biblioname/koha-conf.xml.
>> Try running this again as the koha instance user (or use the koha-shell
>> command in debian)
> 
> 
> Is the file readable by koha?  Permissions should be 640, with user root and 
> biblioname-koha as the group (if that is the group that owns koha).

The file is readable by Koha and in fact it has the correct permission
as you said.

> --
> Héctor González
> ca...@genac.org
> 
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
> 

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

[Koha] Unwanted e-mail about UseTransportCostMatrix

[Michael Kuhn]

Hi

Since two days I am receiving the following unwanted e-mail from my demo 
installation (running Koha 19.05.00) every hour:


##

Subject: Cron cd / && run-parts --report /etc/cron.hourly


/etc/cron.hourly/koha-common:
UseTransportCostMatrix set to yes, but matrix not populated at 
/usr/share/koha/lib/C4/HoldsQueue.pm line 193.


##

But in fact system preference "UseTransportCostMatrix" is NOT set to yes:

mysql> select value from systempreferences where 
variable="UseTransportCostMatrix";

+---+
| value |
+---+
| 0 |
+---+
1 row in set (0.00 sec)


What does it mean and how can I prevent getting this unwanted e-mail?

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