Re: [Koha] Setting up Koha for the 1st Time

[अभिषेक नागर Abhishek Nãgar]

Barcode may be same as Accession Number you might already have those.

On Wed 27 Mar, 2019, 07:10 ,  wrote:

> Hello,
>
> Can anyone tell me how you establish the barcode structure you would
> like to implement when you are setting up Koha for the first time?
>
> Allen in Butte
> ___
> 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] Setting up Koha for the 1st Time

[abrazier]

Hello,

Can anyone tell me how you establish the barcode structure you would 
like to implement when you are setting up Koha for the first time?


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

[Koha] Adding memcached to Koha

[Tom Hanstra]

Where am I missing the documentation for adding memcached to Koha?

I don't currently have it installed but would like to try it. Where can I
find instructions on how to properly add the software and configure it and
then configure Koha to use it?

Tom

-- 
*Tom Hanstra*
*Sr. Systems Administrator*
hans...@nd.edu


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

Re: [Koha] Hardware Koha 18.11.03

[Mark Tompsett]

Greetings,

200 administrative users?! Simultaneously? If so, I would go with more than 
4GB. As has always been said, more memory is never bad. However, I do think 
the 2 CPU, 50GB Drive Space VM would otherwise do. Your problem will not be 
hosting the data. Your problem will be accessing the data.

I typically assume 100MB per simultaneous user + 2GB for OS + 10KB* items 
(not biblios, items) * 4.

It has generally been my experience there is a 100MB footprint for a Koha 
access with default Apache, no special tweaks. And while the memory leaks do 
recover over time, they don't recover quickly. But who has the time to 
figure out how to configure Apache even more optimally?!

And while you probably can run your OS for less than 2GB, OS's do strange 
things like kill processes when it starts getting tight on memory and you 
don't have swap configured.

The 10KB I believe is the maximum size of a MARC record. Ours typically run 
more like 4-5K, but we have some that are large. The 4 factor accounts for a 
full reindex, given that Zebra + MySQL + Both trying to cache. Yes, it's 
overkill. But you want some room, not squeeze and barely hobble along.

To summarize with your variable value plugged in:
Users: 100MB * 200 = 2000MB ~= 2GB
OS: 2GB
Data: 10KB * 5 * 4 ~= 2GB

I would recommend more like 6GB, and then if 200 
checkouts/searches/whatever's happened simultaneously, you will have no 
issues. You will, however, find that VM Host providers tend to like powers 
of 2, so you may need to jump to 8, which is way more than you will need.

Now, if you aren't going to have 200 people accessing your Koha all at the 
same second (i.e. okay, everyone, click search in 3, 2, 1... NOW *the sound 
of 200 simultaneous clicks*), but rather just have than many administrative 
users, and only 20 are on duty at any given time, then plug in 20, not 200. 
And then you'll see that you probably will cope okay with 4GB. You'll need 
to also consider patron OPAC searches into this equation too.

Just my suggestions.

GPML,
Mark Tompsett

-Original Message- 
From: Victor Barroso Oliveira
Sent: Tuesday, March 26, 2019 10:45 AM
To: koha@lists.katipo.co.nz
Subject: [Koha] Hardware Koha 18.11.03

what ideal configuration of a machine to use koha with 50,000 records
and 200 administrative users accessing the adm interface for loans and
returns?
CPU
Memory
HD
___
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] Hardware Koha 18.11.03

[Michael Kuhn]

Hi Victor

> what ideal configuration of a machine to use koha with 50,000 records
> and 200 administrative users accessing the adm interface for loans and
> returns?
> CPU
> Memory
> HD

Personally I would suggest a virtual machine with 2 CPUs, 4 GB RAM and 
50 GB disk space on one partition. Using Debian GNU/Linux 9 as the 
operating system. Also think about another place to regularly save your 
backups (for example your local machine or any other host).


Many providers offer such virtual machines for less than 60 Euros per 
year, for example here:


https://contabo.com/?show=vps

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] [EXTERNAL] Doubts cataloguing serial items

[Hernandez, Heather]

Hi, Rubeno--

Your questions are not silly at all--I'm sure there are always people with
the same questions who haven't asked them yet, and serials cataloging is
never simple!

Serials change periodicity, size, publisher, title, etc., all the time, and
only when a serial is very rare & unique do we usually take the time to
note as many of these changes as we can.  Usually we mention some of these
changes in the bibliographic record.  Since you ask many specific questions
about size and pagination, here are some options, but I'm happy to address
other changes, too, if you'd like!

Usually the pagination of specific issues and volumes can be ignored unless
the serial is very rare & unique.  Changes in size are very common.  So
usually these are usually addressed in a 300 field with a range, like this:
300 _ _ volumes : $b illustrations (some color) ; $c 29-37 cm
In the subfield c, the smallest height and the tallest height of all the
issues you have is noted.
If the issues are wider than they are taller, and then change in size, you
might have something like this:
300 _ _ volumes : $b illustrations (some color) ; $c 29 x 32 cm to 37 x 45
cm

Then in your item records, it doesn't really matter what size they are
unless they are shelved in different areas--your 952 $c might have these
locations.  And your 952 $h might then just note the volume/issue
numbering, e.g.:
952$c Per $h v.1 no.4 (Apr. 1954) Annual review issue
952$c Per Oversize $h v.10 no.7 (July 1967)

In our catalog, e.g.:
952$c Stacks $h v.10 (1954)
952$c ff $h v.12 (1956).

We put information in the 952 $z (public note) that might be useful in this
case such as, "Poor condition."

With serials, and their frequent changes, I think it is important to
balance how much time you spend on accounting for the changes in your
catalog records with how much cataloging & data entry you have to
do--putting in enough detail is important for identifying and finding the
right serial, but you can easily spend lots of time trying to track every
little change, and then never get the next serial done...:)

Hope this is helpful!  Cheerio,
h2
~~
Heather Hernandez (she, her, hers)
Technical Services Librarian
San Francisco Maritime National Historical Park Research Center
2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA  94123-1284
415-561-7032, heather_hernan...@nps.gov
Library catalog: http://keys.bywatersolutions.com/
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Hardware Koha 18.11.03

[Victor Barroso Oliveira]

what ideal configuration of a machine to use koha with 50,000 records
and 200 administrative users accessing the adm interface for loans and
returns?
CPU
Memory
HD
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] LDAP authentication problem

[Lichtsteiner Patric (lici)]

Thanks a lot for the help from all of you.
Just as a reference, if somebody with the same problem searches in the archive 
of this mailinglist:

To enable ldap to a active directory in koha:

In the file /etc/koha/sites//koha-conf.xml
 1
 
   server.zhaw.ch
   OU=unit,DC=zhaw,DC=ch
   1
   1
   0
   1
   %s...@zhaw.ch
   0
   
  
  
  
  
  
  T
  A
   
 

It is needed that there is a Library with the code “T” and a Patron category 
with the code “A”.

Next, you have to restart the following daemons:
/etc/init.d/koha-common  restart
/etc/init.d/memcached restart

Best,
Patric

> On 18 Mar 2019, at 16:55, Lichtsteiner Patric (lici)  wrote:
> 
> Hi all,
> 
> We are currently evaluating koha for our university.
> 
> Right now, I’m trying to configure ldap authentication. I followed the 
> following guides:
> https://openschoolsolutions.org/koha-ldap-setup/
> https://perldoc.koha-community.org/C4/Auth_with_ldap.html
> 
> I did the following configuration in /etc/koha/sites/ name>/koha-conf.xml
> 
> 1
> 
>   ldap://ldap.domain.ch
>   ou=users,DC=domain,DC=ch
>   CN=srvc-koha,OU=unit,DC=domain,DC=ch
>   somepass
>   1   
>   1 
>   1 
>   %s...@domain.ch
>   0
>
>  
>  
>  
>  
>  
>   
> 
> 
> I’m trying to login to OPAC, but get the error message "You entered an 
> incorrect username or password.” and the log file
> /var/log/koha//opac-error.log 
> is still empty.
> 
> How can I debug the ldap authentication in koha?
> 
> Best,
> Patric
> ___
> 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] Self Checkout after Login

[Barton Chittenden]

Mihai,

A staff user (i.e. a user with 'circulate' permissions) needs to log in to
sco-main.pl in order to make it available to the public.

Once available, there is a system preference called 'SelfCheckoutByLogin'
which can be set to allow users to log in using either 'Username and
Password' or 'Cardnumber'. I suspect that you would want 'Username and
Password'.

Give that a shot and see if the 'Username and Password' setting works with
Open ID.

--Barton

On Tue, Mar 26, 2019 at 8:53 AM Mihai Mihai  wrote:

> Hi all,
> we are using Google open ID to login to our Catalog or Username and
> Password.
> It works great, we have to do this since we have restricted resources
> available directly from the catalog only to our users.
> I have problem with checkout.
> Once a student logs in to OPAC and is trying to self check out the
> authenticated session will not let them access the /cgi-bin/koha/sco/
> sco-main.pl unless they user is given specific permission in system
> preferences to use the self checkout feature.
>
> Is it ok to give all patrons that need to self checkout the permission to
> do so ?
>
> Is there another approach anyone knows to such a problem ?
>
> Thank you!
> ___
> 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] Self Checkout after Login

[Mihai Mihai]

Hi all,
we are using Google open ID to login to our Catalog or Username and
Password.
It works great, we have to do this since we have restricted resources
available directly from the catalog only to our users.
I have problem with checkout.
Once a student logs in to OPAC and is trying to self check out the
authenticated session will not let them access the /cgi-bin/koha/sco/
sco-main.pl unless they user is given specific permission in system
preferences to use the self checkout feature.

Is it ok to give all patrons that need to self checkout the permission to
do so ?

Is there another approach anyone knows to such a problem ?

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

[Koha] Koha 17.11.17 release

[Fridolin SOMERS]

The Koha community is proud to announce the release of Koha 17.11.17.

This is a maintenance release.

The full release notes are available at 
https://koha-community.org/koha-17-11-17-release/


Debian packages will be upgraded in a few days.

/!\ Important /!\
I will end this maintaining with next release 17.11.18 that will contain 
only critical bugs.

Consider upgrading :D

Regards,

--
Fridolin SOMERS 
BibLibre, France - software and system maintainer
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] 18.11 - Indexing

[Katrin Fischer]

On 26.03.19 07:47, Michael Kuhn wrote:

And yes, so far (almost) everyone is using Zebra. There is a system
parameter "SearchEngine" (Zebra oder Elasticsearch) in Koha 18.11 but
it is not even shown/existing in
https://hea.koha-community.org/systempreferences

Best wishes: Michael


I think that's a simple oversight, we need to update the Hea
configuration files to cover the newer system preferences. See the bug
below for some discussion on it:

*Bug 22546*
 -
MaxFine is not recorded in HEA

Katrin

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

Re: [Koha] 648$a not correct indexing

[Katrin Fischer]

Hi Erlanda,

I found an existing bug report for the problem:

*Bug 14689*
 - Marc
field 648 does not appear in the subject index

If you add yourself CC to the bug report you will receive information on
any updates. As it hasn't been fixed in a while, you might want to
consider having someone fix it for you and submit a patch to the community.

Katrin

On 14.03.19 13:40, Erlanda Simonyan wrote:

Dear list,

The data which we saved in 648$a (2019, for exm.) in Koha versions 17.11, 
17.05, 18.11

couldn't show the results   when we search as "subject"  .

Why? Can anybody advice how to save chronological term in 648 field and  show the  
correct "subject"  search results?

Thanks,
Erlanda
___
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] 18.11 - Indexing

[Michael Kuhn]

Hi Tom

> Am I not receiving thoughts on this because everyone is using Zebra or
> because I'm just missing something obvious?  I have things working
> with Zebra. But does ElasticSearch also work?  Is it a better option
> going forward?
>
> I could use some input on this from those who have upgraded to 18.11.

You will already know
* https://wiki.koha-community.org/wiki/Elasticsearch
* https://wiki.koha-community.org/wiki/Elasticsearch_status

Paul Poulain has shared some information on 29 January 2019 here:

https://www.biblibre.com/en/blog/koha-and-elasticsearch-today/

And yes, so far (almost) everyone is using Zebra. There is a system 
parameter "SearchEngine" (Zebra oder Elasticsearch) in Koha 18.11 but it 
is not even shown/existing in 
https://hea.koha-community.org/systempreferences


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] Barcode Issue-Please Help!

[Katrin Fischer]

Hi Allen,

the suggestion made before is the same I would have made. Create an item
with the numbering you expect and see if it counts up from there. Easy
to test :)

Katrin


On 20.03.19 02:37, abraz...@buttepubliclibrary.info wrote:


We are having issues with our barcodes. They are not generating as we
expect them to and we'd like to know if anyone has any input regarding
the following issue. Here is my original message:



    While editing items that are being
    added to our collection, when we click in the field (p - Piece
    designation (barcode)) which we have always had set to (autoBarcode:
    generated in the form 1, 2, 3) we are no longer getting the
barcode we
    expect to see.

    We suspect it is now going back to barcodes that once belonged to
items
    that are now deleted (because, that earlier barcode is now
available).



A great reply from somebody in the community:


I took a look at the Koha source code, and it seems that for some
barcode types, it is using this SQL to determine where to start
generating new barcodes:

  select max(abs(barcode)) from items;

It then increments the value that it obtains this way to use as the
new barcode.

So I suspect that you could fix your problem by creating a dummy item
that has the first barcode you want to use, minus one.

Note that I am not an expert and have not tried this myself.



Has anyone tried this before? Any library out there that is making the
transition to Koha? How did you indicate where you would like to
numerically begin ordering the barcodes that come up in the
autoBarcode feature? Any help would be very appreciated!!!

Thank-you,
Allen from Butte, MT
___
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] Error upon loading a CSV file into Koha from Home > Administration > MARC frameworks

[Katrin Fischer]

Hi Peter,

did you change the file manually before reloading it?

Can you try to load a file without changing it and see if the same error
appears?

Also yo might want to try a different format, I usually prefer the ODS
export.

Hope that helps,

Katrin

On 18.03.19 08:22, Peter Lau wrote:

When we tried to import a CSV file into Koha from Home › Administration
› MARC frameworks, there’s an error message upon importing:



:8080 says



Error importing the framework TEST




OK



Just like to know how to fix the error.

Thanks & regards,

*Peter Lau*

Librarian

Tel: (852) 3977 9868 | Email: peter@yccece.edu.hk | Fax: (852) 23384320

  [image:
https://docs.google.com/uc?export=download=1wiYZQsqhNTJZjyNbLJx-6ODZyoYE5NNu=0BzpPRj4UE0XeT1R2WUt2dnhmTFBBeEpVR3dqcU5QbnF6NVg4PQ]

2 Tin Wan Hill Road, Tin Wan, Aberdeen

*YCCECE, Here We Grow Our Future | *www.yccece.edu.hk
___
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