- Koha-devel - lists.koha-community.org

Horizon to Koha migration
by Peter Fanter 25 Jan '17

25 Jan '17

Hello, has someone experience, or provide me with documentation, with what one must do, in order to make a migration, from Horizon to Koha? We have access only to a Horizon database, so we can only run sql queries, and we must get back, as much as possible info needed. I know the Koha part, i lack the knowledge, of how to extract info from Horizon, what tables exist, what info they have, how combine tables, etc Thank you very much

2 1

Matthias working on Coral <> Koha interface
by Paul Poulain 25 Jan '17

25 Jan '17

Hello Koha & Coral lists, I'm happy and proud to announce that in the next 3 months, Matthias will work full time on Coral <> Koha interface. He can be dedicated to this task thanks to 3 companies that joined their strength and money to make this possible: Ebsco (45%), BibLibre (40%) and ByWaterSolutions (15%) He will start by playing the new features and installer of Coral 2.0. Then he will improve the specs I've written (and already sent to some/most of you. If you want them, just ask). Then he will code. Things he will work on : * rebase the Coral <> gokb interface and officially submit it for inclusion into Coral. That will be a first step and framework for later inclusion of Ebsco KB. * work on linking Coral and Koha acquisitions modules: share organizations/vendors, budgets, create basket in Koha from a given Coral acquisition workflow, share bibliographic records when relevent. Some general guidelines we will follow: Coral: * we will keep things as ILS-agnostic as possible. It means we will use webservices, and never access the Koha DB from Coral * Every "linked" feature will be activated through the configurations files. If not activated, Coral users will see no change. That's important for "Coral without Koha" * We will have to add some fields to store the links between ILS and Coral data. Koha: * We will mostly add webservices (restful, of course), related to acquisition (vendors, budget, baskets, ...). * We will have to add some fields to store the links between Koha and Coral data. Hopefully, at the end of those 3 months, we should have a working version 1, not complete, that could be improved for an easier use. Our long term goal is to have a fully integrated solution. -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

4 3

Coding Guidelines: POD Documentation
by Nick Clemens 25 Jan '17

25 Jan '17

Hello Koha developers, At the last developers meeting there was some discussion about guidelines for requiring POD during QA. Our current guideline is here: https://wiki.koha-community.org/wiki/Coding_Guidelines#PERL13:_POD The discussion centered on a few questions: 1 - Should (basic) POD be required when making a small change to a module that has no existing POD. The answer to this seemed to be generally yes, and Barton volunteered to assist. Anyone else wanting to help add POD is more than welcome to join him :-) 2 - Where should POD go? Inline or after __END__ Please offer your opinion if you feel strongly. As I am cutting it close to sending before the meeting I think we can push off adding/updating the guideline until the February meeting. Thanks! Nick (kidclamp)

3 2

Koha Meeting Reminder
by Nick Clemens 24 Jan '17

24 Jan '17

Hi All, Just a friendly reminder that the next Koha Development IRC meeting is tomorrow, 25 January 2017, at 13UTC Here is a converter for local date and time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I… The agenda is on the wiki, please add anything you wish to discuss https://wiki.koha-community.org/wiki/Development_IRC_meeting_25_January_2017 See you there! -Nick

1 0

Koha 16.11.02 released
by Katrin 23 Jan '17

23 Jan '17

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

1 1

Patch to fix Zebra facets
by David Cook 22 Jan '17

22 Jan '17

Hi all, It would be great if https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17871 could get some love. It fixes the issue where Zebra facets aren't retrieved when using newer versions of YAZ. It's just a configuration change, so it's something I've already done locally, but it would be good to have out of the box for everyone. Just realized it doesn't have a test plan. I'll type one up now. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

1 0

Developers, expect patches to no longer apply
by Kyle Hall 20 Jan '17

20 Jan '17

Hey all, I just wanted to alert everyone to that fact that I just pushed the following bug patches: Bug 16239 - Upgrade Bootstrap in the staff client Bug 17196 - Move marcxml out of the biblioitems table I expect this will cause a good number of patches to no longer apply with hopefully trivial fixes required. Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org )

5 6

Missing patch
by Mark Tompsett 19 Jan '17

19 Jan '17

Greetings, The follow up patch from Kyle on bug 13113 is not in master and is the reason my testing in kohadevbox is failing. Could someone fix that and check previous versions too? GPML, Mark Tompsett

1 1

log file of activities for admin of koha in the library
by rania azad mohammed 18 Jan '17

18 Jan '17

Dear We are 3 admins in the library working on shifts in the library, each of us log-in during her time. I want a report or log file to see all the activities of each admin during a specific day. is there such report or file? I tried to find it using the wiki but hopeless -- *Regards,* *Rania Azad |* Library Manager Library Department http://library.auis.edu.iq/ The American University of Iraq, Sulaimani Office: *B-G-32* Ext *1219*

7 13

About defaults of indicators for auth merges
by Tajoli Zeno 18 Jan '17

18 Jan '17

Hi Marcel, I write to you and here same thoughts about defaults of indicators for auth merges. You say: "We actually need framework default indicators first to address merges crossing the authtype border correctly". As start we need to remember that indicators for Auth are different from Biblio indicators (see bug 14769). I think this true only for this specific case: auth 'A' type '1' merge auth 'B' type '2' = auth 'CC' type '3' in case auth 'A' type '1' merge auth 'B' type '2' = auth 'CC' type '1' we need to use indicators of auth 'A' The code of bug 9701 is about Biblio indicators. We need new code, in different .pl, and new columns, in different tables, for authority. Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.tajoli(a)cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)

2 3