- Koha - lists.katipo.co.nz

What's on in koha-devel #11
by Jonathan Druart 05 Apr '17

05 Apr '17

Hello librarians and developers, Not much has happened this month in terms of development. Things are going very slowly at the moment, despite the hackfest in Marseille. We see a lot of new people on the mailing list and the IRC channel asking for questions, but we need more people to be involved in the discussions and the signoff process. There are hundreds of people on this list, you need to know that the Koha community needs you to make the project moving forward. I know that nobody has enough time, but you know one hour per week of even per month can help a lot. It is very easy, fun and interesting :) = How to get involved? = The first action would be to join us on the #koha IRC channel and the koha-devel mailing list. Start by presenting yourself, where do you come from, what do you do? For how long have you been using Koha? How do you think you can help? Attend meetings! We have two kinds of monthly meeting. There is a general one to talk about koha-related stuffs, and the development meeting to talk about technical stuffs. It is important for the community to have a place to be all together and try to make things move. If you are a librarian, we need you to tell developers the directions they need to go. Open bug reports It is important to know that everybody can open new bug reports on our bug tracker (https://bugs.koha-community.org) It is useful for the development team to know the new bugs. And it is also important for you to search for known bugs. A lot of bugs are known from developers but we do not know how to fix them because we are waiting for feedbacks from users. The dashboard (http://dashboard.koha-community.org) is very helpful to know the "hot" bugs that need to be fixed/tested/QAed. The "Overall bug traker health status" section displays the number of new bugs that are important to follow, make moving. If a developer submits a patch for the bug you opened, try and test it! Test bugs Here is how you can really makes things move for the community. You become involved in the development process and make the Koha project better. Sandboxes (https://wiki.koha-community.org/wiki/Sandboxes) are available to test patch easily. You do not need to install anything on your computer and do not need any technical skills. If you are a Koha user, you can test patches! Write patches If you are a developer or have a minimum of technical skills you can write your own patches and fixes bugs or develop new feature. Our dedicated wiki page (wiki.koha-community.org/wiki/Submitting_A_Patch) will guide you over the different steps. It is very easy to get a development environment using KohaDevBox ( https://github.com/digibib/kohadevbox) Start with small patches :) = Refactoring = If you have read my previous "what's on in koha-devel" emails, you may have noticed I talked a lot of "refactoring" bugs. And maybe you do not know what it is and what it brings. The Koha codebase is aged/old, and has grown very quickly since 2006. Since the last few years the development team decided to make the code more robust and slow the integration of patches, getting a stronger integration process. That's why we need to have at least one tester validating the patches, then one QAer to review the patch technically and finally the Release Manager to push it. That's mean 4 independent persons for a single patch. That made our codebase stronger and less regression prone. Some part of the code now needs to be rewritten, and it is why I have focussed on the "refactoring" work over the last year. The goal is to rewrite modules of Koha, step by step. It cleans the code, makes it more readable, reduces the number of lines, centralise the responsibilities, homogenise the code, fixes bugs, adds test coverage, etc. On the mid-long term it means a modern application, easy to maintain, robust, flexible. The bugs will be easier to fix, the enhancements will be quicker to develop and so less expensive. Do you start to understand how it is useful? So yes, it's boring to test because it does not bring anything new to the interface, but the project needs it. If you have been using Koha for months or years, it made you save money, it makes you happy to use it and you love it. If you already got answer from people on the mailing lists or the IRC channel, it's time to say thank you, by getting involved! If you have any specific questions on how to get involved, you can join me on the IRC channel or by email. I can help and guide you if necessary. A developer that loves Koha but needs help, Jonathan

2 1

koha ejournals management
by LIS PROF 04 Apr '17

04 Apr '17

Hi We are trying to understand how koha can manage ejournals renewal. We tried to add details in acquisitions as well as tried to renew in serials but since it is ejournal there are no issues which needs to be maintained. How libraries are managing ejournals renewal in koha. REG lLIS

1 0

Re: [Koha] Moys Classification on Koha
by Toibin, Muireann 03 Apr '17

03 Apr '17

Hi Nasiru, We use Moys classification for the legal materials in our library. It's a classification scheme for legal materials that can be used in conjunction with either the Library of Congress or Dewey Decimal Classification. (We use DDC.) I can't imagine that you will need any modifications in Koha - we haven't. Best regards, Muireann. _________________________ Muireann Tóibín Librarian Revenue Library & Research Centre D’Olier House, D’Olier Street, Dublin 2, D02 XY31, Ireland. +353 (0) 1 6747 930 muireann.toibin(a)revenue.ie ------------------------------ Message: 3 Date: Fri, 31 Mar 2017 10:44:14 +0100 From: Nasiru Yakubu <mnyakubu(a)gmail.com> To: koha-user <koha(a)lists.katipo.co.nz> Subject: [Koha] Moys Classification on Koha Message-ID: <CAMZDM8NY0O6qGxv2rQ4_czhL4NPqU1M0=pLw8KEbi40ex2QRoA(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Hi all, We recently started a school of law and their Librarian has requested for the Moys classification scheme to be implemented in Koha. Can any one please point me in the right direction? -- M Nasiru Yakubu mobile: +234 818 747 4227 and +234 806 601 8785 Skype: nasyak ------------------------------ Message: 4 Date: Fri, 31 Mar 2017 11:30:45 +0100 From: Ian Bays <ian.bays(a)ptfs-europe.com> To: koha(a)lists.katipo.co.nz Subject: Re: [Koha] Moys Classification on Koha Message-ID: <a9d19cd0-8592-2a73-d203-9a4b84749cfa(a)ptfs-europe.com> Content-Type: text/plain; charset=utf-8; format=flowed Hi. Looks like Moys might be OK with Library of Congress: https://en.wikipedia.org/wiki/Moys_Classification_Scheme Good luck. On 31/03/2017 10:44, Nasiru Yakubu wrote: > Hi all, > > We recently started a school of law and their Librarian has requested for > the Moys classification scheme to be implemented in Koha. > > Can any one please point me in the right direction? > -- Ian Bays Director of Projects, PTFS Europe Limited Content Management and Library Solutions +44 (0) 800 756 6803 (phone) +44 (0) 7774 995297 (mobile) +44 (0) 800 756 6384 (fax) skype: ian.bays email: ian.bays(a)ptfs-europe.com ------------------------------ Please note that Revenue cannot guarantee that any personal and sensitive data, sent in plain text via standard email, is fully secure. Customers who choose to use this channel are deemed to have accepted any risk involved. The alternative communication methods offered by Revenue include standard post and the option to use our (encrypted) MyEnquiries service which is available within myAccount and ROS. You can register for either myAccount or ROS on the Revenue website. Tabhair faoi deara nach féidir leis na Coimisinéirí Ioncaim ráthaíocht a thabhairt go bhfuil aon sonraí pearsanta agus íogair a gcuirtear isteach i ngnáth-théacs trí r-phost caighdeánach go huile is go hiomlán slán. Meastar go nglacann custaiméirí a úsáideann an cainéal seo le haon riosca bainteach. I measc na modhanna cumarsáide eile atá ag na Coimisinéirí ná post caighdeánach agus an rogha ár seirbhís (criptithe) M'Fhiosruithe a úsáid, tá sí ar fáil laistigh de MoChúrsaí agus ROS. Is féidir leat clárú le haghaidh ceachtar MoChúrsaí nó ROS ar shuíomh gréasáin na gCoimisinéirí.

1 0

Problem with saving changes to MARC records
by lukasz.mesek＠alingsas.se 02 Apr '17

02 Apr '17

Hello, I have a problem with saving corrections in MARC records imported to our catalog. During importing through Z39.50 all the changes done to record, like framework and filling of empty fields or changing them, I can save and they stay as I wish them to be. But when I go to the record next time, saving of corrections is not possible. I can only change the framework then but all the corrections done to MARC fields disappear. What could it be a reason? Med vänlig hälsning Lukasz Mesek Vuxenbibliotekarie Alingsås bibliotek lukasz.mesek(a)alingsas.se

2 1

Re: [Koha] Separate hold queues?
by BRANNON, CHRISTOPHER 01 Apr '17

01 Apr '17

Andreas, Our consortium simply does not show the patron where they are in the queue. We find it to be misleading, due to the number of items available to be placed on hold, local holds priority, cancellations, and high demand loan periods that kick in. Plus there is the rare occasion a hold is shifted. Showing that information is just inviting patrons to try and manage what the system is doing. We do let them know how many requests are on the record, but that is it. We never let them know where they are in the queue, even if they ask. This has worked very well for us. ___________________________ Christopher Brannon IT Coordinator 702 E Front Ave Coeur d'Alene, ID 83814 (208)769-2315 Ext. 456 cbrannon(a)cdalibrary.org www.cdalibrary.org Keep tabs on us at: -----Original Message----- Hi all! We are at Stockholm University Library experiencing some difficulties with how Koha is currently handling hold queues, and are considering development in this area. Are there any other libraries who are experiencing similar issues (see below), and would be interested in the development of separate hold queues? Or have an opinion on whether this would be a good/bad idea? In Koha today it is possible to limit the fulfilment of holds per branch (same pick-up location as home/holding library) and item type. For us, it makes most sense to view this as several hold queues for one bibliographic record. For example: a person queuing for a book from the textbook collection (item type = ”TC”) isn’t actually queuing for books for the general collection (item type = ”GC”). But Koha handles this as one big queue. This isn’t a problem for the holds per se, as Koha only fetches the book that has the right criteria to fill the hold (i.e. the correct item type or home/holding library) but it has proven to be an issue for our patrons. As Koha displays it as one big queue, it might seem that the queue is much bigger that it actually is. This has confused a number of patrons, and have discouraged others from placing holds. Continuing our example: a book has three patrons on hold for item type GC, when a new patron adds a hold for TC. This makes this person number four in the queue in Koha today, making the patrons believe that they will have to wait weeks or months for the book (in our library TC is 7 days, GC 28 days) when in reality it is only one week. For us, this would better be described as two queues: One with 3 patrons on hold (General collection) One with 1 patron of hold (Textbook collection) The same is true for hold fulfilment that require pick-up location to be the same as home/holding library (i.e. hold fulfilment per branch). Say a public library also have a school library in it’s organization, that is a special case where books from the other libraries should not be sent to the fulfil holds, or vice versa. As in our example above it would be better to display queues separately so 5 holds at the main library won’t discourage a student from placing a hold on that same book at the school library. So my question is basically, is there are other libraries out there who are using any of these hold fulfilment features (or would like to), and would want to see a new feature to separate/split hold queues? Or who could see the benefit of such a feature. Please note that separate hold queues would of course only come in effect if any system preference that limits hold fulfilment is set to allow. Also, this would not effect holds to pull. I look forwards to hearing people’s opinion about this! Best regards, Andreas ________________________________ Andreas Hedström Mace Librarian Stockholm University Library Stockholm University 106 91 Stockholm Tel: +46 (0) 8 16 49 17 su.se/english/library<http://su.se/english/library>

1 0

Circulation - Notices (over due) - help
by SATISH 01 Apr '17

01 Apr '17

Hi, Currently with Koha 16.5/Package Installation/ Ubuntu 14.04 Desktop / I am unable to retrieve details in Overdue Notice(ODUE) template for auto generation of email. For Checkout, Checkin, Advance Notice, Due Reminder, books/items details are retrieved. But not sure, why the same code in not retrieving for Overdue Notices. It comes with blank email. Overdue Template contains Title: <<biblio.title>>, by <<biblio.author>> Accession No: <<items.barcode>> Check out (Borrowed) date: <<issues.issuedate>> Due Date: <<issues.date_due>> Can you please help me to fix/ or is there any reason, I meant, I want to retrieve above said details in Overdue Notices. With Thanks. Satish MV Librarian Govt. Engineering College, Hassan. Karnataka. --

2 2

Koha Community Newsletter: March 2017
by kohanews 01 Apr '17

01 Apr '17

Fellow Koha users: The Koha Community Newsletter for March 2017 is here: https://koha-community.org/koha-community-newsletter-march-2017/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. Thanks! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Help - Email lookup while using lists
by Suresh Kumar Tejomurtula 31 Mar '17

31 Mar '17

Dear all, Is there any option to lookup for sending emails using lists or cart in koha opac. What iam looking is if I type a name when trying to send email, will it look for similar names or emails. Iam looking for an option like that of lookup used in check-out. -- Regards T. Suresh Kumar

2 2

Koha 3.22.19 security release
by Julian Maurice 31 Mar '17

31 Mar '17

The Koha community is proud to announce the release of Koha 3.22.19. This is a security release and contains several bugfixes. If you are running 3.22.x it is strongly recommended to upgrade. The full release notes are available at https://koha-community.org/koha-3-22-19-security-release/

1 0

Koha 16.11.06 released
by Katrin 31 Mar '17

31 Mar '17

The Koha community is proud to announce the release of Koha 16.11.06. This is a maintenance release of 16.11 and contains 9 bugfixes. The full release notes are available at https://koha-community.org/koha-16-11-06-release/ Packages will be available soon.

2 1