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

[Bug 20607] New: Elasticsearch - ability to add a relevancy weight in mappings.yaml file
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '19

06 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20607 Bug ID: 20607 Summary: Elasticsearch - ability to add a relevancy weight in mappings.yaml file Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: claire.hernandez(a)biblibre.com The code could be able to inject mappings and weight if a mapping in mappings.yaml file contains boost-in-simple-search: Exemple: Personal-name: label: Personal-name mappings: - facet: '' marc_field: 100abcdefghjklmnopqrstvxyz marc_type: marc21 sort: ~ suggestible: '' - facet: '' marc_field: 100abcdefghjklmnopqrstvxyz marc_type: normarc sort: ~ suggestible: '' type: '' boost-in-simple-search: 4 4 is added in field weight in table search_field. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 22034] New: Viewing rrecord with Default framework doesn't work on MARC tab
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '19

06 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22034 Bug ID: 22034 Summary: Viewing rrecord with Default framework doesn't work on MARC tab Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- To test: - Create a record in any framework that is not default - Search for the record in your catalog - Switch to the MARC tab - Change framework pull down to default on top - Note the page reloads, but the framework doesn't stay default - Verify it works for other frameworks -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 18712] New: Run database_dependent test suite --No ignored
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '19

05 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18712 Bug ID: 18712 Summary: Run database_dependent test suite --No ignored Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: gmcharlt(a)gmail.com Reporter: bob-ewart(a)bobsown.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 63893 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=63893&action=ed… Full log of 'make test' including STDERR and STDOUT Build Koha from the tarball. Answer no to 'run the database-dependent test suite (no, yes) no. Running 'make test' generates many errors trying to access the database. Most of the tests which do generate DBD::mysql::st errors still show up as 'ok'. See the attached log. t/Matcher.t and t/Prices.t do fail Test Summary Report ------------------- t/Matcher.t (Wstat: 768 Tests: 12 Failed: 3) Failed tests: 3-5 Non-zero exit status: 3 t/Prices.t (Wstat: 65280 Tests: 5 Failed: 1) Failed test: 5 Non-zero exit status: 255 Parse errors: Bad plan. You planned 16 tests but ran 5. Files=100, Tests=11528, 95 wallclock secs ( 0.89 usr 0.16 sys + 81.23 cusr 3.06 csys = 85.34 CPU) Result: FAIL Failed 2/100 test programs. 4/11528 subtests failed. Makefile:9572: recipe for target 'test_dynamic' failed make: *** [test_dynamic] Error 255 -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 18224] New: Cleanup after Buug 14778
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '19

05 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18224 Bug ID: 18224 Summary: Cleanup after Buug 14778 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Fixtures introduce biblios but they are not used in the whole test case. Remove unnecessary code. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 20654] New: Omnibus: Update two-column templates to use Bootstrap grid
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '19

05 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20654 Bug ID: 20654 Summary: Omnibus: Update two-column templates to use Bootstrap grid 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 CC: testopia(a)bugs.koha-community.org Blocks: 14546 This omnibus bug will cover bugs which update two-column template grid markup from YUI to Bootstrap. Typical markup to be replaced: <div id="doc3" class="yui-t2"> <div id="bd"> <div id="yui-main"> <div class="yui-b">  </div> </div> <div class="yui-b">  </div> </div> </div> Replacement: <div class="main container-fluid"> <div class="row"> <div class="col-sm-10 col-sm-push-2">  </div> <div class="col-sm-2 col-sm-pull-10">  </div> </div> </div> Note that "col-sm-push-2" and "col-sm-pull-10" are the classes that reverse the visible column order in the desktop layout. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14546 [Bug 14546] Make staff client templates responsive -- You are receiving this mail because: You are watching all bug changes.

1 103

[Bug 22144] New: Add method marc() to Koha::Biblio
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '19

04 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22144 Bug ID: 22144 Summary: Add method marc() to Koha::Biblio Change sponsored?: --- Product: Koha Version: unspecified 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 Target Milestone: --- It would be very convenient to be able to retrieve a bib's MARC::Record object directly from biblio object. This would be very useful for Template Toolkit syntax in slips and notices where a library would like to use arbitrary MARC fields that aren't stored in the database. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 21411] New: Advanced cataloging editor - rancor - Allow configuration of Keyboard shortcuts
by bugzilla-daemon＠bugs.koha-community.org 03 Aug '19

03 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21411 Bug ID: 21411 Summary: Advanced cataloging editor - rancor - Allow configuration of Keyboard shortcuts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 These patches will add a link tot he keyboard shortcuts dropdown in the advanced cataloging editor to a page where the mappings can be redefined -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 47

[Bug 21181] New: Cancel expired holds cronjob does not cancel holds in transit if ExpireReservesMaxPickUpDelay not set
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '19

29 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21181 Bug ID: 21181 Summary: Cancel expired holds cronjob does not cancel holds in transit if ExpireReservesMaxPickUpDelay not set Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Debatable, but that problem as it arose: 1 - Patron places a hold, sets 'not needed after' to July 1 2 - Hold is put in transit 3 - Time passes, it is now July 2 4 - Cancel expired holds cron does not cancel hold - found='W' 5 - Hold arrives at destination on July 3 6 - Hold is trapped, patron is notified -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 21534] New: ElasticSearch - Dash is considered like a boolean operator
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '19

26 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21534 Bug ID: 21534 Summary: ElasticSearch - Dash is considered like a boolean operator Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)collecto.ca Hi, The following search "Pierrette Saints-Anges" gives no results. url is opac-search.pl?q=pierrette+Saints-Anges The search "Pierrette saints anges" works. url is opac-search.pl?q=pierrette+Saints+Anges I think dash (-) in my first search is considered like a boolean operator, right? Has this problem been identified for ElasticSearch? Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 15679] New: Reset item level hold back to record level hold without deleting and readding the hold
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '19

26 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15679 Bug ID: 15679 Summary: Reset item level hold back to record level hold without deleting and readding the hold Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: hbraum(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Right now, if a hold is tied to a specific item (for any number of reasons), and it needs to be set back to a title level hold, you have to delete and readd the hold. This is cumbersome enough, but it's even more cumbersome when a record has multiple holds (especially 20+), and the hold has to be replaced and manually back in its original priority order. It would be nice if Koha could allow you to reset a hold back to record level after it's been placed, for all cases, including when it's in transit for a patron. Situations arise where an item arrives damaged or is lost in transit and a new item is needed to fulfill the hold. There should probably be a permission to control access to this proposed functionality, like the existing modify_holds_priority permission. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5