May 2017 - Koha-bugs - lists.koha-community.org

[Bug 8612] CSV export profile to have custom fields in export csv basket
by bugzilla-daemon＠bugs.koha-community.org 09 May '17

09 May '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8612 --- Comment #101 from Josef Moravec <josef.moravec(a)gmail.com> --- Ok, it was not good solution, now should be better ;) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8612] CSV export profile to have custom fields in export csv basket
by bugzilla-daemon＠bugs.koha-community.org 09 May '17

09 May '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8612 Josef Moravec <josef.moravec(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #63158|0 |1 is obsolete| | --- Comment #100 from Josef Moravec <josef.moravec(a)gmail.com> --- Created attachment 63279 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=63279&action=ed… Bug 8612: QA followup - strip white chars from csv profile definition, expand test -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15399] MARCXML records larger than 1 MB (1048576 bytes) are not searchable.
by bugzilla-daemon＠bugs.koha-community.org 09 May '17

09 May '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15399 --- Comment #15 from Fridolin SOMERS <fridolin.somers(a)biblibre.com> --- Looks like the perl Module Net-Z3950-ZOOM also has an option to specify max record size (1MB by default). http://search.cpan.org/~mirk/Net-Z3950-ZOOM/lib/ZOOM.pod#option()_/_option_… -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15399] MARCXML records larger than 1 MB (1048576 bytes) are not searchable.
by bugzilla-daemon＠bugs.koha-community.org 09 May '17

09 May '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15399 --- Comment #14 from Fridolin SOMERS <fridolin.somers(a)biblibre.com> --- We had the same issue and proposed rebuild_zebra.pl options on Bug 10482 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14716] opac-detail.pl -- Series link fails when series title ends with semicolon preceded by space.
by bugzilla-daemon＠bugs.koha-community.org 09 May '17

09 May '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14716 --- Comment #23 from Mason James <mtj(a)kohaaloha.com> --- (In reply to Katrin Fischer from comment #22) > Removing the ; would be an incomplete fix, but much easier to do as a > workaround solution. ..after re-readed this bug, i agree with Katrin :0) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15399] MARCXML records larger than 1 MB (1048576 bytes) are not searchable.
by bugzilla-daemon＠bugs.koha-community.org 08 May '17

08 May '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15399 --- Comment #13 from Barton Chittenden <barton(a)bywatersolutions.com> --- (In reply to alfre69 from comment #9) > If you increase $max_record_size too much it breaks the Z39.50 server. > > A yaz-client search report this: > > Target has closed the association. > Reason: protocolError, message: Incoming package too large Does this error occur on *all* searches, or simply searches whose results are greater than 1 MB? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15399] MARCXML records larger than 1 MB (1048576 bytes) are not searchable.
by bugzilla-daemon＠bugs.koha-community.org 08 May '17

08 May '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15399 --- Comment #12 from Barton Chittenden <barton(a)bywatersolutions.com> --- (In reply to Barton Chittenden from comment #8) > It turns out that the 1024 K limit is the default max record size in > zebrasrv; this can be changed using the -k option to zebrasrv. > > man zebrasrv shows: > > -k size > Maximum record size/message size, in kilobytes. Default is 1024 KB (1 MB). > > This could be increased in koha-start-zebra, koha-restart-zebra and > koha-zebra. I imagine the change would look something like this: > > from > > zebrasrv \ > -v $loglevels \ > -f "/etc/koha/sites/$instancename/koha-conf.xml" && \ > return 0 || \ > return 1 > > to > > zebrasrv \ > -v $loglevels \ > -k $max_record_size > -f "/etc/koha/sites/$instancename/koha-conf.xml" && \ > return 0 || \ > return 1 > > where $max_record_size would be read from $KOHA_CONF in the same manner that > $loglevels is. Based on my testing, I believe that the documentation is wrong -- the value of -k is in bytes, not Kilobytes. -- This may be a moot point, considering the issues with Z39.50. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13944] Fund sorting is inconsistent across different parts of Koha
by bugzilla-daemon＠bugs.koha-community.org 08 May '17

08 May '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13944 --- Comment #4 from Sandre Cunha <cunha(a)monterey.org> --- I think fund name would be the best option. Between our operating and our trust fund budget, we have a lot of fund codes, and sorting by the code would not put the fund lines in any kind of meaningful order. At least if the sort is by fund name, one has the option of adding words or letters to force the sort into the order one wants. The sorting by order of creation is a nightmare when you are trying to create a budget and group things in a logical way. If you miss one, or had a couple of last minute additions, you either have to re-do the whole thing, or just let them hang out at the bottom, rather in a related group. It would be nice to be able to re-sort them, but if the default was to sort by name, this issue would less of a problem. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14850] Funds from inactive budgets appear in 'Funds' dropdown on acqui/invoice.pl
by bugzilla-daemon＠bugs.koha-community.org 08 May '17

08 May '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14850 Marjorie Barry-Vila <marjorie.barry-vila(a)ccsr.qc.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marjorie.barry-vila(a)ccsr.qc | |.ca -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13944] Fund sorting is inconsistent across different parts of Koha
by bugzilla-daemon＠bugs.koha-community.org 08 May '17

08 May '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13944 --- Comment #3 from Marjorie Barry-Vila <marjorie.barry-vila(a)ccsr.qc.ca> --- Hi, I prefer too, sort by fund name. But now in 16.11, fund pulldown for an order line ( acqui/neworderempty.pl ) is sort by Fund code. But in acqui/invoice.pl, shipping funds are sort by Name (and other problem, all funds are displayed). Anyone want to works on it? Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes.

1 0