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

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

Bug 17908 Authority merge omnibus
by Marcel de Rooy 14 Jan '17

14 Jan '17

Hi all, There is a lot of code to *merge* on merging authorities. (Among others, bugs 5572 and 11315 and 11700 are offering parallel solutions.) I moved all relevant reports (imo) to this omnibus, and propose a strategy there to get this moving. As a self-appointed 'feature manager' I closed and blocked a few bugs in this regard. I would like to also move some patches or copy some code to other reports while keeping the attribution to the original authors. Do you agree and would you be so kind to follow along? Other thoughts ? Thanks, Marcel

2 1

Call for news: January 2016 Newsletter
by kohanews 14 Jan '17

14 Jan '17

I'm collecting news for the January newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events -- **** one month back is the cut-off ***. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Update the SQL reports (Remove biblioitems.marcxml field)
by Jonathan Druart 13 Jan '17

13 Jan '17

Hi devs, Bug 17196 is on its way to master, that means that some SQL reports from our wiki will be obsolete. https://wiki.koha-community.org/wiki/SQL_Reports_Library#Query_MARC We need to provide to libraries the examples of equivalent reports to help them updating their custom reports. It seems very easy to update the reports from the wiki, but we will need to propose the 2 versions (with and without the biblioitems.marcxml field). As the marcxml will be moved to the biblio_metadata.metadata field, the reports are very easy to update, for instance: 1/ Simple request on the biblioitems table: SELECT biblionumber, ExtractValue(marcxml, 'count(//datafield[@tag="505"])') AS count505 FROM biblioitems HAVING count505 > 1; Will become: SELECT biblionumber, ExtractValue(metadata, 'count(//datafield[@tag="505"])') AS count505 FROM biblio_metadata HAVING count505 > 1; 2/ With info from the biblio table: SELECT biblionumber, substring( ExtractValue(marcxml,'//controlfield[@tag="008"]'), 8,4 ) AS 'PUB DATE', title FROM biblioitems INNER JOIN biblio USING (biblionumber) WHERE biblionumber = 14; Will become: SELECT biblionumber, substring( ExtractValue(metadata,'//controlfield[@tag="008"]'), 8,4 ) AS 'PUB DATE', title FROM biblio_metadata INNER JOIN biblio USING (biblionumber) WHERE biblionumber = 14; 3/ Move complex query: SELECT concat(b.title, ' ', ExtractValue(m.marcxml, '//datafield[@tag="245"]/subfield[@code="b"]')) AS title, b.author, count(h.reservedate) AS 'holds' FROM biblio b LEFT JOIN biblioitems m USING (biblionumber) LEFT JOIN reserves h ON (b.biblionumber=h.biblionumber) GROUP BY b.biblionumber HAVING count(h.reservedate) >= 42; Will become: SELECT concat(b.title, ' ', ExtractValue(m.metadata, '//datafield[@tag="245"]/subfield[@code="b"]')) AS title, b.author, count(h.reservedate) AS 'holds' FROM biblio b LEFT JOIN biblio_metadata m USING (biblionumber) LEFT JOIN reserves h ON (b.biblionumber=h.biblionumber) GROUP BY b.biblionumber HAVING count(h.reservedate) >= 42; So basilly "biblioitems" becomes "biblio_metadata" and marcxml becomes "metadata". We could almost script it! The only difficulty I see is when we will need infos from the biblioitems table, we will need to add a join on biblio_metadata. I was going to add the biblio_metadata version on the wiki, but, the first example of ExtractValue is completely wrong. It says that 2 queries are equivalent ("they are equivalent") and that "they return the whole 952 field". Which is totally wrong. The work is a bit more complex than expected apparently, this wiki page need to be updated and cleaned first. Then we will be able to provide equivalent queries. Cheers, Jonathan

1 1