Re: [Koha] Loan periods

[Katrin Fischer]

Hi Alexander,

some thoughts/ideas what you could try:

For the newly acquired materials:

* You could use the "Item modifications by age" too to automatically
move them from a short term loan itemtype to a different item type using
some rules and the "age" of the items.

* You could also use the course reserves module to give them a temporary
item type that is then switched to the final one when they are removed
from the 'shelf'/course reserve.

For the databases/licenses

* I also lean towards manually entering the due date on checkout, as
Caroline suggested.  You could then summarize those under one itemtype
like 'individual loan period' or 'license/subscription' and have that
show up in the OPAC search filters. And you could use the item type to
create some "alert" on checkin/checkout to remind your staff about the
special use case.

In general we also use the item types to indicate the type of use
'reference material' or 'normal loan'. Sometimes item types and material
types overlap, but not always. You'll find that you can pretty much hide
the item type from display anywhere in the OPAC using configuration. If
you are looking for something specific, let us know.

Hope this helps,

Katrin

On 12.10.23 15:28, Wagner, Alexander wrote:

Hello!

Being pretty new to Koha I still struggle to get a solution for our loan 
periods.

I understand that Koha specifies loan periods based on `item types` and `patron 
types` and then calculates the loan period using the circulation matrix. I also 
believe I have an understanding of this matrix and I also know such concepts 
from other ILS.

However, in our library we assume that all patrons are created equal.

Now, we (currently) assume that not all books (just to take one item type) are 
created equal.

IOW in our current system we have books with a loan period of 4 weeks (usual default) while we also 
have books with a loan period of 3 days (being open 24/7 with self service checkout this is our 
`not for loan`) and others with 2 years. Currently, any patron (they are all equal) can have items 
with any of these loan periods. Eg. I got Peskin/Schroeder as as desktop reference for 2 years. 
Then go to the library during my usual working hours (10pm or so ;) and up pick Bailin/Love from 
the open shelves to prepare the next lecture and while I am there I spot this interesting "new 
piece over there" and add it to the lot not noticing that it should stay there for a week or 
so. (Telling our SIP terminal "you can not take this" will not work well, especially as 
most of our patrons would not notice the red frownie and no-one would notice the beeps at the 
entrance in the middle of the night.)

However, till here I can model most of it by creating an item type `book` along 
with `desktop reference` for the first two items. I do not yet see the new 
items shelve (a temporary location) where items stay for a week till they move 
to their permanent location with a regular loan period of 4 weeks. (IOW in our 
current system the loan period sometimes depends on temporary locations.)

Still, this requires to add a new item type for each loan period.

When it comes to databases we now have a number of different loan periods, as 
we model them as the subscription period minus some contract dependent time to 
allow for cancellation (or renewal). E.g. some are subscriptions for campus 
(real not for loan) with some contract running a year. The next contract runs 3 
years with 4 month before it's end for cancellation.

Then we have individually licensed accesses ranging from a monthly or bi-monthly period 
to years. Those are currently checked out to the patrons who have the access and we use 
the reminders as notification to our patrons ("should we renew?") and the 
renewals as a notification to us that the contract should indeed be renewed for another 
period. How would I model this in Koha? Do I really create a host of item types with 
funny names like

1 week, 2 weeks, 3 weeks, 4 weeks, 5 weeks, 6 weeks, 7 weeks, 8 weeks, 1 month, 
2 months, 3 months, 4 months, 5 months, 6 months, 7 months, 8 months, 9 months, 
10 months, 11 months, 12 months, 18 months, 24 months, 30 months, 36 months, 42 
months, 48 months, 54 months, 60 months, 66 months, 72 months, 78 months

It looks a bit messy in cataloguing but these would also show up in the OPAC 
(eg. in the advanced search limiters).

In our current system I just had a subfield on item level where I could specify 
a loan period. Do I get it right that this concept does not exist and can not 
be modeled in Koha? How can I get around this? How do others handle this? Maybe 
I need a different angle to look at it...


___

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

Re: [Koha] Cannot stage authority files in 22.11.

[Katrin Fischer]

Hi,

I've looked in bugzilla and found this bug:

*Bug 34965*
 -
Authority match failing due to possible encoding conflicts

I am not sure if it's related, but maybe something to look into.

Hope this helps,

Katrin

On 25.09.23 06:25, Raymund Delahunty wrote:

We moved from 21.11 to 22.11 recently and since then attempts to stage and 
import authority record have failed. We are using the LC-card-number index as 
the matchpoint and have tried changing the normalisation rule from None to 
Remove spaces but the stage still fails. We can stage without matching, but 
when we change the matchpoint afterwards to LC-card-number (auth 010$a) we 
receive an Error 500. We have also had a problem with diacritics in authority 
searches when using Zebra and on our test server this is solved using 
Elasticsearch which we are testing out. But ES has not resolved our auth 
staging problem. Any ideas?

Ray Delahunty
University of the Arts London



.
This email and any attachments are intended solely for the addressee and may 
contain confidential information. If you are not the intended recipient of this 
email and/or its attachments you must not take any action based upon them and 
you must not copy or show them to anyone. Please send the email back to us and 
immediately and permanently delete it and its attachments. Where this email is 
unrelated to the business of University of the Arts London or of any of its 
group companies the opinions expressed in it are the opinions of the sender and 
do not necessarily constitute those of University of the Arts London (or the 
relevant group company). Where the sender's signature indicates that the email 
is sent on behalf of UAL Short Courses Limited the following also applies: UAL 
Short Courses Limited is a company registered in England and Wales under 
company number 02361261. Registered Office: University of the Arts London, 272 
High Holborn, London WC1V 7EY
___

Koha mailing listhttp://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] [translate] Migrate Pootle to Weblate

[Katrin Fischer]

Hi,

I added some notes at the bottom of the wiki page.

Hope it helps,

Katrin

On 29.09.23 15:14, Jonathan Druart wrote:

Hello everybody,

A quick update, I am back on this and I logged the progress on the wiki:
https://wiki.koha-community.org/wiki/Translation_server_migration_weblate
If you have worked with Weblate already and know it well, please let me
know, I have a couple of questions :)

Cheers,
Jonathan

Le jeu. 13 juil. 2023 à 17:12, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> a écrit :


Hello everybody,

If you are a translator of Koha you should read this.

Pootle is dead and we should move to Weblate, which is an active and
well maintained project.
We have been setting up a test server to let translators see how it goes.
THIS IS A TEST SERVER: none of the changes will be saved!

There are some changes in how the projects are structured.
We will now have 2 projects: "koha" and "koha-manual". Each will
contain several "components".
One component in Pootle can only track on po file, which means we need
one component per po file:
https://translate.test.koha-community.org/projects/koha/ shows
https://snipboard.io/rtKdTS.jpg

It can be a bit disturbing at first, but there is this view:
https://translate.test.koha-community.org/languages/es/koha/ that
shows the progress per language: https://snipboard.io/UCJ1Ky.jpg

The big win are:
* We should no longer get "Critical errors: Python brace placeholders"
(to be confirmed)
* Translation changes will be propagated between the components of a
given project, and so between versions: if you modify a string for
23.05 it will also modify it for the other branches! (to be confirmed
as well!)

guest user (not logged in) can only make suggestions:
https://translate.test.koha-community.org/

User reviewer/6Mx1$HU*1KNbzCZV can accept suggestions.

You are welcome to test and provide feedback!

There is still a lot of work before effectively doing the migration,
but we need first to know if users/translators are happy with it!

Let us know!
Cheers,
Jonathan

PS: About the structure of the projects, I've contacted the author of
Weblate: https://github.com/WeblateOrg/weblate/discussions/9556
Next version will add a mecanism to structure components within a project!


___

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] Single Item due mail

[Katrin Fischer]

Hi,

did you check the "digest" checkbox in the messaging preferences?

The DUEDGST notice is then used and includes information on all items
becoming due.

Hope this helps,

Katrin

On 15.10.23 10:45, JITHIN N wrote:

The Item due notice mail sending as individual mails to patron for each
book. Is there any way to sent the details (Bibliographic Information) that
are due in a single mail .


With regards
JITHIN N
___

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] Single Item due mail

[JITHIN N]

The Item due notice mail sending as individual mails to patron for each
book. Is there any way to sent the details (Bibliographic Information) that
are due in a single mail .


With regards
JITHIN N
___

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