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

[Bug 18791] New: Add the ability for librarians to easily copy, download or print DataTables based tables in Koha
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '20

12 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18791 Bug ID: 18791 Summary: Add the ability for librarians to easily copy, download or print DataTables based tables in Koha Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org There are many tables in Koha where it would be useful for librarians to easily copy, download or print the table for various purposes. These functions are available via DataTables button plugins. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 51

[Bug 18071] New: Extend script update_authorities.pl
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '20

12 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18071 Bug ID: 18071 Summary: Extend script update_authorities.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 43

[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 17510] New: marc modification templates ignore subfield $0
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '20

02 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17510 Bug ID: 17510 Summary: marc modification templates ignore subfield $0 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: hagud(a)orex.es QA Contact: testopia(a)bugs.koha-community.org We have realized that Koha MArc modification templates ignore subfield 0, it is not very common used subfield, it is working with subfields greater than 0 We have create a template for adding 773$0 (host biblionumber in analytics) but the template doesn't get the subfield and only stores main tag 773. Checked in: Koha 3.22 & 16.05.05 Debian 8 and plack enabled TEST Go to Tools --> MARC modification templates Create one rule. Add/Update field 773 0 with value 'demo' save it you can check that subfield is not appearing in the descrption, if you edit it appears, but when you try to execute thah template, and try to previwe the marc you get internal error and get the following log. This action is not implemented yet at /usr/share/koha/lib/Koha/SimpleMARC.pm line 169. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 18958] New: If patron has multiple record level holds on one record transferring first hold causes next hold to become item level
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '20

26 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18958 Bug ID: 18958 Summary: If patron has multiple record level holds on one record transferring first hold causes next hold to become item level 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Imagine you have a record with 3 items, each item is held by LibraryA, LibraryB and LibraryC respectively. Now, a patron places to record level holds for pickup at LibraryD. When any of the items are checked in, that item is trapped to fill the first hold, but a side affect is that the next open hold because item level for the item that was just checked in! This is clearly incorrect and prevents the patron from placing more record level holds on the record. To reproduce: 1. Create and use a patron that can place multiple record level holds per record 2. Create a record with X items, each at a different library 3. Place X 'Next available' holds on the record for the patron using the 'Holds to place' box 4. Check in LibraryA's copy as LibraryA and confirm the hold 5. Revisit request.pl for the record, notice the next hold in line is now item-specific 6. Attempt to place another hold for your patron, notice that it requires an item-specific hold -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 119

[Bug 18420] New: t/dbdependent/Budgets.t fails without patron category 'S'
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '20

20 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18420 Bug ID: 18420 Summary: t/dbdependent/Budgets.t fails without patron category 'S' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: veron(a)veron.ch QA Contact: gmcharlt(a)gmail.com If no patron category 'S' is defined, t/dbdependent/Budgets.t fails. -- You are receiving this mail because: You are watching all bug changes.

1 48

[Bug 17458] New: ID of logged user is displayed when just consult an invoice (parcel.pl)
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '20

20 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17458 Bug ID: 17458 Summary: ID of logged user is displayed when just consult an invoice (parcel.pl) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org Hi, When we just consult receipt summary (parcel.pl), the ID of logged user is displayed in field "Received by" But effective receipt were done by someone else. Id of user who done receipt is logged somewhere? Regards, Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21