May 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

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

Request for feedback: Bug 20779 - Style refresh for patron detail page
by Owen Leonard 05 Jun '18

05 Jun '18

I've submitted a patch on Bug 20779 to refresh the style of the patron detail page, and I'd like to get some feedback on my proposal. Compare this "before" image: https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=75434 ...with this screenshot after the patch has been applied: https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=75435 ...and another alternative: https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=75638 If anyone has a vote or suggestions, please chime in. Thanks, -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

7 9

Re: [Koha-devel] [Koha] Single Sign-On via Drupal
by Mark Tompsett 31 May '18

31 May '18

Greetings, This reminds me of Google authentication code... opac/svc/auth/googleopenidconnect Around line 186 there is auto-register code. I'm sure auto-registration could be broken out for reuse, and the CAS equivalent linked to this. I would love to code this for the community, but sadly I do not know how to set up a CAS server to properly test. GPML, Mark Tompsett

2 1

adding serial numbers to the list of items in CHECKIN email
by Indranil Das Gupta 29 May '18

29 May '18

Hi, I'm trying to add a serial number (1,2,3 ... n) to each row of items listed in the CHECKIN digest email on the latest oldstable. First I tried to be cocky and attempted to do something like this : .circdata tr:not(.circheader) { counter-increment: row-num; } .circdata tr:not(.circheader) td:first-child::after { content: counter(row-num); text-align: left; } Of course even in 2018, GMail web client does not seem to allow that. So I looked at the code in C4/Circulation.pm, Letters.pm, Message.pm and read up the bug reports on adding TT syntax to the notices, but i could not see a way to do that. If I am missing something obvious or is attempting to do something that is not possible on present codebase, please feel free to hit me over the head with a cluebat ;-) cheers indranil -- Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg

2 1

Explanations in systempreferences options?
by Jon Knight 29 May '18

29 May '18

Hi, In the midst of working on a new patch on my kohadevbox, I wanted to add a new system preference. In doing so (and debugging as a result!) I noticed some existing system preferences appear to have what I would assume should be the explanation in the option field: mysql> select * from systempreferences where type = "yesno" and variable like "Suspend%"; +----------------------+-------+------------------------------------------------+-------------+-------+ | variable | value | options | explanation | type | +----------------------+-------+------------------------------------------------+-------------+-------+ | SuspendHoldsIntranet | 1 | Allow holds to be suspended from the intranet. | NULL | YesNo | | SuspendHoldsOpac | 1 | Allow holds to be suspended from the OPAC. | NULL | YesNo | +----------------------+-------+------------------------------------------------+-------------+-------+ Yet these appear on the administration system preferences output OK. Are these wrong, or am I misunderstanding how explanation and options are supposed to work? I thought explanation was the human readable text and options were things you could choose from?

2 1

Dashboard
by Marcel de Rooy 25 May '18

25 May '18

I like the Koha dashboard, but I would not mind if someone else (...) removed the patch status changes box and the patches pushed for release 18.05 list. (The last one is not updated in a longer time.) Removing should not be that hard for the maintainer himself ? I am focusing on Koha in the meantime :) Thanks, Marcel

1 0

Replace Catmandu indexing code with pure perl and eventually drop Catmandu as a Koha dependency
by David Gustafsson 25 May '18

25 May '18

Hi all! I have been working on replacing Catmandu depandant indexing code with a simpler and faster Koha-specific one using the Search::Elasticsearch package (which Catmandu uses internally): https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19893 Some of the benefits would be: 1) Increased indexing performance (about twice as fast, six times as fast if comparing time spent in update_index()), due to more efficient json-conversion and fewer Elasticsearch requests. 2) With Catmandu indexing speed decreases as more mappings are added, with the alternative algorithm indexing is kept more or less constant no matter how many mappings you add. 3) Neglectable indexing start-up time. Especially noticeable when indexing a single document. For example we have an issue with the book drop machine, each return taking a couple of seconds because of the Catmandu start-up overhead (or when saving biblios in staff client). 4) More transparent code and less complexity compared with Catmandu (admittedly partly subjective statement) should lead to improved maintainability and increased stability. 5) No need for new developers to learn the Fix language 6) Closer to the metal so easier to perform even more Koha-specific optimizations and customizations which might not be feasible with Catmandu in tthe way The proposed patch only addresses the indexing logic but the remaining Catmandu-dependant code (mainly for searching) should be pretty trivial to replace with Search::Elasticsearch implementation which can be done as a next step. Would be wonderful if this could be raised for discussion at the next developers meeting. Best regards David Gustafsson

2 6

Koha 17.05.12 release
by Fridolin SOMERS 24 May '18

24 May '18

The Koha community is proud to announce the release of Koha 17.05.12. This is a maintenance release containing 2 security patches. The full release notes are available at https://koha-community.org/koha-17-05-12-release/ Regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer

1 0