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

Gitweb + Github?
by David Cook 05 Feb '18

05 Feb '18

Hi y'all, I know we've had a Gitweb vs Github thing going for years where GIthub is just a mirror. But I saw something interesting today on Apache Jena's Gitweb where it seems that they'd merged commits from Github into their master repo. You can see it at https://git-wip-us.apache.org/repos/asf?p=jena.git and specifically with https://git-wip-us.apache.org/repos/asf?p=jena.git;a=commit;h=466f16558b9cd1 a7a930fbb5e2844610ee8fb373. I guess it doesn't mess with the mirroring because they're not merging into the Github repositories. Rather, they're merging in from pull requests, which appear to just be a different type of git ref. I suppose that doesn't help in terms of tracking things through Bugzilla. but I thought it was interesting nonetheless and thus worth sharing. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 2

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

Koha Community Newsletter: January 2018
by kohanews 01 Feb '18

01 Feb '18

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

Cover image lookup via UPC
by Barton Chittenden 01 Feb '18

01 Feb '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 01 Feb '18

01 Feb '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 31 Jan '18

31 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

a few koha questions
by Johan Seyfferdt 25 Jan '18

25 Jan '18

Hello, we started to use Koha in December and so far very happy with it!!! I just have a few questions: Firstly, all our books we can give out and return except for one book which we gave out in December, and no we cant return it. Ps. I have already ran the fix for auto_increment problem and it didnt work sadly. The Patron has two books, one we can return the other not. Help will be greatly appreciated! If it is somehow possilbe to remove the book while it is out or remove the user, either in the web-interface or in the terminal, it will also be good! Secondly, When our librarian is adding books, she only have a list of pblishers and atohrs, and she was wondering if we can create like a dropdown menus for those fields that she doesnt have to type it every time but simply choose what she wants? Was wondering if someone can help me? Thank you so much and looking forward to hear from you Johan Seyfferdt

2 1

Clarification on build_browser_and_cloud.pl
by Barton Chittenden 23 Jan '18

23 Jan '18

The documentation for misc/cronjobs/build_browser_and_cloud.pl States > *Important* > This preference and cron job should only be used on French systems. (see https://koha-community.org/manual/18.05/en/html/16_cron_jobs.html?highlight… ) The associated OpacBrowser syspref says: Important > > This preference only applies to installations using UNIMARC at this time. ... but the script itself seems to use MARC::File::USMARC exclusively: 13 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use C4::Koha; 14 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use C4::Context; 15 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use C4::Biblio; 16 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use Date::Calc; 17 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use Time::HiRes qw(gettimeofday); 18 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use ZOOM; 19 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> *use MARC::File::USMARC;* 20 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use Getopt::Long; 21 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use C4::Log; (see http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui… ) The subroutine dewey_french obviously isn't translatable (I've filed bug Bug 20007 - build_browser_and_cloud.pl contains hard-coded text in French for thatt 173 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> sub dewey_french { 174 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> return { 175 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> "0" => "Généralités (Ouvrages généraux (encyclopédies, bibliographies, etc.) et informatique)", 176 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> "00" => "Savoir et communication", 177 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> "001.42" => "Collecte, agencement, analyse des données", 178 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> "003" => "Systémique, systèmes", 179 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> "003.1" => "Identification de système", 180 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> "003.2" => "Prévisions. Futurologie", ... The French text seems to be at cross purposes with MARC::File::USMARC, because French catalogers would probably use UNIMARC; at the same time the use of USMARC contradicts the documentation. Ideally, I'd to get the I18N *and* the marc flavor fixed so that everyone can use this, and I'd like to file bug reports that accurately show what needs to be fixed. Any clarification is welcome. Thanks, --Barton

2 2