September 2018 - Koha-bugs - lists.koha-community.org

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

07 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

[Bug 19885] New: Allow MaxOpenSuggestions to be set by patron type
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '23

01 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19885 Bug ID: 19885 Summary: Allow MaxOpenSuggestions to be set by patron type Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It would be nice if we could set MaxOpenSuggestions by patron type/library. This would allow each library in a consortium to use the suggestions in the way that was most efficient for each library. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 19062] New: Don't queue check-in/ checkout messages if patron has no e-mail
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '23

29 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19062 Bug ID: 19062 Summary: Don't queue check-in/checkout messages if patron has no e-mail Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org If the patron has no e-mail address we should not queue a check-in or checkout message. If later on an e-mail address is added to the patron account all the old messages could be sent out by accident. Check out and check in messages are only interesting close to the checkout/checkin process, later on, they are just confusing to patrons. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 20676] New: svc/barcode should allow barcode to be printed without text
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '23

28 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20676 Bug ID: 20676 Summary: svc/barcode should allow barcode to be printed without text Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org svc/barcode currently generates the barcode using $image = GD::Barcode->new( $type, $barcode )->plot()->png(); >From perldoc GD::Barcode plot() $oGd = $oGdBar->plot([Height => $iHeight, NoText => 0 | 1]); creates GD object with barcode image for the $sTxt specified at new method. $iHeight is height of the image. If NoText is 1, the image has no text image of $sTxt. ex. my $oGdB = GD::Barcode->new('EAN13', '123456789012'); my $oGD = $oGdB->plot(NoText=>1, Height => 20); # $sGD is a GD image with Height=>20 pixels, with no text. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 20894] New: Feature request: pass barcode width and height as parameters to /svc/barcode
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '23

28 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20894 Bug ID: 20894 Summary: Feature request: pass barcode width and height as parameters to /svc/barcode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org /svc/barcode does not currently accept width and height parameters, even though GD::Barcode does. We should allow these to be passed in. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 17228] New: Make two versions of SIPconfig.xml identical
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '23

23 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17228 Bug ID: 17228 Summary: Make two versions of SIPconfig.xml identical Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Packaging Assignee: magnus(a)libriotech.no Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net We have two versions of SIPconfig.xml: etc/SIPconfig.xml debian/templates/SIPconfig.xml The former has been updated with some changes to the possible configuration of SIP2 servers, e.g. by bug 15006. The latter has not been updated with the same information. Since debian/templates/SIPconfig.xml contains no special placeholders or variables, this bug proposes to simply copy etc/SIPconfig.xml to debian/templates/SIPconfig.xml, so that admins using the packages will see an up-to-date SIP2 config example when they have enabled SIP2 for a site. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 18094] New: Patron search filters are broken by searchable attributes
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '23

20 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18094 Bug ID: 18094 Summary: Patron search filters are broken by searchable attributes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com When using searchable patron attributes they seem to be added to all searches as a contain To recreate: Add a new patron attrbute and mark it searchable Populate a new patron with 'potato' in that field Add/edit another patron to have email potato(a)invalidemail.com' Perform a patron search with filters 'Email' and 'Starts with' and query 'potato' You will see both patrons in your results Remove the potato email Perform search again You will be directed to the patron containing the potato attribute -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 18426] New: Subscriptions batch editing
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '23

17 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18426 Bug ID: 18426 Summary: Subscriptions batch editing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Serials Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com -- You are receiving this mail because: You are watching all bug changes.

1 47

[Bug 18853] New: Module wise email alerts
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '23

16 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18853 Bug ID: 18853 Summary: Module wise email alerts Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: mishravk79(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org At present koha is having limited number of email configurations for which library module managers is finding difficulty in replying or getting feedback from users. Therefore in sender address email should be separate module emails so that if a user reply should directly come to concern module manager like Acquisition, Circulation, Serial etc. because the emails are generating from the various modules/manager but replying to only one email is something very difficult to manage. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 21452] New: Items available for hold or loan must have an item type
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21452 Bug ID: 21452 Summary: Items available for hold or loan must have an item type 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Because items may be created during cataloging or acquisitions before we know the item type, it's not practical to set a database constraint where items.itype is not NULL. However, if an item without an item type is checked out or a hold is placed on the item, either items.itype or biblioitems.itemtype (if we're using biblio level items) *must* be populated, or we'll trigger an internal server error. We should be checking for this when we set the notforloan status. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5