Re: [Koha] zebra utility after koha upgrade

[Mason James]

hi George
you should not need to manually add any cronjob for indexing,

in newer koha versions (like 19.05) the indexing is handled automatically



if you are having problems with indexing, its possibly due to incorrect zebradb 
file/dir permissions

check in /var to confirm that the instance's zebra files/dirs are correctly 
owned by it's koha user

___

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

Re: [Koha] zebra utility after koha upgrade

[Mason James]

On 28/10/21 2:43 am, George Mikuchadze wrote:

After successful upgrading koha from v3.22.21 to v19.05.17 zebra indexer
doesn't work in the crontab.
I have the following cronjobs:
PERL5LIB=/usr/share/koha/lib
*/5 * * * * KOHA_CONF=/etc/koha/koha-conf.xml
/usr/share/koha/bin/migration_tools/rebuild_zebra.pl -b -a -z >/dev
but after 5 minutes od adding new biblioitems they are not searched.
If I run the command in the shell:
$ KOHA_CONF=/etc/koha/koha-conf.xml /usr/share/koha/bin/migration_tools/
rebuild_zebra.pl -b -a -z >/dev
the new biblioitems are appearing in serch results.
Can anybody help me to set up a crontab for the zebra rebuild utility?
___

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


hi George
you should not need to manually add any cronjob for indexing,

in newer koha versions (like 19.05) the indexing is handled automatically


you should see 2x 'daemon' jobs per koha instance.
 1 job for zebra searching, 1 job for zebra indexing


# /etc/init.d/koha-common status
● koha-common.service - LSB: Start required services for each Koha instance
   Loaded: loaded (/etc/init.d/koha-common; generated)
   Active: active (running) since Thu 2021-10-28 03:05:50 UTC; 3min 13s ago
 Docs: man:systemd-sysv-generator(8)
    Tasks: 4 (limit: 3394)
   Memory: 152.1M
   CGroup: /system.slice/koha-common.service
   ├─29544 daemon --name=dev1-koha-zebra --pidfiles=/var/run/koha/dev1/ 
--errlog=/var/log/koha/dev1/zebra-error.log 
--output=/var/log/koha/dev1/zebra-output.log --verb…
   ├─29547 /usr/bin/zebrasrv -v none,fatal,warn -k 1024 -f 
/etc/koha/sites/dev1/koha-conf.xml
   ├─29620 daemon --name=dev1-koha-indexer 
--errlog=/var/log/koha/dev1/indexer-error.log 
--stdout=/var/log/koha/dev1/indexer.log --output=/var/log/koha/dev1/indexer-ou…
   └─29622 /usr/bin/perl 
/usr/share/koha/bin/migration_tools/rebuild_zebra.pl -daemon -sleep 5

___

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

[Koha] Fine Minimum vs. Fine Grace Period

[Charles Kelley]

Hello, all!

My library will be migrating to its ILS in the next few months. I am
setting up the circulation and fine rules. Mostly they're reasonably
straightforward. So far, I have had few problems. A little experimentation
on the development machine has answered my questions.

In the dim, dark, misty past, one of the libraries I worked in charged
fines; none of the rest has. Instead of a grace period per se, that library
management set up a minimal overdue fine. If a patron checked out a book
and returned it three days late, the system would calculate the fine at the
going rate. If the calculation were at or over the minimum, the patron
would incur the fine; otherwise, the fine would vanish.

Of course, it amounted to a grace period; at least, that's how the
patrons referred to it. I can't tell you the two years it took to get the
terminology consistent among the staff and patrons so that the collective
consciousness would treat it differently.

So, just as a matter of curiosity, how does Koha make a library handle
a minimal fine in the circulation rules? Do you arithmetically calculate
the number of days (or other period) it would take for an overdue work to
breach the minimal fine, and enter that value into the Fine Grace Period?
Or is there another way?

By the way, my library doesn't charge fines, so this is moot to us.

Thanks, all!

-- 

気を付けて。 /ki wo tukete/ = Take care.

-- Charles.

Charles Kelley, MLS
PSC 704 Box 1029
APO AP 96338

Charles Kelley
Tsukimino 1-Chome 5-2
Tsukimino Gaadenia #210
Yamato-shi, Kanagawa-ken
〒242-0002 JAPAN

+1-301-741-7122 [US cell]
+81-80-4356-2178 [JPN cell]

mnogoja...@aol.com [h]
cmkelley...@gmail.com [p]

linkedin.com/in/cmkelleymls 
Meeting Your Information Needs. Virtually.
___

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

Re: [Koha] Off-site storage

[Charles Kelley]

Hello, Elaine Bradtke !

In our latest exchange, on 27 Oct. 2021 at 08:00 [JST], I received this
from you through the Koha Discussion Group:

Belatedly I discovered that only one status will display and the
restricted status
> field hides 'not for loan'. Though the information is still there in the
> staff interface. I don't think this will be a problem. But you folks on
> the coal face may feel differently.
>

I'm curious: Is that the problem you are trying to solve, to show
offsite storage, a status, and the restriction-of-access or not-for-loan
value in the same column?

By the way, I did notice that the OPAC does display only one status
while the staff mode displays all of the ones assigned. I guess what is
displayed follows a hierarchy of states. And some persons may be concerned
about information overload because if you erect too many signs, people --
staff and patrons alike -- stop reading.

   Well, nice exchange.

-- 

気を付けて。 /ki wo tukete/ = Take care.

-- Charles.

Charles Kelley, MLS
PSC 704 Box 1029
APO AP 96338

Charles Kelley
Tsukimino 1-Chome 5-2
Tsukimino Gaadenia #210
Yamato-shi, Kanagawa-ken
〒242-0002 JAPAN

+1-301-741-7122 [US cell]
+81-80-4356-2178 [JPN cell]

mnogoja...@aol.com [h]
cmkelley...@gmail.com [p]

linkedin.com/in/cmkelleymls 
Meeting Your Information Needs. Virtually.
___

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

[Koha] Koha 20.05.17 released

[Victor Grousset/tuxayo]

Hello! :)

The Koha Community is happy to announce the release of Koha 20.05.17

The full release notes can be found at:
https://koha-community.org/koha-20-05-17-released/

Debian packages should be available shortly.

Thanks to everyone involved :)


Cheers,

--
Victor Grousset/tuxayo
___

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

Re: [Koha] Avoiding duplicate items during MARC staging/import

[Bales (US), Tasha R]

I'm writing to retract this question.  I don't think the solution I'm looking 
for (being able to remove and replace all item records during a MARC load) 
exists.

To solve my duplicate item records issue, I plan to delete all items that lack 
barcodes, and reload with barcodes.  I'm in between ILS's and am trying to keep 
Koha in sync with changes made in Millennium, where some records lack barcodes. 
 This is why I cannot use Koha item record number as a match point.

Thank you.

Tasha Bales
Enterprise Services
http://isesi.web.boeing.com/

From: Bales (US), Tasha R
Sent: Wednesday, October 27, 2021 11:20
To: koha@lists.katipo.co.nz
Subject: Avoiding duplicate items during MARC staging/import

Is there a cheat sheet for staging and loading MARC records?

I keep getting hung up and am creating duplicate item records during loads, 
despite continuing to read the manual closely, and experimenting with different 
options.

I think my problem is with my expectations (coming from Millennium ILS), and my 
interpretation of the menu options that begin with "Add items..."  I only want 
to add items if they don't already exist.  What I really want to do is to 
replace all 952 fields with the new fields I am loading.  However, in practice, 
the option to "Replace items if matching bib was found (only for existing 
items)" doesn't seem to accomplish this.  If my file is a mix of existing and 
new records, it looks like my new records aren't getting items created, 
presumably because those items didn't already exist.

I don't think it will be useful to share all the scenarios and options I've 
tried.  Just hoping someone else has similarly misinterpreted the instructions 
and may have created a "cheat sheet" for which options to select to avoid 
duplicates.

It may be useful to add that the sample record I am working with at the moment 
has no barcode numbers in any of its attached items.  I'd like to be able to 
reload this MARC record and wipe all the items out, replacing with whatever 
items are in my new MARC file, but my actions so far have only loaded more 
items, resulting in duplicates.

Thanks for your time,


Tasha Bales
Enterprise Services
http://isesi.web.boeing.com/

___

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

Re: [Koha] Records visible to those who login

[Katrin Fischer]

Hi,

OpacHiddenItems hides the items and records if all items are hidden.
This worked independent from if you are logged in or not. Then
OpacHiddenItemsExceptions can make items visible for certain patron
categories again, which is an information only available if you are
logged in.

Hope that explains,

Katrin

On 27.10.21 21:57, Cab Vinton wrote:

I looked at those settings but didn't see where logged in status could be
used as the controlling factor.

What am I missing?

Cab Vinton
Plaistow Public Library
Plaistow NH


On Wed, Oct 27, 2021, 11:56 Tomas Cohen Arazi  wrote:


You can do it!

You could use a combination of OpacHiddenItems and
OpacHiddenItemsExceptions.



___

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

___

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

Re: [Koha] Records visible to those who login

[Cab Vinton]

I looked at those settings but didn't see where logged in status could be
used as the controlling factor.

What am I missing?

Cab Vinton
Plaistow Public Library
Plaistow NH


On Wed, Oct 27, 2021, 11:56 Tomas Cohen Arazi  wrote:

> You can do it!
>
> You could use a combination of OpacHiddenItems and
> OpacHiddenItemsExceptions.
>
>
___

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

[Koha] Avoiding duplicate items during MARC staging/import

[Bales (US), Tasha R]

Is there a cheat sheet for staging and loading MARC records?

I keep getting hung up and am creating duplicate item records during loads, 
despite continuing to read the manual closely, and experimenting with different 
options.

I think my problem is with my expectations (coming from Millennium ILS), and my 
interpretation of the menu options that begin with "Add items..."  I only want 
to add items if they don't already exist.  What I really want to do is to 
replace all 952 fields with the new fields I am loading.  However, in practice, 
the option to "Replace items if matching bib was found (only for existing 
items)" doesn't seem to accomplish this.  If my file is a mix of existing and 
new records, it looks like my new records aren't getting items created, 
presumably because those items didn't already exist.

I don't think it will be useful to share all the scenarios and options I've 
tried.  Just hoping someone else has similarly misinterpreted the instructions 
and may have created a "cheat sheet" for which options to select to avoid 
duplicates.

It may be useful to add that the sample record I am working with at the moment 
has no barcode numbers in any of its attached items.  I'd like to be able to 
reload this MARC record and wipe all the items out, replacing with whatever 
items are in my new MARC file, but my actions so far have only loaded more 
items, resulting in duplicates.

Thanks for your time,


Tasha Bales
Enterprise Services
http://isesi.web.boeing.com/

___

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

Re: [Koha] Records visible to those who login

[Tomas Cohen Arazi]

You can do it!

You could use a combination of OpacHiddenItems and
OpacHiddenItemsExceptions.

El mié., 27 oct. 2021 6:01, Toni Afandi  escribió:

> Dear All,
>
> If we make OPAC accessible to the public, could we hide some records and
> make them visible to those who login.
>
> Thank you in advance,
>
> *Toni Afandi*
> *Librarian*
> *STT SAAT*
> *(Southeast Asia Bible Seminary)*
> Jl. Bukit Hermon No 1, Tidar Atas
> Malang, Jawa Timur 65151
> Indonesia
> www.seabs.ac.id
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

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

Re: [Koha] Records visible to those who login

[Elaine Bradtke]

Yes, it's possible.  Helpful video here:
https://bywatersolutions.com/education/hiding-items-on-the-opac
Elaine
VWML 



On Wed, Oct 27, 2021 at 2:01 AM Toni Afandi  wrote:

> Dear All,
>
> If we make OPAC accessible to the public, could we hide some records and
> make them visible to those who login.
>
> Thank you in advance,
>
> *Toni Afandi*
> *Librarian*
> *STT SAAT*
> *(Southeast Asia Bible Seminary)*
> Jl. Bukit Hermon No 1, Tidar Atas
> Malang, Jawa Timur 65151
> Indonesia
> www.seabs.ac.id
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

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

Re: [Koha] Records visible to those who login

[Eric Phetteplace]

Hi Toni,

This is a good question. I don't think Koha is able to hide some records
from unauthenticated users. There is a "Restricted Page" which is only
visible to users who are logged in:
https://koha-community.org/manual/21.05/en/html/opacpreferences.html#restricted-page

Why do you want to hide some records? It might be possible to use the
Restricted Page to accomplish your goals. If you have some private
information related to certain records, you could collect it all on the
Restricted Page, then link to that page from the records. Not the most
convenient workaround but I thought I would point that out.

Best,

ERIC PHETTEPLACE Systems Librarian, Libraries (he/him)

ephettepl...@cca.edu | o 510.594.3660 (cca)

5212 Broadway | Oakland, CA | 94618

CCA is situated on the traditional unceded lands of the Ohlone peoples.

Black-owned bookstores in Oakland: Ashay by the Bay
, Marcus Books


:(){ :|: & };:


On Wed, Oct 27, 2021 at 2:01 AM Toni Afandi  wrote:

> Dear All,
>
> If we make OPAC accessible to the public, could we hide some records and
> make them visible to those who login.
>
> Thank you in advance,
>
> *Toni Afandi*
> *Librarian*
> *STT SAAT*
> *(Southeast Asia Bible Seminary)*
> Jl. Bukit Hermon No 1, Tidar Atas
> Malang, Jawa Timur 65151
> Indonesia
> www.seabs.ac.id
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

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

[Koha] zebra utility after koha upgrade

[George Mikuchadze]

After successful upgrading koha from v3.22.21 to v19.05.17 zebra indexer
doesn't work in the crontab.
I have the following cronjobs:
PERL5LIB=/usr/share/koha/lib
*/5 * * * * KOHA_CONF=/etc/koha/koha-conf.xml
/usr/share/koha/bin/migration_tools/rebuild_zebra.pl -b -a -z >/dev
but after 5 minutes od adding new biblioitems they are not searched.
If I run the command in the shell:
$ KOHA_CONF=/etc/koha/koha-conf.xml /usr/share/koha/bin/migration_tools/
rebuild_zebra.pl -b -a -z >/dev
the new biblioitems are appearing in serch results.
Can anybody help me to set up a crontab for the zebra rebuild utility?
___

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

[Koha] Records visible to those who login

[Toni Afandi]

Dear All,

If we make OPAC accessible to the public, could we hide some records and
make them visible to those who login.

Thank you in advance,

*Toni Afandi*
*Librarian*
*STT SAAT*
*(Southeast Asia Bible Seminary)*
Jl. Bukit Hermon No 1, Tidar Atas
Malang, Jawa Timur 65151
Indonesia
www.seabs.ac.id
___

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