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

Re: [Koha-devel] [Koha] RFC for MARC holdings record support
by Ere Maijala 21 Feb '19

21 Feb '19

Good morning! Thanks for the feedback. I added a note to the RFC about embedded holdings in bibliographic records. They cover a lot of needs and we have considered embedding the holdings, but there are issues if there are multiple holdings. Regards, Ere Sebastian Hierl kirjoitti 5.4.2018 klo 10.08: > Good morning! > > I think that the feature would provide added flexibility, in particular > for monographic series and periodicals. Institutions who currently work > with an ILS that has holdings records would want to see the same in > Koha, should they be considering Koha. We currently use the 866 to > display holdings information, thus I don't see this as essential, but it > would be a useful enhancement. > > Greetings from Rome, > Sebastian > > -- > Sebastian Hierl, Ph.D. > Drue Heinz Librarian, Arthur & Janet C. Ross Library > American Academy in Rome > Via Angelo Masina 5 > 00153 Rome > Italy > > T: +39 06 5846 417 > F: +39 06 5810 788 > > On Wed, Apr 4, 2018 at 5:11 PM, Nick Clemens <nick(a)bywatersolutions.com > <mailto:nick@bywatersolutions.com>> wrote: > > There was some discussion of this at the IRC meeting today, > forwarding on > to the general list as well for librarian input/feedback > > On Tue, Apr 3, 2018 at 3:33 AM Ere Maijala <ere.maijala(a)helsinki.fi > <mailto:ere.maijala@helsinki.fi>> wrote: > > > Hi Katrin, > > > > Thanks for the comments. I'll try to clarify the RFC. > > > > --Ere > > > > Katrin Fischer kirjoitti 1.4.2018 klo 17.32: > > > Hi Ere, > > > > > > thx for your work on that! I've added some comments and > questions at the > > > bottom of the RFC page. I think key is to break the big > development down > > > into multiple steps that can be easily tested. > > > > > > Katrin > > > > > > > > > On 26.03.2018 12:58, Ere Maijala wrote: > > >> Hi Everyone, > > >> > > >> I've written an RFC for adding support for MARC holdings records, > > >> available here: > > >> > <https://wiki.koha-community.org/wiki/MARC_Holdings_Records_RFC > <https://wiki.koha-community.org/wiki/MARC_Holdings_Records_RFC>>. I'd > > >> be grateful for any feedback on this. I know there have been some > > >> initiatives to add (back) holdings records, but this proposal > is a bit > > >> different in that it relies on the MARC format and I already > have it > > >> working in a local custom branch apart from OPAC support. > > >> > > >> Regards, > > >> Ere > > >> > > > > > > _______________________________________________ > > > Koha-devel mailing list > > > Koha-devel(a)lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > > > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > <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/ > <http://bugs.koha-community.org/> > > > > -- > > Ere Maijala > > Kansalliskirjasto / The National Library of Finland > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel(a)lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > <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/ <http://bugs.koha-community.org/> > > > -- > Nick Clemens > Sonic Screwdriver (Development Support) > ByWater Solutions > IRC: kidclamp > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> > https://lists.katipo.co.nz/mailman/listinfo/koha > <https://lists.katipo.co.nz/mailman/listinfo/koha> > > -- Ere Maijala Kansalliskirjasto / The National Library of Finland

5 8

Bug 1993 - Task Scheduler Needs Re-write
by Barton Chittenden 28 Sep '18

28 Sep '18

This is an old issue that's never really been addressed. As I understand it, at one time, we had a tool that used the unix 'at' scheduler to run requested reports. This was a huge security hole, and we disabled it.... and it's never worked since. As such, those who host servers must add calls to runreport.pl by hand. Bug 1993 was opened to address this. It was marked as 'In Discussion' in 2013. I would like to see this move forward -- server admins are dying from a thousand paper cuts, and I think that users would benefit from having more control over when their reports are scheduled. What still needs to be discussed here? Thanks, --Barton

5 5

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

Formatting control number searches
by Barton Chittenden 27 Jul '18

27 Jul '18

I'm working on generating links for 7XX linking fields in XSLT, a-la Bug 15140 - Add MARC21 776 to OPAC and staff display ( https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15140) This Takes the 773$w, and uses the XSLT template 'extractControlNumber' which strips the leading MARCOrgCode, e.g. turning (OCoLC)2776588 into 2776588 ... and then the search URL is /cgi-bin/koha/opac-search.pl?q=Control-number:2776588 The problem is that 2776588 isn't the actual OCLC number -- The formatting rules are here: https://help.oclc.org/Metadata_Services/OCLC-MARC_records/Content_designato… In short: 0-8 digits: 0 pad to 8 digits, prepend 'ocm': 2776588 -> ocm02776588 9 digits, prepend 'ocn' > 9 digits, prepend 'on' I tried formatting the search with a leading '*': /cgi-bin/koha/opac-search.pl?q=Control-number:*2776588 as well as with leading and trailing '*' /cgi-bin/koha/opac-search.pl?q=Control-number:*2776588* Neither of these worked. Formatting the control number according to the OCLC rules above did work: /cgi-bin/koha/opac-search.pl?q=Control-number:ocm02776588 So I have three questions: 1) Is there a way to format a Control-number search that doesn't force me to generate the control number according to the OCLC rules above? 2) If not, does anyone have pointers about how to * Test for (OCoLC) -> * Test length of control number * < 9 -> 0 pad to 8 digits, prepend 'ocm' * 9 -> prepend 'ocn' * > 9 -> prepen 'on' 3) Are there other control number formatting rules for other MARCOrgCodes?

2 4

CSS issue in Ordering information on /cgi-bin/koha/acqui/supplier.pl
by David Cook 19 Jul '18

19 Jul '18

I haven't checked master yet, but in the 17.xx versions, I'm noticing it is really difficult to click the dropdown for "List prices are:" in "Ordering information" on /cgi-bin/koha/acqui/supplier.pl. When I look using the F12 tools in Chrome, I see that later "ol" elements are overlapping earlier "li" elements. So the "ol" for the tax options is sitting on top of the "li" for "List prices are:". Only a tiny part of the "li" is clickable underneath that "ol". It looks like the floats in the "li" element are causing the sizing of the "ol" to be no good. See https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Block_formatting_cont ext. There are a number of strategies for fixing this but I'm not sure what the best one would be here. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

3 3

Do you want to see a Koha 18.05 running Elastic Search in production ?
by Paul Poulain 04 Jul '18

04 Jul '18

just go there : https://koha.bulac.fr kudos to BULAC for this move ! And thanks to them for the developments they've sponsored (and are on bugzilla) PS: they made it by themselves, so no reason to congratulate BibLibre ;) -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

6 6

Koha Community Newsletter: June 2018
by kohanews 29 Jun '18

29 Jun '18

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

Koha 17.05.13 release
by Fridolin SOMERS 26 Jun '18

26 Jun '18

The Koha community is proud to announce the release of Koha 17.05.13. This is a maintenance release with only critical bugfixes. The full release notes are available at https://koha-community.org/koha-17-05-13-release/ I see there is not a lot of translation changes. I will stop managing 17.05.x after 17.05.16 in septembre. Regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer

1 0

Suggestion: create a deprecated() function in Koha.
by Barton Chittenden 25 Jun '18

25 Jun '18

It would be useful for Koha to have a 'Deprecated' function, which would send a warning about the caller() function and the version of Koha where the function will be deprecated, and what it will be replaced by... so let's say that C4::Adequate::DoEET() is being replaced by Koha::Awesome->sauce(). in Koha 18.11. In versions of koha prior to 18.11, we add a call to deprecated( "18.11", "Koha::Awesome->sauce()"); at the beginning of C4::Adequate::DoEET(). Then, when C4::Adequate::DoEET() is called, this would generate the following message in the logs: "C4::Adequate::DoEET is deprecated and will be removed in Koha 18.11. It will be replaced by Koha::Awesome->sauce()." This would allow plugin authors to know that they will need to patch their plugins before they break on upgrade. This is a bare-bones implementation of deprecated(): sub deprecated { my ( $version, $replacement ) = @_; my ( $package, $filename, $line, $subroutine, $hasargs, $wantarray, $evaltext, $is_require, $hints, $bitmask, $hinthash ) = caller(1); warn( "${subroutine} is deprecated and will be removed" . " in Koha version $version." . defined( $replacement ) ? " It will be replaced by ${replacement}." : "" ); }

3 2

Koha 17.11.07 release
by Fridolin SOMERS 25 Jun '18

25 Jun '18

The Koha community is proud to announce the release of Koha 17.11.07. This is a maintenance release. The full release notes are available at https://koha-community.org/koha-17-11-07-release/ 17.11.x is my baby now ;) Regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer

1 0