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

newbie would appreciate help!
by Johan Seyfferdt 08 Dec '17

08 Dec '17

Hello. Thank you for adding me to this mailing list. I have a question. I am a sysadmin in St Petersburg, Russia and we are in the process of moving to Koha. So I am a newbie :) I chosed the unimarc option as our database is in rusmarc. We have our database in .mrc format, it is about 27 000 books in cyrilic, english and german. I was able to setup koha import that database but the search function does not work. I did a lot of googling, i tried kooha 16.05, 16.11, 17.05 on Debain 8 and 9 but without avail... Any help will be truly appreciated! as i am truly stuck. Johan Seyfferdt

4 3

Update koha-misc4dev
by Jonathan Druart 07 Dec '17

07 Dec '17

Hi devs, If you are using the koha-misc4dev (in a devbox for instance), you should update it to use the new commit I have just pushed. It will fix an error caused by bug 19724 In a dev box: `cd /home/vagrant/misc4dev; git fetch origin; git rebase origin/master` should do the job Cheers, Jonathan

1 0

REST api: some needed changes / vote proposal
by Tomas Cohen Arazi 07 Dec '17

07 Dec '17

Hi everyone, we've moved forward with the REST api devs, and some decisions we made at the beginning should be dealt with now, before it is too late :-D Right now the so-called REST api consists in 5 endpoints. Vendors: - /acquisitions/vendors - /acquisitions/vendors/{vendor_id} Cities: - /cities - /cities/{cityid} Holds: - /holds - /holds/{reserve_id} Patrons: - /patrons - /patrons/{borrowernumber} Illrequests: - /illrequests When implementing the vendors endpoint, I followed the api first approach, which implies we first think of the api itself, and how it is going to be used, and then think about the implementation. The result is that the exposed attribute names don't match the DB columns (because we picked more meaningful names), and (for example) unused attributes aren't even exposed. When it comes to the previously integrated endpoints, they mostly mimick the DB structure and thus the external api consumers see things that are highly inconsistent: We call them holds, but the ID is reserve_id instead of just hold_id, same for borrowernumber instead of patron_id. New endpoints are being developed with this in mind, but the already implemented ones need to get fixed. As the REST api is already at its first stages I suggest we just change those attributes and notify on the release notes about the change, but it is worth being voted. So I added it to next's dev meeting agenda. It is an urgent decision, as some of fields that would be renamed, are FK for the new endpoints being developed. I hope everyone interested on this gets involved in the discussion on this thread, and we can move forward just voting on the dev meeting. Thanks in advance! -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

3 2

REST api developments
by Tomas Cohen Arazi 06 Dec '17

06 Dec '17

Dear friends, I write this email to let you know me and the ByWater friends are committed to getting endpoints written, so development projects you are working on can succeed. With recent additions and specially all enhancements surrounding bug 19410, we should be able to start writing endpoints faster and easier. The REST api is top priority for us, and making it easier to code, one of our short-term goals. Let us know the endpoints your project might benefit from, we can commit to writing those endpoints, or help you in the process. We still need to have better documentation, but we'll be looking for 'REST api' tagged bugs trying to help. Kind regards -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 <+54%209%20351%20351-3384> GPG: B2F3C15F

4 5

no acces to debian.koha-community.org
by Laurent Ducos 02 Dec '17

02 Dec '17

Hello Since about 1 hour I do not have access to debian.koha-community.org from our public ip 91.121.55.79 Can you give us access again please? since others ip everything is ok --

6 11

Koha Community Newsletter: November 2017
by kohanews 01 Dec '17

01 Dec '17

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

Looking for Koha System Admin
by MHE IT admin 29 Nov '17

29 Nov '17

Hi, We are looking for a Koha system admin to do two task for our university. 1. Back up and Upgrade our Koha 2. Fixing indexing for Arabic and Kurdish records both are RTL Our site is http://library.koyauniversity.org Thank you

1 0

Koha 16.05.19 released
by Mason James 29 Nov '17

29 Nov '17

The Koha community is proud to announce the release of Koha 16.05.19. This is a maintenance release of 16.05 and includes 5 enhancements and 15 bugfixes. The full release notes are available at https://koha-community.org/koha-16-05-19-release This will be my last release as the 16.05.x RMaint Thanks to everyone involved, and to Tomas and Jonathan for the new jenkins :0) cheers, Mason

3 3

Koha 17.05.03 released
by Fridolin SOMERS 27 Nov '17

27 Nov '17

The Koha community is proud to announce the release of Koha 17.05.03. This is a security release including 3 enhancements, 13 bugfixes and 16 security fixes. The full release notes are available at https://koha-community.org/koha-17-05-03-security-release/ Regards, -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers(a)biblibre.com

2 4

Test: planned count or done_testing()
by Mark Tompsett 26 Nov '17

26 Nov '17

Greetings, While testing various bugs, frequently conflicts come up with tests where one bug adds a test, and another adds two tests, and the count difference causes the need to correct the test plan count while rebasing. So, I was wondering if perhaps when adding tests we could switch to just done_testing() and not actually use test counts, so adding and removing tests will not need fixing of line or lines that have a plan count. Thoughts? GPML, Mark Tompsett

6 5