- Koha - lists.katipo.co.nz

Fwd: FW: Recalls possible in KOHA
by Marcel de Rooy 20 Jan '22

20 Jan '22

Please see bug 19532. This feature is not yet part of Koha unfortunately. Shortly, the QA/release team will be working on it again, hopefully getting the feature in. Marcel PS Writing Koha is generally preferred on this mailing list 🙂

1 0

koha migration, simple view
by tuxflow.de 18 Jan '22

18 Jan '22

Hello, we have migrated a Koha 18.11 to a new server following these instructions: http://kohageek.blogspot.com/2015/08/move-old-koha-database-to-new.html Everything looks and works fine, only the description (normal view) of the books is not displayed. I could not find anything in the logs. At which point do I have to search? Many greetings

2 4

Need help for hiding the records in search result page in OPAC?
by Abid Fakhre Alam 18 Jan '22

18 Jan '22

Hi all, 1. When we accept or approve a suggested item purchased from the Suggestion Management Module, that item appears in the OPAC with a holding message that says "No physical items for this record". So, how can we hide those items, or how to make them not discoverable to the user in OPAC? 2. There are some magazines which we are not keeping in the library as bound volume but these magazines are visible to the user while searching in OPAC. So, how to hide those records from users or not find them in OPAC search results? -- Thanks and regards,

2 1

Time to translate: string freeze to prepare Koha 20.11.14 has begun
by Victor Grousset/tuxayo 18 Jan '22

18 Jan '22

Hi, String freeze is into effect as of now for the 20.11.x maintenance branch. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 20.11, then you must also copy it to 21.05 and 21.11. Otherwise your work will be lost for future versions. Happy translating :) -- Victor Grousset/tuxayo

1 0

SQL Report of Recently Edited Records
by Charles Kelley 18 Jan '22

18 Jan '22

Hi, all! Is it possible to get a SQL report of recently edited records? I looked on the Koha wiki, but I didn't see one. Thanks, all! -- よろしくお願いします。 -- 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] mnogojazyk(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

2 1

How to import record from ABCD to Koha
by Russel G. P. Shihepo 17 Jan '22

17 Jan '22

Hallo, Does anybody perhaps have experience with the migration of data records from ABCD to Koha. Our library just implemented Koha as the main Library Management system. However, we would like to import our old records to Koha MARC 21. Your feedback is highly appreciated. Regards, Russel Shihepo Country Training Coordinator- VuFind Namibia

1 0

Dollar 1 -- Which Version?
by Charles Kelley 17 Jan '22

17 Jan '22

Hi, all! I manage a library which has a lot of East Asian books. We are applying the RDA cataloging standard, which specifies {dollar}1 when transcribing kanzi, kana, and hangul. Most of our records are coded with [dollar]1, however, because I thought I recalled that even though {dollar}1 is the current cataloging standard, [dollar]1 is the Koha convention. Now, of course, a few records have turned up with {dollar}1. So which is it in Koha? brackets [dollar]1 braces {dollar}1 I'd like to know before I correct the wrong set of records. Many thanks, all! -- よろしくお願いします。 -- 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] mnogojazyk(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

1 0

RabbitMQ is using a lot of virtual memory
by Isabel Pineda 17 Jan '22

17 Jan '22

Hi. I have just seen that my server is using a lot of virtual memory recently and that RabbitMQ is the process which is using most of it (more than 3 GB). Before I try and make changes on my own, I would like to ask if someone can give me a recommendation what to do. I'm running Koha on Ubuntu 18.04. Thank you Isabel Pineda

1 0

Linking via 830$w
by Thomas Klausner 15 Jan '22

15 Jan '22

Hi! We have encountered an interesting behaviour and are not sure if it's a bug in Koha, in our data, or something else: We have a bibliographic record A where 830$w points to another record B (to the other records' 001 value, to be precise): A: 830$w = 12345 B: 001 = 12345 When Koha renders record A, it produces a link to B, but with a bad param: http://intranet/cgi-bin/koha/catalogue/search.pl?q=rcn:12345 Changing the param from 'rcn' to 'control-number' finds the correct record: http://intranet/cgi-bin/koha/catalogue/search.pl?q=control-number:12345 We're using ElasticSearch with default mappings. Looking into those, I see that there are defintions for record-control-number (rcn) and control-number. control-number points to 001, and rcn to various 7/8nn$w fields. Now it makes sense that the search for rcn did not find the value stored in record B.001, and why chaning the search to control-number finds the record. Which leads to my question; * Should we add 001 to the fields mapped to record-control-number? * Should we use a different field than 830w$? We are quite sure that we shouldn't, as the DNB is also using 830$w: https://portal.dnb.de/opac/simpleSearch?query=9783847703389 "Beziehungen: Die Andere Bibliothek ; Bd. 338", linking to (DE-101)015935620: https://portal.dnb.de/opac/opacPresentation?cqlMode=true&reset=true&referre… * Should we change the template to produce a link using a different param? Feels wrong, becuase it does make sense to link to 'rcn' and not to 'control-number'. Also we don't want to mess with the core Koha templates... Any ideas / pointers? Greetings, domm -- #!/usr/bin/perl https://domm.plix.at for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}

3 7

Marc Staging - Failed - (UPLERR_CANNOT_WRITE) undefined
by Fairlamb, Christina 15 Jan '22

15 Jan '22

Hello all, Having an issue with the "Stage MARC records for import" tool since our latest upgrade to Koha 21.05, getting the following message: Failed - (UPLERR_CANNOT_WRITE) undefined I can see it is a permissions error but don't know where to look to fix the issue, any pointers? Thanks for the help -- Christina

2 1