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

[Bug 23640] New: L1 cache too long in SIP Server
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '20

11 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23640 Bug ID: 23640 Summary: L1 cache too long in SIP Server Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Both plack.psgi and rebuild_zebra.pl run Koha::Caches->flush_L1_caches() to periodically flush the L1 cache. The SIP server is another persistent process like those, but it currently has no functionality for flushing the L1 cache. If I understand the code correctly, it'll fetch from the L2 cache (e.g. memcached) once and then keep it there for the life of the master process. I'm not very familiar with the SIP protocol, so I don't know the best place to flush the L1 cache off the top of my head. Perhaps we should run Koha::Caches->flush_L1_caches() at the start of C4::SIP::SIPServer::process_request for every connection, or in C4::SIP::SIPServer::sip_protocol_loop or C4::SIP::SIPServer::read_request. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 53

[Bug 23116] New: AllowHoldPolicyOverride allows a librarian to almost place a hold on an item already on hold
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '20

11 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23116 Bug ID: 23116 Summary: AllowHoldPolicyOverride allows a librarian to almost place a hold on an item already on hold Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- A library appears to be able to place a second item level hold on an item a patron already has on hold if A) AllowHoldPolicyOverride is enabled and B) the circ rule allow for multple item level holds. Once the patron submits the hold requests though, the hold does not get stored in the database. Because allowing two item level holds for the same item makes no sense, we should not allow this attempt to take place, even if AllowHoldPolicyOverride is enabled. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 23504] New: Allow forgiving fines on returned lost items
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '20

11 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23504 Bug ID: 23504 Summary: Allow forgiving fines on returned lost items Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Here's the situation: - Library has WhenLostForgiveFine set to Don't Forgive - Item is overdue with accruing fine - Item is set to lost - Fine switching from FU to F - Item is returned, checked in with Forgive Overdue Charges checked - Fine is not forgiven because it is accounttype F rather than FU Some libraries would like this fine to be forgiven when the item checks in w/ Forgive Overdue Charges -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 17382] New: Elasticsearch - provide a method to identify records not indexed
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '20

10 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17382 Bug ID: 17382 Summary: Elasticsearch - provide a method to identify records not indexed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org While testing I ran across an error in rebuilding where a bad dateaccessioned ('0002-00-05') caused a record to fail indexing It owuld be nice to provide this inofrmation to the user - either via a table or a cronjob/email report - something to allow the library to correct problematic records. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 18193] New: Elasticsearch - adding new records from Z39.50 results in ' internal server error'
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '20

10 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18193 Bug ID: 18193 Summary: Elasticsearch - adding new records from Z39.50 results in 'internal server error' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1 - Go to cataloging 2 - Select 'New from Z39/50' 3 - Search, find a record, import 4 - Save the record 5 - Error! Checking the logs you should see a dump of the record in xml - Koha chokes trying to access it as a MARC::Record In C4/Search.pm: 2492 If we are using elasticsearch, it'll already be a MARC::Record and this 2493 function needs a new name. 2494 2495 =cut 2496 2497 sub new_record_from_zebra { 2498 2499 my $server = shift; 2500 my $raw_data = shift; 2501 # Set the default indexing modes 2502 my $search_engine = C4::Context->preference("SearchEngine"); 2503 if ($search_engine eq 'Elasticsearch') { 2504 return $raw_data; 2505 } However, that doesn't seem to be the case, we are still getting marc XML, adding "&& 0" to the if and nullifying that section (or removing it) seems to solve the issue -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 18822] New: Advanced editor - Rancor - searching broken
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '20

10 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18822 Bug ID: 18822 Summary: Advanced editor - Rancor - searching broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It seems we expect MARC::Record objects, but get MarcXML for local searches - since we can double process the easiest method seem to be attempting conversion and using the updated record if successful -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35

[Bug 16728] New: Display Issued with entry (MARC21 777) to staff and OPAC normal view
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '20

09 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16728 Bug ID: 16728 Summary: Display Issued with entry (MARC21 777) to staff and OPAC normal view Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: eb(a)efdss.org QA Contact: testopia(a)bugs.koha-community.org The 777 field is not one of the fields currently displayed in staff or OPAC normal view. It is visible in the MARC view, but this does not enable the link (via subfield w) to the related record. The subfields are identical to 773 (which does display in the normal view). The main difference being the automatic text generated by the indicators. http://www.loc.gov/marc/bibliographic/concise/bd777.html This is a very important field for music libraries. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 23852] New: Merge biblio-title.inc and biblio-default-view.inc
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '20

09 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23852 Bug ID: 23852 Summary: Merge biblio-title.inc and biblio-default-view.inc Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org The functionality in biblio-default-view.inc should be moved into biblio-title.inc. A "link" parameter will be set when the include file should show a linked title. -- You are receiving this mail because: You are watching all bug changes.

1 32

[Bug 24020] New: System Preference todaysIssuesDefaultSortOrder is not sorting properly
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '20

06 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24020 Bug ID: 24020 Summary: System Preference todaysIssuesDefaultSortOrder is not sorting properly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The system preference todaysIssuesDefaultSortOrder allows the library to choose how their patron's checkouts are sorted on the circulation.pl page. Currently (18.11.10), this is not sorting by due date with either Earliest to Latest or Latest to Earliest chosen. 1. Find 3 items types that circulate for different lengths of time. 2. Checkout out these 3 items to a patron. 3. See that the items are not sorted by due date at all. I found this bug, and there is disagreement with the wording of the system preference, but the manual states " Asks: Sort today’s checkouts on the circulation page from ___ due date", that this should be sorting on Due Date, not checkout date/time. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14005 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 20888] New: Allow use of boolean operator 'not' in item search
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '20

04 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20888 Bug ID: 20888 Summary: Allow use of boolean operator 'not' in item search 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Sometimes it's helpful to be able to exclude items from an item search, for example 'all callnumbers starting with 9'. The item search form currently offers 'or' and 'and', but 'not' is not an option. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 51