December 2019 - Koha-bugs - lists.koha-community.org

[Bug 18475] New: Table 'Place a hold on a specific item' needs a tidy up
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18475 Bug ID: 18475 Summary: Table 'Place a hold on a specific item' needs a tidy up Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The table 'Place a hold on a specific item' looks outdated and the column 'Information' is not very readable. It needs a tidy up. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 18520] New: special_holidays should be unique by date and branch code
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18520 Bug ID: 18520 Summary: special_holidays should be unique by date and branch code Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Holidays Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I just found a library that had up to 7 entries in the special_holidays table for a given combination of branchcode and year, month, day. This doesn't make sense, it's not fixable in the UI, and it can cause performance issues, because all values will be checked. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 18872] New: Clicking "Place hold" on catalogue/ detail.pl triggers software error if any items have NULL homebranch
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18872 Bug ID: 18872 Summary: Clicking "Place hold" on catalogue/detail.pl triggers software error if any items have NULL homebranch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To re-create: 1) Create several items. Set homebranch to NULL on one of the items. 2) Go to the detail page for the bib record. Click "Place Hold". 3) This will trigger a software error. Here are the results from the logs: Use of uninitialized value in hash element at /usr/share/koha/intranet/cgi-bin/reserve/request.pl line 362. Use of uninitialized value in hash element at /usr/share/koha/intranet/cgi-bin/reserve/request.pl line 363. Use of uninitialized value in string ne at /usr/share/koha/intranet/cgi-bin/reserve/request.pl line 368. Use of uninitialized value in string ne at /usr/share/koha/intranet/cgi-bin/reserve/request.pl line 368. item-level_itypes set but no itemtype set for item (762357) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. No homebranch at /usr/share/koha/lib/C4/Reserves.pm line 2121. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 18879] New: Sending notices via Facebook messenger
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18879 Bug ID: 18879 Summary: Sending notices via Facebook messenger Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I saw some services that use FB Messenger for sending customer notices. What do you thing about it guys? Maybe its "cooler way" for younģer patrons. Its free for library, it can turn into interactive talk with two real people, so it can help to make better relationship between library and patrons. Description of API: https://developers.facebook.com/docs/messenger-platform -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 18883] New: koha-http.conf designed for Apache 2.2
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18883 Bug ID: 18883 Summary: koha-http.conf designed for Apache 2.2 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org I was installing a Koha site from source and got a syntax error from the "Order" directive since I am using Apache 2.4 and koha-http.conf is designed for Apache 2.2. It's an easy enough change to use "Require all denied" instead of "Order deny,allow\n Deny from all", but I wonder if we should update the file to use Apache 2.4 just to keep non-package installs more in-line with package installs (although I suppose there are quite a few differences between the Apache configuration files anyway). I was planning to submit a patch using mod_version, but that's an extension module, so I think it might be a bit much to expect people to install that just to run Koha out of the box. I notice openSUSE doesn't even have mod_version in the 42.2 repositories, so I'm just going to update my file to 2.4 sytnax, but thought I'd raise it here in any case. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 18892] New: RDA fields not searchable as Publisher
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18892 Bug ID: 18892 Summary: RDA fields not searchable as Publisher Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 14198 - RDA: Indexing 264 field (Zebra) added an index called 'Provider' (with a CCL mapping of 'pv'). However, this does not allow bibs cataloged under RDA to be searched using the 'Publisher' search. Library of congress shows that 264 indicator 2 can be used to distinguish manufacture and distribution vs. publication: Second Indicator - Function of entity 0 - Production Field contains a statement relating to the inscription, fabrication, construction, etc., of a resource in an unpublished form. 1 - Publication Field contains a statement relating to the publication, release, or issuing of a resource. 2 - Distribution Field contains a statement relating to the distribution of a resource. 3 - Manufacture Field contains a statement relating to the printing, duplicating, casting, etc., of a resource in a published form. 4 - Copyright notice date Field contains a date associated with a notice of protection under copyright or a similar regime. Copyright dates include phonogram dates (i.e., dates associated with claims of protection for sound recordings). ... so indicator 2 values of 1 or 4 should correspond to publisher. We have the ability to specify indicator values when indexing; we should use it in this case. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 19561] New: Add "preferred language" to OPAC Personal Details opac-memberentry.pl
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19561 Bug ID: 19561 Summary: Add "preferred language" to OPAC Personal Details opac-memberentry.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 17762 adds the ability to translate notices. The new system preference for translatenotices allows staff members to set a preferred language in the user account, which controls which template will be used when generating notices. It would be great to allow patrons to select their preferred language in the OPAC Personal Details page on opac-memberentry.pl. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 19084] New: Spine label with BN_IN UTF8 data rendered incorrectly
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19084 Bug ID: 19084 Summary: Spine label with BN_IN UTF8 data rendered incorrectly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: indradg(a)l2c2.co.in QA Contact: testopia(a)bugs.koha-community.org Created attachment 65878 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=65878&action=ed… View of expected output vs output rendered I was trying to generate spine labels with call numbers in my mother tongue Bengali, which is spoken by 250 million people making it the 7th largest spoken language in the world. In the attachment, the text bordered with green outline is how it is expected to appear, however what appears in the PDF is the text within the red border on left. FWIW, the koha-conf.xml ttf settings for Bengali font are in place, checked with different fonts, including Lohit Bengali which is the default BN_IN font on RHEL, Fedora and Ubuntu etc. as well as with NOTO Sans Bengali from Google. None of the conjunct clusters as well as matraas that go before a letter are rendered in the correct order. Unless this is fixed Koha can not be used to correctly generate spine labels for Bengali books For reference, here is discussion about a similar problem with iText - http://palashray.com/making-itext-work-with-indic-scripts/ -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 19264] New: Patron card creator: Add descriptions to PODs in Patroncard.pm
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19264 Bug ID: 19264 Summary: Patron card creator: Add descriptions to PODs in Patroncard.pm Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org PODs in Patroncard.pm need descriptions. See: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18541#c23 -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 19406] New: REST API: Add route for checkins
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19406 Bug ID: 19406 Summary: REST API: Add route for checkins Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au I don't have plans to work on this at the moment, but it would be great to have a route for checkins. I notice that there is already a bug for checkouts at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13895. This could replace svc/checkin. I haven't tried the REST API yet but it's probably better performance than svc/checkin anyway. Plus, this would allow other apps to checkin for Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3