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

Elasticsearch < 2.x support
by Tomas Cohen Arazi 27 Apr '17

27 Apr '17

Hi, I would like to ask what would the support status will be in 17.05 for Elasticsearch 1.x (and maybe 2.x). According to the official docs [1], 1.x is already deprecated, and 2.x will be supported until 2018-02-28. I propose deprecating ES 1.x support officially, and also remove it from kohadevbox. Maybe something to discuss next dev meeting, but I suppose there's no point supporting unsupported versions. Regards [1] https://www.elastic.co/support/eol -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

5 4

schema.koha-community.org not updated
by Paul Poulain 27 Apr '17

27 Apr '17

Hi, We just discovered that schema.koha-community.org has not been updated since december. Can it be fixed ? (it's really annoying for master) -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

1 0

Koha Developers IRC Meeting Tomorrow
by Nick Clemens 26 Apr '17

26 Apr '17

Hello Koha community! In case any of you didn't read to the end of Jonathan's email (and if you didn't you really should) tomorrow is the next developers meeting: The next dev IRC meeting is tomorrow, April 26th at 13UTC https://wiki.koha-community.org/wiki/Development_IRC_meeting_26_April_2017 Local time and date conversion here: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I… This will be the last meeting before feature slush so come one and come all, tell us what you need, tell us how you want to help, or just come and lurk and watch the sausage get made :-) -Nick

1 0

What's on in koha-devel #12
by Jonathan Druart 25 Apr '17

25 Apr '17

Hello librarians and developers, My last email got a lot of interest and people do not stop contacting me to help us, it's fantastic! Heh, no, just kidding. But I am still willing to help you! Whenever you are ready, just let me/us know! The next release is on its way. We are in the final stretch, I will summarize in this email what needs to be done in the next month. = Release dates = Kyle published the different dates of the Koha 17.05 release: May 5 - Feature Slush May 12 - Feature Freeze, String Freeze, 1st Draft of Release Notes May 19 - Release Beta, 2nd Draft of Release Notes May 26 - Final Release May 27 - Champagne! What does it mean? * Feature slush - enhancements that have not been marked as Passed QA at this time will not be considered for the release * Feature freeze - no new enhancements will be pushed to master, only bug fixes! * String freeze - only bug fixes without string changes will be pushed to master If you want one of our awesome features waiting for testing to be present in this new release, you should warm the sandboxes up for the next 10 days! = New stuffs pushed (or almost) = == Hea v2 == The production server (https://hea.koha-community.org) has been updated last week. The Koha side code (bug 18066) has been pushed to master and should be backported into the next stable releases (16.11.07, 16.05.13 and 3.22.21). What's new? * Ability to share the information at library level instead of installation level. If you have more than one library defined in your Koha installation, you will be able to share the URL, country and geolocation of each library * Configuration page in the administration module to define what you want to share with the community (Home › Administration › Usage statistics - admin/usage_statistics.pl) * On the hea website your Koha installation will be linked to one public page where you will see all the public information we collect * The database of the website has been cleaned to remove the duplicate and test entries The screenshots I have done during the development: Koha side: New page to configure the info to share: https://pageshot.net/opGCLAZFt0s1HVzp/pro.kohadev.vm (with libraries info) https://pageshot.net/SKTFZgr40EKg6fge/pro.kohadev.vm (without libraries info) Hea side: New layout for the homepage: https://pageshot.net/GGKbBZlZwxpXuCoi/localhost View "see all libraries" (existing one): https://pageshot.net/2XplbZXFFr9rLNJS/localhost View "see libraries by country": https://pageshot.net/G5czRcqh47WFIfRD/localhost View "see libraries on a map": https://pageshot.net/Xa4qW3Vc4MclrEhO/localhost View "public view for a library" (to show libraries what is public): https://pageshot.net/7whCONhkPuJUUxDP/localhost I invite you all to take a look at the configuration page and share with us the information you want to be public. You can find the "Terms and Conditions" on github https://github.com/joubu/hea-app/blob/v2/Terms_and_Conditions.md (Todo: link it from the hea website and Koha!) == Onboarding tools == The onboarding tool (bug 17855) is not pushed yet to master but is Passed QA and should be part of the next release. It adds new steps at the end of the installation process, to create different kinds of data and ease the first contact. You will be able to create a first library, patron category, item type, circulation rule and a patron with superlibrarian permission. Note that another patch (bug 17942) will arrive soon to refresh the style of the web installer interface. = Patches waiting for love = == Automatically convert SQL reports (urgent) == Since we have bug 17196 (Move marcxml out of the biblioitems table) pushed into the next release, we absolutely need bug 17898 (Add a way to automatically convert SQL reports) too. It is waiting for testing and is really easy to test and QA. This patch will help librarians to update SQL reports after the move of the marcxml field out of the biblioitems table. == Permissions for lists (urgent) == The aim of bug 18228 is to make the permissions for list easier to use and understand. However as it will remove complexity, it may remove a feature you are using. If you are using complex permission system to manage the lists you should take a look at this bug from comment 19. As Marcel already asked on the mailing list twice, this is the LAST CALL. I am going to QA it before the feature slush if nobody disagrees. == Facet configurable for Elastic == If you want to get a new Elastic search enhancement in the next release, take a look at bug 18235. It adds a new configuration area to configure facets. = Technical discussions = I would like to rework our background jobs. They do not work under Plack and it is a pity (see bug 15032). If anybody already did that in the past or has a clear idea on how to implement a job queue using TheSchwartz, gearman or others, please let me know. Unfortunately I do not have much time at the moment to explore the different options and play with them. = Tools for devs = I have added a new commit to the apply_on_cascade branch of my git-bz github repo: https://github.com/joubu/git-bz/commit/7afcfdb8a55384e79405ae44a697c36fa5f5… It modifies the behaviour of `git bz attach -e` when there are several patches to attach. The edit will be effective on the first attachment only. Indeed most of the time I just want to change the status and obsolete the patches and not to edit the commit messages. Just revert it if you do not want this behaviour. If you want to help testing bugs before the release, take a look at this search: https://frama.link/Koha_Needs_Signoff_bugs It shows all the opened bugs with a patch attached. They are bugs and new enhancement, are sorted by severity. Pick them from the top :) The next general IRC meeting is on May 3rd, 20 UTC. https://wiki.koha-community.org/wiki/General_IRC_meeting_03_May_2017 The next dev IRC meeting is tomorrow, April 26th at 13UTC https://wiki.koha-community.org/wiki/Development_IRC_meeting_26_April_2017 Hope to see your there! Cheers, Jonathan

1 0

[Koha] Koha 3.22.20 security release
by Julian Maurice 24 Apr '17

24 Apr '17

The Koha community is proud to announce the release of Koha 3.22.20. This is a security release and contains several bugfixes. If you are running 3.22.x it is strongly recommended to upgrade. The full release notes are available at https://koha-community.org/koha-3-22-20-security-release/

1 0

Update of SQL files transaltion for 17.05 and bug 18039
by Tajoli Zeno 19 Apr '17

19 Apr '17

Hi to all, Now 17.05 is near, we need to think how to transalte SQL files. In fact we have a huge change with bug 18039: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18039 So, what do we do ? Do you want 18039 inside 17.05 or not ? IMHO we don't have the resources to insert it into 17.05 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)

3 3

Call for news: April 2017 Newsletter
by kohanews 14 Apr '17

14 Apr '17

I'm collecting news for the April 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

RDF Dereferencing/tracing/following links
by David Cook 13 Apr '17

13 Apr '17

Hi all, The key to Linked Data is obviously the links, but I dont think any of us quite know how the links actually work. In theory, I imagine having a record (ie a set of triples), in a local triplestore, which links to records available on the Internet. Periodically, those records are downloaded, and stored in a local triplestore as a cache. Then we somehow follow the links as they are stored in our local triplestore and have a set of string literals which we can show to users on a web page. In practice, I dont know how that would work. I can see us getting a list of record subjects in our local triplestore, and then iterating through each one to download the links in its objects. But I dont know where wed put that content. I also dont know if wed recurse into that content to follow more links or not. Lets say that we store that content in named graph called cache. When it comes time to re-trace the links for our list of record subjects, how do we know what local content to delete? In theory, we could use the URI from the object, but many records contain many subjects, so even if we did delete that subject from cache, we havent deleted the other subjects that it links to internally in the triplestore. Im going to ask around to see if anyone can enlighten me. Im hoping Petter might be able to shed light on how Oslo Public Library makes it work, especially in the context of ls.ext interfacing with Koha! David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

1 0

Roles for Koha 17.10
by Kyle Hall 12 Apr '17

12 Apr '17

Hey all, it's about that time of year again! I've created a skeleton wiki page for the Koha 17.10 roles! I've left it nearly all TBD so if you want to continue your role, please update this page! https://wiki.koha-community.org/wiki/Roles_for_17.11 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 )

4 5

Linked Data Discussion from Hackfest
by Joy Nelson 11 Apr '17

11 Apr '17

Here's a quick recap of the linked data discussion we had at Hackfest in Marseille. It's a two part email: a little linked data background by me and technical discussion by Nick Clemens. Thanks! joy & nick Joy Nelson I gave a brief presentation on linked data and the benefits and potential challenges inherent in moving towards a linked data system. It was based loosely on the presentation given at KohaCon 2016 which can be viewed here: https://www.slideshare.net/talljoy/kohacon2016 We discussed some of the challenges in linked data. One of those is "Choice of Linked Data Vocabulary". In the U.S. the Library of Congress is developing BibFrame as a MARC replacement. Ideally, the system created would be 'vocabulary agnostic'. The Koha linked data system should allow users the ability to utilize one of many vocabularies or *any* vocabulary they wish. (bibframe, bf:lite, schema.org, dublin core, etc) Identifying the purpose of Linked Data is another area that needs discussion and some consensus. How do libraries envision themselves using this kind of data/system? -Do we create triplestores converted from MARC to store and allow those stores to be crawled? Thereby making a collection visible on the web in search results. -Do we concentrate on creating a system that allows for libraries to connect their data to other libraries, data stores external or internally? For example, Is the goal to link our authors and subject tags to URIs on the web that we can pull in to Koha and display more information to the user? -Do we create linked data URIs for special libraries (museums, academic institutions) to provide to other institutions and allow others to link into their system to gather data to display to their users? Linked Data is a fundamental shift in how we think about our data and how we will use that data. It is a much more cooperative venture in cataloging that will provide benefits to both staff and patrons. Nick Clemens I presented the basic work I have done on implementing a triplestore backend for Koha which can be found on github here: https://github.com/bywatersolutions/bywater-koha-devel/tree/RDF The code is very basic so far and does a few things: 1 - Implements Koha::RDF::Store as a base for which all individual backend implementations will be built 2 - Adds a beginning implementation of RDF::Trine to allow storage and retrieval of RDF triples 3 - A very basic form on the intranet details page to enter a predicate and subject (assuming the URL of the details page) as the object The code is a start and begins to raise a few of concerns which I see and what we need to do to continue. I am very interested in developing Koha/RDF in a way that is backend agnostic and allows for differing front end implementations. The next steps I see are: 1 - We must agree on a common set of subroutines that any backend will support. They will require basic CRUD and options for retrieving in various formats 2 - We will need to develop endpoints: A SPARQL endpoint, and REST endpoints for CRUD, and OAI endpoints 3 - We need to decide on how we will mint and serve URIs - we could continue to use the current details URLs and add parameters for format to supply triples or xml, however, for things like works and authors we will need some method of linking. Links with parameters are not as 'cool' as named or numbered URIs but provides the ability for linking our data out to other resources, making it crawlable, and internally linking. Once we can agree on building a base together, than we can all proceed to develop in different directions as we see fit and provide various options that can all be pursued without conflict or duplicated effort. -- Joy Nelson Director of Migrations ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software Office: Fort Worth, TX Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>

1 0