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

Call for news: October 2014
by Koha News 16 Oct '14

16 Oct '14

Fellow Koha users ~ We're collecting news for the October newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- * News items can be of any length. * Anything and everything Koha. * Submit by the 26th. If you are working on an interesting project or development related to Koha, please let us know and we'll include it in the development section. -- Chad Roseburg Joanne Dillon Editors, Koha Newsletter

1 0

Cataloging and linking to authorities subfield ORDER!
by Dhd Koha (grharry) 15 Oct '14

15 Oct '14

Hi, My librarian complains that when in cataloging and in particular when he links a biblio marc record to an authority existing record, he needs the order of the subfields copied from the authority to be intact and according to the authority record! For instance When he wishes to link to marc_field XXX subfields ($a, $y, $x, $z) then the subfields of the final marc record should be in the same order and *not* as the defined in the subfields of this marc framework for this TAG! Say there is a field 444 and subfields defined are a,y,x,z The tags and the RECORD Types are just example tags we need to link and copy fields from Authority record type "AN_AUTHORITY_TYPE_RECORD" but inside the Authority record the fields are saved with the order ( a, z, y, x ) So we need them also to be saved in the biblio marc record as tag 444 $a ..... $z ..... $y...... $x ......... So far when cataloging the subfields are stored with the same order as they appeared in the subfields definition of the MARC framework !! Problem 2 Also playing around and observing the js cataloging code we found that the perl function in the Authority.pm my $record=eval {MARC::Record->new_from_xml(StripNonXmlChars($marcxml),'UTF-8', (C4::Context->preference("marcflavour") eq "UNIMARC"?"UNIMARCAUTH":C4::Context->preference("marcflavour")))}; is not honoring any order at all, not the framework subfield definition and not the Authority record subfields existing order ! Is there a solution to this? Is there anybody else with the same issue in hand ??? Regards Harry!

1 0

Photos from KohaCon14
by Paul Poulain 15 Oct '14

15 Oct '14

Hi, I've added a chapter to the wiki page http://wiki.koha-community.org/wiki/KohaCon14, suggesting to add links to the photos you've published. I've put mine (with 100+ photos, more coming) -- Paul Poulain, Associé-gérant / co-owner BibLibre, expert du logiciel libre pour les bibliothèques BibLibre, Open Source software for libraries expert

1 0

Proposed addition to the development-meetings:
by Brendan Gallagher 10 Oct '14

10 Oct '14

Hello All - I'd like at have an addition to the development-meeting. The idea is that, I would present some of the older bugs or even some new ones that really need to have a discussion that results in a solid agreed upon path forward. For example we have 2~3 methods for using DBIC for Koha code where we really need to decide on one path and move forward with that design. The method that I would like to add to the dev-meetings is that I will bring up certain topics at a development-meeting as a homework assign, so that we can all discuss that idea/bug/thought at the next meeting. Along with the first homework assign I will also be setting a date for us to vote on the (homework) bug/enh/thought at the meeting after a sufficient discussion has occurred. The main goal here is to set some deadlines for some of these larger discussions so that we can all move forward. Any meetings that I know I will miss I will find a representative to fulfill this role at the development-meetings. Thanks, Brendan Gallagher ByWater Solutions

1 0

Koha Community Newsletter: September 2014
by Koha News 03 Oct '14

03 Oct '14

Fellow Koha users: The Koha Community Newsletter for August 2014 is here: http://koha-community.org/koha-community-newsletter-september-2014/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email us with any corrections or suggestions. Thanks! Chad Roseburg Joanne Dillon Editors, Koha Community Newsletter

1 0

952$j
by Paul 02 Oct '14

02 Oct '14

Our cataloguers have asked for additional precision in specific stacks -- 952$j "Shelving control number" would appear to be perfect :=) However, any value entered (eg: LLF15 -- loose leaf folder #15) systematically saves as 0 and SchemaSpy doesn't appear to even mention this field which is in the "default template" with no apparent restrictions. Can anyone with good "corporate memory" of 952$j use and programming please assist? Many thanks and best regards -- Paul

3 2

Presentation to mailing list: akafred
by akafred 02 Oct '14

02 Oct '14

Hi! Just a short intro as per the welcome mail: I am contracted by the Oslo Public Library (Deichmanske bibliotek) in Norway to help out in their efforts to build systems for their new library that will open in Oslo in a few years. Koha has been chosen as a cornerstone in this effort. I have been working as a consultant for 15+ years, developing business critical systems for clients in and around Oslo. I LOVE programming, but I also have a passion for quality and a certain disdain for repetitive tasks, and error prone, manual, routines - so I am very into Test-Driven Development (London-style), automation (e g using provisioning tools like Ansible, SaltStack, Puppet, Chef) and prefer properly tested deployment units (like a jar, war, Docker image or, if all else fails, a virtual machine image). Generally, I think learning is what all development efforts should optimize their efforts for, and that transparency, collaboration and rapid feedback are key ingredients in achieving that. The better we are at learning the better we will be at creating awesome stuff that works for our end users. We are in an early phase in our efforts but if you are curious a lot of what we do will be publicly available on our github profile: https://github.com/digibib These days we are looking into how to deploy Koha in Docker. My real name is impossible for non-Norwegians to parse, remember and pronounce so on the interwebs I mostly go by a nickname I chose in a moment of general unclarity and confusion: "Fred" ... so I am a.k.a Fred .... akafred. I try to stop by #koha as akafred, but not always 'there' even if it looks like it - koha(a)akafred.com works though. See ya :-) Regards, - Kjetil a.k.a. "Fred"

4 3

Dom indexing operational with a fresh install?
by Francois Charbonnier 02 Oct '14

02 Oct '14

Hello, Yesterday, I bumped into an indexing bug. The 008 language code is not indexed. I can't find the records using this value. I checked on bugzilla and found this old bug : http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7586. This bug changed "ln:n" by "ln:w" in record.abs . It works with grs-1 indexing. On Katrin advice, I checked if the installation is using dom or grs-1 indexing. I'm on 3.14.07. So it should use dom. koha-conf.xml says "dom" but zebra-biblios.cfg seems to say "grs"... So, I checked "zebra-biblios.cfg" on master and the default values are : * iso2709.recordType:grs.marcxml.record * marcxml.recordType:grs.sgml * recordType:grs.xml Shouldn't we have a reference to dom for these parameters? I also checked biblio-zebra-indexdefs.xsl and biblio-koha-indexdefs.xml and the language index is "ln:n". I tried to change it by "ln:w", restarted zebra server, reindexed but it didn't work. I followed the wiki instruction (http://wiki.koha-community.org/wiki/Switching_to_dom_indexing) to change the "zebra-biblios.cfg" values as well but didn't work either. Any ideas? Thanks! -- François Charbonnier, Bibl. prof. / Chef de produits Tél. : (888) 604-2627 francois.charbonnier(a)inLibro.com <mailto:francois.charbonnier@inLibro.com> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>

3 5

OPAC items location (shelf)
by Paul A 02 Oct '14

02 Oct '14

I've looked through the wiki and bugs.koha... but can't seem to find anything relevant. opac-search.pl (if it finds more than one result) produces a line that reads e.g. "Availability: Copies available: 2nd floor rare (2)," using opac-results.tt which relies on data 'available_items_loo.location' The 'location' that it uses is the one that is defined in the *default* framework (952$c "Other options/Authorized value") (and, by the way, appears to use the raw "auth. value" strings, not the "Description (OPAC)" strings.) It appears that if you define, say for videos, a different set of "Auth. values" (LOC2 instead of LOC) for the "video framework 952$c", this is not picked up by opac-search.pl (for the Main OPAC search page which now reads "Availability: Copies available:(2), "), but is picked up by opac-detail.pl in the proper place in the holdings tab. If you change the "default framework" to use LOC2, it works for "videos", but "book" locations disappear. Maybe I've missed something very obvious, if not I'll try and delve deeper. We have literally hundreds of "locations" and to avoid very long lists in the admin item cataloguing drop down boxes, I've been asked to subdivide them... (LOC2 is fully functional per item type, but introduces the above "loss of functionality" in the OPAC.) The only "work around" that I can quickly find is to put *all* possible locations into LOC, and use LOC2, LOC3 etc for item types -- but this leads to a very ugly page in the "Shelving location" tab at advanced search <http://opac.navalmarinearchive.com/cgi-bin/koha/opac-search.pl>. Thanks and best regards, Paul

1 0

Koha 3.14.10 released
by Fridolin SOMERS 02 Oct '14

02 Oct '14

The Koha community is proud to announce the release of 3.14.10. This is a maintenance release and contains some enhancements and several bugfixes. As always you can download the release from http://download.koha-community.org. Have a look at release post : http://koha-community.org/koha-3-14-10-released "Get the pie while it's hot" Regards, -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers(a)biblibre.com

2 2