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

Centralize and move to gitlab
by Jonathan Druart 08 Aug '18

08 Aug '18

Hi devs, (Spoiler: I am not talking about a move from bugzilla to gitlab for the Koha git repo) Just a quick comment: gitlab has the ability to move projects with all the issues. >From the export page of a project, they say: """ The following items will be exported: Project and wiki repositories Project uploads Project configuration including web hooks and services Issues with comments, merge requests with diffs and comments, labels, milestones, snippets, and other project entities """ So that will be easy to move (already discussed with Chris, will do in May) * koha-community-devs-users/kohadocs to koha-community/kohadocs * https://gitlab.com/koha-dashboard/koha-dashboard to koha-community/koha-dashboard And the ones from github too: * joubu/koha-misc4dev to koha-community/koha-misc4dev * Koha-Community/qa-test-tools to koha-community/qa-test-tools Then, maybe: koha-testing-docker koha-release-notes kohadevbox koha-howto The idea is to centralize our things in one place, ease the PRs and the ability to clone/fork keeping the visibility on what is the reference (account 'koha-community'). I would also like to generate a CI configuration for some of them. CI file for Koha: https://tree.taiga.io/project/joubu-koha-rm-1711/us/146 (I am going to submit that on bugzilla soon) CI file for the manual: https://gitlab.com/koha-community-devs-users/kohadocs/blob/master/.gitlab-c… Any pros/cons? Cheers, Jonathan (No troll please)

11 16

Exploration of Koha ElasticSearch implementation
by Claire Hernandez 06 Apr '18

06 Apr '18

Hi, I want to share a work with you. I knew we can now switch SearchEngine syspref to ElasticSearch in Koha community version, but I didn't know a lot more. I explored with some BibLibre guys what we can really do, if we can propose this feature to our users. It seems there is some work to do but it would be great to have a more solid version for 18.05 if we test and fix more things, a version for early adopters who want to try it in production. I began a document where I list the gap to this version, it is a work in progress. I integrated the items identified by Nick (kidclamp) in the wiki page (Elastisearch_status). Thanks. I could have put everything in bugzilla or wiki but it wasn't ideal to me at this time. Depending your feedback I can make it better. https://docs.google.com/spreadsheets/d/10VUKvIYZjlbJhE-oCLmInLe601su6vIRBRC… Notes about tabs: - Way to 18.05 : I wanted it "macro functionnal", but currently it lists features or issues that may be too small. I tried to evaluate the work in "complexity point", "1" can be one developper day or maybe more or less; - Questions : can be used as a faq, I dropped my questions, sometimes I answered myself and other time someone else answeredme; - Queries and behaviours : we did a lot of work to implement Solr in Koha (at BibLibre, it begun in 2011) and an advanced search version is always maintained. I think it can be asked, so I pasted a list of queries we work with, it is expected to be different, it is just examples; - Pros : quick list of advantages for ElasticSearch in Koha Please, feel free to read, add lines, add questions or whatever. I am often available on #koha (@clrh). Claire.

2 2

Write good bug report titles and commit messages
by Jonathan Druart 04 Apr '18

04 Apr '18

Hi devs, I would like to do a little reminder about the bug report titles and commit messages. For bugs: The bug report title must shortly tell what the *bug* is, whereas the commit messages must tell what the *fix* does. Sometimes they are not related at all. For instance: - bug report titles: "Feature X is not working correctly when Y is enabled", "Click on button 'Save' does not save the record", "Saving stuff on screen X does not work", "This script generates error logs", "Mystake is misspelled in this script", "Behaviour X no longer work as expected" etc. - commit messages: "Fix Feature X when Y is enabled", "Make sure behaviour is correct when button is clicked", "Remove warnings from this script", "Correct spelling of mistake in this script", "Fix regression on behaviour X" etc. For enhancements / new feature: We could have the same title and commit messages in some cases. - bug report titles: "Add new awesome feature", "Add the ability to do that", "Code is duplicated in method Koha::Stuff->method" - commit messages: "Add new awesome feature", "Add the ability to do that", "Remove code duplication in method Koha::Stuff->method" Note that "Address comment #42" is a terrible commit message. Then, I would like to standardize the commit messages a bit. We have "Bug 12345 - ", "Bug 12345: ", "Bug 12345" and "[follow-up]", "(follow-up)", "[QA Followup]", etc. I would suggest: "Bug 12345: you commit message" And reject any commit messages with only "follow-up" (or whatever how it is written), but accept "Bug 12345: (follow-up) same commit message as before" If you forgot something, even if "Bug 12345: (follow-up) This was missing" And QA follow-ups (added by QA team member): "Bug 12345: "(QA follow-up) Add/remove this stuff" I am going to suggest these change during the next dev meetings. If accepted I will change the bug report titles and commit messages before the push during few weeks, then ask authors to do it themselves (patches from new contributors will not be rejected for that reason). You should also read or re-read: https://wiki.koha-community.org/wiki/Bug_Reporting_Guidelines https://wiki.koha-community.org/wiki/Commit_messages Cheers, Jonathan

6 6

git-bz: avoid storing unencrypted passwords in gitconfig
by Julian Maurice 06 Feb '18

06 Feb '18

Hi all, I recently shared an LXD container containing my Koha dev environment, and of course I forgot to remove my Bugzilla credentials from the git config... I immediately changed it, but for that not to happen again I searched for a way to not have to store unencrypted passwords for git-bz. The result is here https://github.com/jajm/git-bz/tree/git-credential It uses git-credential, so you can theoretically use any password manager you want, as long as you can write a git-credential helper for it (I use the builtin 'cache' helper, which stores passwords in memory) I thought it might interest some people here. For more information, see the commit message at https://github.com/jajm/git-bz/commit/efb06d8fe3033a83772d0294ab5f67c7f51ea… -- Julian Maurice <julian.maurice(a)biblibre.com> BibLibre

6 10

Debian 9 support
by Tomas Cohen Arazi 01 Feb '18

01 Feb '18

Hi everyone, I wanted to highlight that Debian 9 is more used nowadays for Koha deployments, and we need to figure what to do with HTTP::OAI, which is causing constant complaints because Koha is broken with Debian 9's (and Ubuntu 16.04's). I propose we package it in our repo, or just put the code on our source tree if packaging it becomes problematic for whatever reason. Ideas? -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

4 3

Cover image lookup via UPC
by Barton Chittenden 31 Jan '18

31 Jan '18

I've been trying to find out whether pulling cover images via Universal Product Code would be possible from Amazon and Google. I did some digging; we're doing this via Syndetics and Baker & Taylor already, so the groundwork is already partially laid: Bug 14607 : Make Baker & Taylor cover images accessible by UPC as well as ISBN URL : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14607 Priority : P5 - low Assigned To : jweaver(a)bywatersolutions.com Urgency : enhancement Status : CLOSED Bug 15388 : Show Syndetics covers by UPC in search results URL : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15388 Priority : P5 - low Assigned To : nick(a)bywatersolutions.com Urgency : enhancement Status : RESOLVED What little googling I've done for Amazon seems to indicate that they have the ability to look up items and their product images via UPC, although I'm not clear if that's available across all locales. I haven't looked at Google yet. I haven't see any bugs filed for this -- has anyone else done any research on using UPC lookup for Amazon or Google? --Barton

3 4

Re: [Koha-devel] Koha hackfest in Marseille & https://reasonablegraph.org/ platform
by David Cook 31 Jan '18

31 Jan '18

Thanks for your reply, Nikos. That certainly sounds interesting. I'd like to know more about the platform, although I won't be making it to the hackfest in Marseille this year. How does RG handle Linked Data relationships? Say I was entering in a place of publication and wanted to use dbpedia's entry for New York City. I would provide the URI but what happens after that? Do I add a local triple to describe that external resource using a schema supported by RG, or does it fetch the RDF document from the remote server and let me decide what to import or transform? If you can direct me to the appropriate demo, I'd love to look more at how your system handles Linked Data. I think I've gone as far as there is to go with RDF on its own, but curious how existing systems are handling the links to external resources. Cheers, David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- From: Nikos Papazis [mailto:papazis@altsol.gr] Sent: Thursday, 1 February 2018 1:01 AM To: David Cook <dcook(a)prosentient.com.au>; 'Paul Poulain' <paul.poulain(a)biblibre.com>; koha-devel(a)lists.koha-community.org Subject: Re: [Koha-devel] Koha hackfest in Marseille & https://reasonablegraph.org/ platform Dear David, regarding the github repo of ReasonableGraph (RG): until now the sole developers of the RG platform are us. There isn't any community yet. We do provide the platform with l-GPL license in our installation, which are listed on the platform's website and are located in Greece. So we do not allocate any resources in maintaining a public repo. If a community arises, we will switch our private repos to the public one and do there our commits. This is the reason why our github repo seems abandoned. We too have implemented BIBFRAME 2.0, among other standards. Primarily for proof of concept and for providing demo installations. Our purpose is to demonstrate the fact that different ontologies can be quite easily implemented on our platform. Which has configuration files for describing any ontology and the entry forms necessary to manage it. For all our demo instalations, we provide full access to anyone who might be interested. Having said that, I come to your question regarding the use or possible value of RG for the KOHA ecosystem. We feel that RG can offer 2 valuable functions: 1) a real-time backend that transforms MARC21 or UNIMARC collections into FRBR or BIBFRAME datasets (or any other semantic model) 2) and the ability to simultaneously manage/annotate/enrich the collection on both standards. So it can act as the necessary tool for adopting the new standards. Helping to keep the MARC expertise and tools and at the same time experiment with the new standards. And the same time it allows libraries to explore the possibility of having unified repositories for all their collections (bibliographic, archival, museum, musical, etc). The demos mentioned by Paul are showcasing the above. Thanx to David and Paul for their comments. Looking forward to meeting you in Koha hackfest in Marseille Regards, Nikos PS: I am not a member of the koha-devel list yet. So please forward it there for completeness On 31/01/2018 12:52 πμ, David Cook wrote: > I'm skeptical of anything that claims to implement BIBFRAME for production, since BIBFRAME appears to still be an experimental work in progress (https://www.loc.gov/bibframe/faqs/#q09) That said, it does seem like folk like Ex Libris are trying to use BIBFRAME 2.0 in production (https://www.loc.gov/bibframe/implementation/register.html) I suppose every technology needs its early adopters. I can see why places like Oslo Public Library, the National Library of Sweden, and la Bibliothèque Nationale de France are using their own schemas though. > > The ReasonableGraph Github only seems to have 1 contributor and a handful of commits. Mostly from 1 year ago and 15 days ago. I wonder what is missing? I haven't had time to deep dive the code yet. > https://github.com/reasonablegraph > > That said, I'm intrigued by anything that claims to use Linked Data. To date, I've mostly only seen systems that use RDF stored locally. That is, that only link internally and don't resolve external links. The most interesting example of Linked Data that I've actually found is with OCLC WorldCat: http://www.worldcat.org/title/good-omens-the-nice-and-accurate-prophecies-o…. If you open the "Linked Data" section, you can see that "New York" from the top of the webpage comes from this predicate and object: library:placeOfPublication <http://dbpedia.org/resource/New_York_City>. The interesting bit is if you go down to "Related Entities", you'll see 'schema:name "New York"'. I find that interesting because http://dbpedia.org/page/New_York_City doesn't have a predicate of schema:name. So, in theory, OCLC must be converting a triple from another vocabulary into Schema.org. Either that or they provide the link as the authoritative link and ! > then just add their own local triple saying "New York". I suppose that's a possibility too. But it kind of defeats the purpose of machine readable Linked Data. But Linked Data is hard since you never know what you're going to get back from the other end. > > At this point, what could Reasonable Graph offer for Koha? > > Apologies if that sounds rude at all. I've just been thinking a lot about RDF and Linked Data for the last couple of years. > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St > Ultimo, NSW 2007 > Australia > > Office: 02 9212 0899 > Direct: 02 8005 0595 > > > -----Original Message----- > From: koha-devel-bounces(a)lists.koha-community.org > [mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of Paul > Poulain > Sent: Tuesday, 30 January 2018 11:45 PM > To: koha-devel(a)lists.koha-community.org > Cc: Nikos Papazis <papazis(a)altsol.gr> > Subject: [Koha-devel] Koha hackfest in Marseille & > https://reasonablegraph.org/ platform > > Hi koha-devel, > > I had a hangout with Nikos (in cc:) , from Reasonablegraph. > reasonablegraph is a platform (L-GPL) that is able to deal with MARC > records, transform them into FRBR / Bibframe /linked data. They made > some work with Koha (http://unioncatalog.reasonablegraph.org/?lang=en, > click on "Search" top-left) > > At the end of Nikos demo, I suggested him to come to the hackfest for a day or two, in order to present reasonablegraph to anyone interested, and talk about any possible collaboration between Koha community and reasonablegraph. He will probably come. > > That's another very good reason to come to Marseille in March :D > > -- > Paul Poulain, Associé-gérant / co-owner BibLibre, Services en > logiciels libres pour les bibliothèques BibLibre, Open Source software > and services for libraries > > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : > http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ > > > > -- AltSol team mob: +30 6974471632 office: +30 2109617148 fax: +30 2109617148 URL: http://www.altsol.gr linkedIn: https://www.linkedin.com/in/npapazis

1 0

Recent changes in our Bugzilla tracker
by Victor Grousset 31 Jan '18

31 Jan '18

Hi, Last week there have been some changes at https://bugs.koha-community.org/ Things that I noticed and miss until now are 1. No more diff view for the patches. It looked like this https://bugzilla.mozilla.org/attachment.cgi?id=8581857&action=diff 2. Can't add a tag to a comment. For example to mark it as obsolete and hide it by default to reduce the noise. Does anyone have infos about these changes? Reason, duration, other changes, etc. Cheers, -- Victor Grousset, dev support/maintenance BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Libre/Open Source software and services for libraries

3 5

Koha hackfest in Marseille & https://reasonablegraph.org/ platform
by Paul Poulain 30 Jan '18

30 Jan '18

Hi koha-devel, I had a hangout with Nikos (in cc:) , from Reasonablegraph. reasonablegraph is a platform (L-GPL) that is able to deal with MARC records, transform them into FRBR / Bibframe /linked data. They made some work with Koha (http://unioncatalog.reasonablegraph.org/?lang=en, click on "Search" top-left) At the end of Nikos demo, I suggested him to come to the hackfest for a day or two, in order to present reasonablegraph to anyone interested, and talk about any possible collaboration between Koha community and reasonablegraph. He will probably come. That's another very good reason to come to Marseille in March :D -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

2 1

Koha 17.05.08 release
by Fridolin SOMERS 25 Jan '18

25 Jan '18

The Koha community is proud to announce the release of Koha 17.05.08. This is a maintenance release. The full release notes are available at https://koha-community.org/koha-17-05-08-release/ Regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre - software and system maintainer

1 0