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

Zebra: the 'elements zebra::snippet' doesn't work
by Tajoli Zeno 11 Jan '17

11 Jan '17

Hi all, I trying to check my indexes in Zebra. My setup: OS: Debian jessie Koha: 3.20.7 [manual install] Zebra: 2.0.61 [install from IndexData repo] Format: UNIMARC Probably the fact that I use unimarc is relevant but I don't understand where. I do the debug described here: http://wiki.koha-community.org/wiki/Troubleshooting_Zebra#Why_does_a_search… The result of a working search is: Diagnostic message(s) from database: [25] Specified element set name not valid for specified database -- v2 addinfo 'zebra::snippet' but my ../etc/zebradb/retrieval-info-bib-dom.xml is correct: <?xml version="1.0" encoding="UTF-8"?> <retrievalinfo xmlns="http://indexdata.com/yaz"> <retrieval syntax="unimarc" name="F"> <backend syntax="xml" name="marc"> <marc inputformat="xml" outputformat="marc" inputcharset="utf-8" outputcharset="utf-8"/> </backend> </retrieval> <retrieval syntax="unimarc" name="B"> <backend syntax="xml" name="marc"> <marc inputformat="xml" outputformat="marc" inputcharset="utf-8" outputcharset="utf-8"/> </backend> </retrieval> <retrieval syntax="xml" /> <retrieval syntax="xml" name="index"/> <retrieval syntax="xml" name="marc" identifier="info:srw/schema/1/marcxml-v1.1"/> <retrieval syntax="xml" name="marcxml" identifier="info:srw/schema/1/marcxml-v1.1"/> <retrieval syntax="xml" name="zebra::*"/> </retrievalinfo> Do I need to check in other places for the setup of ' zebra::snippet' ? Bye Zeno Tajoli -- Zeno Tajoli / SVILUPPO PRODOTTI/ - Automazione Biblioteche Email: z.tajoli(a)cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)

5 13

INSTALL.debian is outdated
by Jonathan Druart 27 Nov '16

27 Nov '16

2015-11-11 22:37 GMT+00:00 Robin Sheat <robin(a)catalyst.net.nz>: > Aparrish schreef op wo 11-11-2015 om 08:13 [-0700]: >> I followed the official instructions: >> http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=INSTALL.debian;hb… > > We need to delete those, they're from 2012 and are super out of date. Shall we 1) delete them, 2)replace them with the content of the wiki page or 3) just put a link to the wiki page?

12 23

Introduce the use of Grunt or Gulp?
by Owen Leonard 13 Oct '16

13 Oct '16

I would very much like to start using some kind of build tool for front-end assets in Koha. The ones I've encountered are Grunt and Gulp: Grunt: http://gruntjs.com/ Gulp: http://gulpjs.com/ I have some experience with Grunt, and have heard good things about Gulp. Has anyone else used either in their non-Koha projects? Adopting them would introduce a little more complexity to the process of making client-side changes to Koha, and to be honest I'm not sure of the right way to incorporate the tools into our workflow. What I see as the advantages: - Automatic linting, minification, and concatenation of CSS and JS - Potentially, automatic compression of images and contruction of image sprites - Overall performance improvements from the above Disadvantages: A new process to learn for those wanting to contribute front-end modifications. A new set of dependencies for front-end developers (Node.js etc). If there is interest I'd be happy to submit a patch introducing the process to the OPAC as a demonstration. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

10 22

How do we find consensus on interface changes?
by Owen Leonard 06 Oct '16

06 Oct '16

Do we need a procedure for getting consensus on Koha interface changes? I'm thinking about this issue in part because of a couple of interface changes I've been working on. One for Bug 16421: Move hold edit actions into dropdown menu https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16421 (screenshot: https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=51111) ...and another for Bug 11375: Patron permission names are untranslatable https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11375 (screenshot: https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=51847) When proposing a change like that should there be a more inclusive process than getting one sign-off and one QA approval? If so, how do we decide what kind of changes require wider approval? How do we solicit opinions from a wider audience? Or is the process working well as-is? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

9 15

RFC: Retiring of the koha-patches mailing list
by Jesse 13 Jul '16

13 Jul '16

Traffic on the koha-patches mailing list has been slowly dying off over the past several years, and at this point it's almost entirely unused. Bugzilla now gives us the workflow that the patches mailing list was a part of. Does anyone have any strong objections to shutting down the mailing list? While any of us can, of course, unsubscribe, I don't feel there's a good reason to keep it running. -- Jesse Weaver

8 8

SQL92 keywords and naming columns
by David Cook 31 May '16

31 May '16

I was wondering if we have any advice for naming columns, especially TIMESTAMP columns, so I looked on the wiki and found that we're not supposed to use SQL92 keywords: https://wiki.koha-community.org/wiki/Coding_Guidelines#SQL2:_SQL92_keywords I'm not super familiar with all the keywords, but I'm confident that "timestamp" is one of those keywords. Here's the distribution on a dev Koha I have: 'created', 1 'created_on', 2 'date', 1 'dateadded', 1 'date_uploaded', 2 'dtcreated', 1 'lastmodified', 1 'message_date', 1 'modification_time', 1 'needed', 1 'time', 2 'timestamp', 26 'time_queued', 1 'updated', 1 'upload_timestamp', 2 'validated', 1 'valid_until', 1 I thought I'd check out DATETIME as well. Interestingly, there is a DATETIME column named "timestamp" as well: 'datearrived', 1 'datereviewed', 1 'datesent', 1 'datetime', 1 'date_approved', 1 'date_created', 3 'date_due', 2 'date_modified', 1 'date_run', 1 'issuedate', 2 'itemlost_on', 2 'lastreneweddate', 2 'last_modified', 1 'last_run', 1 'returndate', 2 'sharedate', 1 'start_time', 1 'suspend_until', 2 'timeclicked', 1 'timestamp', 1 'withdrawn_on', 2 It seems undesirable to use timestamp for things like "upload_timestamp" and "message_date" as well, as TIMESTAMP will automatically update when that row is updated as per these conditions: http://dev.mysql.com/doc/refman/5.7/en/timestamp-initialization.html. Anyway, something to think about. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595

2 1

More problems with MySQL 5.7
by Bernardo Gonzalez Kriegel 30 May '16

30 May '16

Hi, testing things on MySQL 5.7 - Koha 3.22, found a new problem: memberentry.pl: DBD::mysql::st execute failed: Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'kohadev.categories.categorycode' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by ... This comes trying to add a patron after fresh install, 3.22+marc21+all sample data Can we change sql_mode for Koha? Regards Bernardo -- Bernardo Gonzalez Kriegel bgkriegel(a)gmail.com

5 4

Koha Community Newsletter: May 2016
by kohanews 28 May '16

28 May '16

Fellow Koha users: The Koha Community Newsletter for May 2016 is here: https://koha-community.org/koha-community-newsletter-may-2016/ 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

POC of a new plugin system
by Julian Maurice 27 May '16

27 May '16

Hi all, A couple of months ago, we talked about how great it would be to have a more powerful plugin system (thread subject was "Country-specific forks" [1]). The current implementation have some problems. For instance, it's not possible to properly manage plugins with a VCS (bug 15879 [2] try to address this issue) Alex and I have started to write a new plugin system, as an attempt to fix the problems of the current implementation. It's still in a very "alpha" status, but we would like to hear what you think of it. Code is in BibLibre repository, branch koha-module-poc: http://git.biblibre.com/biblibre/kohac.git Features: * VCS-compatible (every directory under the modules directory and containing a module.yaml file is a module) * Allow modules to define custom "URL routes" (see module/router.pl) * Allow modules to modify the intranet top menu (so they can add a link to their custom routes) * Allow modules to have their own TT include files and TT plugins A sample module was made to demonstrate these features: http://git.biblibre.com/biblibre/koha-module-LoremIpsum.git This module creates a new page which display some "lorem ipsum" text fetched from loripsum.net, and add a link to this page in the intranet top menu. Very basic but it shows how it works. Quick start: 1. git remote add biblibre http://git.biblibre.com/biblibre/kohac.git 2. git checkout -b koha-module-poc biblibre/koha-module-poc 3. installer/data/mysql/updatedatabase.pl 4. misc/devel/update_dbix_class_files.pl 5. mkdir /path/to/modules 6. Edit $KOHA_CONF and add a line <modules_dir>/path/to/modules</modules_dir> 7. cd /path/to/modules && git clone http://git.biblibre.com/biblibre/koha-module-LoremIpsum.git LoremIpsum (note: the directory's name is important) 8. Go to Administration > Modules 9. Enable the module LoremIpsum 10. You should now see a new link in the top menu Final note: we would like to work on it during the hackfest in Thessaloniki, so if you are interested, let us know! [1] http://lists.koha-community.org/pipermail/koha-devel/2016-February/042382.h… [2] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15879 -- Julian Maurice <julian.maurice(a)biblibre.com> BibLibre

4 5

16.05.00-beta tagged
by Brendan Gallagher 26 May '16

26 May '16

Hi All - I have tagged a beta release of 16.05. (I did not include the release notes yet - I have run them and they look pretty clean - so yay!). I have also generated a tarball but I need access to the downloads - I am in the process of getting that worked out). The plan is that on Friday - I'll roll a RC1. I will be releasing on May 26th. (If you see something that I have missed - please don't hesitate to talk to me) Thanks, Brendan -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Headquarters: Santa Barbara, CA - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info(a)bywatersolutions.com

3 4