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

[Bug 15977] New: Optional double screen message in Patron Info/Status
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '23

20 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15977 Bug ID: 15977 Summary: Optional double screen message in Patron Info/Status Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com This code in MsgType.pm: $resp .= maybe_add( FID_SCREEN_MSG, $patron->{branchcode}, $server ) if ( $server->{account}->{send_patron_home_library_in_af} ); produces two AFs if you enable that attribute in your config. Not sure if that should be the case and is conform protocol. Also: are we solving a problem here in the wrong place? It looks kind of inappropriate use.. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 22317] New: Performance issues with large number of funds
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '23

17 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22317 Bug ID: 22317 Summary: Performance issues with large number of funds 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- The acquisitions landing page displays a summary table for the funds. This can sometimes be very large and cause a significant lag in the page load and display. Ultimately, it would be nice to fix this performance issue at the root. (There is initially a fairly prominent server lag, but there is also a clear difference between rendering time in Chrome/Firefox vs in IE). As a 'quick fix' it may be enough to make the display of that summary table syspref controlled so libraries with a large number of funds defined can choose not to display the summary on that page to improve the performance of page load so they can proceed to Vendor searches and other acquisitions actions available from that page. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 22221] New: Changing an item to a Lost Status on an item level hold does not change the hold
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '23

17 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22221 Bug ID: 22221 Summary: Changing an item to a Lost Status on an item level hold does not change the hold Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 Target Milestone: --- If a library is using Item Level holds and a patron places a specific item hold. If the library finds that this specific item is missing, they can change the item to missing, however, the hold is still attached to this item. The library then needs to remove the item level hold and re-attach it to another item or make it a bib level hold. It would be nice, if this change of "Lost" status of this item is altered, the hold can be changed to a bib level hold or an easy ability to adjust the hold as necessary. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 19098] New: Additional logic for 260/RDA 264 fields
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '23

17 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19098 Bug ID: 19098 Summary: Additional logic for 260/RDA 264 fields 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If we have implemented 10306 and 19096, we can add some additional logic for multiple RDA 264 fields. Making e.g. the place and year picked more accurate than just glueing together or picking the first one. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 23124] New: trailing spaces in DefaultPatronSearchFields can break patron searching
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '23

16 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23124 Bug ID: 23124 Summary: trailing spaces in DefaultPatronSearchFields can break patron searching Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- We should probably just trim this string on save? To recreate: 1 - Add a trailing space to DefaultPatronSearchFields 2 - Attempt to search for patrons 3 - Error! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 21106] New: oai.pl XML output doesn't validate against OAI-PMH XML schema
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '23

16 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21106 Bug ID: 21106 Summary: oai.pl XML output doesn't validate against OAI-PMH XML schema Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P3 Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: pablo.bianchi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 21102 When using some verbs Koha return a well formed but in invalid XML. CLI test: wget -q "https://www.openarchives.org/OAI/2.0/OAI-PMH.xsd" wget -q "https://demo.bibkat.no/cgi-bin/koha/oai.pl?verb=ListSets" -O test.xml xmllint --noout --schema OAI-PMH.xsd test.xml Web test: An online way to test this is with http://validator.oaipmh.com/ 1. verb=ListSets: When no set is defined Koha incorrectly output <ListSets/>. A set (child element of ListSets) should always be there, minOccurs default value is 1. Otherwhise should be: <error code="noSetHierarchy">No sets defined</error>, AFAIK even if tehere is no error. 2. verb=Identify: setDescription is not a string, is descriptionType ##other, "defined by a community" (?) See https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17785#c13 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21102 [Bug 21102] OAI-PMH specification conformance [UMBRELLA] -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 22712] New: Funds from inactive budgets appear on Item details if using MarcItemFieldstoOrder
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22712 Bug ID: 22712 Summary: Funds from inactive budgets appear on Item details if using MarcItemFieldstoOrder Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Created attachment 88047 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=88047&action=ed… drop down Bug 14850 has been fixed and patched for 18.11. This removes the ability to see inactive funds when allocating orders to these funds from an inactive budget. However, if a library is using the system preference MarcItemFieldstoOrder, all the funds will appear in the drop-down menu for that item record. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 21330] New: Add xslt for authority normal view in OPAC
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21330 Bug ID: 21330 Summary: Add xslt for authority normal view in OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Hi, It would be fine to have a xslt stylesheet for authority normal view in OPAC (opac-authoritiesdetail.pl). Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes.

1 74

[Bug 23838] New: Add ability to view item renew history
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23838 Bug ID: 23838 Summary: Add ability to view item renew history 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: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It should be possible, when viewing a patron's circulation history, to view details of an item's renewals. Each renewal should be displayed as: Renewed on <renewal date> by <renewed by> -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 119

[Bug 18827] New: Elasticsearch mappings - not displayed or retrieved in saved order
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '23

06 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18827 Bug ID: 18827 Summary: Elasticsearch mappings - not displayed or retrieved in saved order Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The mappings listed under 'Biblios' and 'Authorities' are draggable - this allows ordering of fields. The ordering affects the id field in the search_marc_map table When retrieving for display or mapping we are not ordering by the this field. In general I am not sure if we are gaining anything with this ordering: https://www.elastic.co/guide/en/elasticsearch/guide/current/_sorting.html " When sorting on fields with more than one value, remember that the values do not have any intrinsic order; a multivalue field is just a bag of values. Which one do you choose to sort on?" I think we can switch to the idea that a single field per index should be chosen for ordering: author = 100 (only make this one sortable) author = 700 author = 245c or, in the case of authorities, we should expect a single field to populate the field for sorting (100, 110, 150 ... are alldefined as 'main-heading' - but each record should only have a single one of these field) -- You are receiving this mail because: You are watching all bug changes.

1 18