February 2020 - Koha-bugs - lists.koha-community.org

[Bug 19324] New: New Inventory workflow eliminates "mark item seen"
by bugzilla-daemon＠bugs.koha-community.org 29 May '24

29 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19324 Bug ID: 19324 Summary: New Inventory workflow eliminates "mark item seen" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org With recent updates to 16.11.09 and the master release, there seem to be 2 functionality changes. The first is the workflow for marking items seen in the inventory tool seems to disappear. The second is Koha is not bringing back results (No data available in table) when you don't compare to a list. Steps to recreate comparing barcodes against a list of results in 16.11.09 and master 1) Upload a file of barcodes with same shelving location 2) Choose option compare barcodes to list of results 3) Filter by library, call number or shelving location 4) Click submit 5) you will be presented with a 2 boxes letting you know the number of items modified : datelastseen set to xx/xx/xxx and the Number of potential barcodes read: xxx 6) No option to mark the results "Mark seen and quit" or "Mark seen and continue" or "Continue without marking" Steps to recreate NOT comparing barcodes against a list of results in 16.11.09 and master 1) Upload a file of barcodes with same shelving location 2) Filter by library, call number or shelving location 3) Click submit 4) you will be presented with a 2 boxes letting you know the number of items modified : datelastseen set to xx/xx/xxx and the Number of potential barcodes read: xxx 5) No data available in table 6) Koha no longer brings back results of the other filtered locations We believe this is where the functionality changes from bug 14399 Fix inventory.pl part two (following 12913) Steps to recreate NOT comparing barcodes against a list of results (16.11.04 & 16.11.07) 1) Upload a file of barcodes with same shelving location 2) Filter by library, call number or shelving location 3) Click submit 5) you will be presented with a 2 boxes letting you know the number of items modified : datelastseen set to xx/xx/xxx and the Number of potential barcodes read: xxx 6) There is an option to mark the results "Mark seen and quit" or "Mark seen and continue" or "Continue without marking" Steps to recreate NOT comparing barcodes against a list of results (16.11.04 & 16.11.07) 1) Upload a file of barcodes with same shelving location 2) Filter by library, call number or shelving location 3) Click submit 5) you will be presented with a 2 boxes letting you know the number of items modified : datelastseen set to xx/xx/xxx and the Number of potential barcodes read: xxx 6) We do not get an option to mark the results "Mark seen and quit" or "Mark seen and continue" or "Continue without marking" 7) This does have a list of results in the table -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 23051] New: Optionally renew fine accruing items when all fines on item are paid off
by bugzilla-daemon＠bugs.koha-community.org 29 May '24

29 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23051 Bug ID: 23051 Summary: Optionally renew fine accruing items when all fines on item are paid off 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 Target Milestone: --- Currently, if a user pays an accruing fine on an overdue item but forgets to renew the item fines start accruing again. If a user pays off the amount outstanding on an item with an accruing fine (accounttype "OVERDUE" & status "UNRETURNED" in 19.05) via the OPAC or self-service, or a member of staff takes payment in the staff client, attempt to automatically renew the item according to circulation rules. This behaviour should be controlled by a new syspref "RenewAccruingItemWhenPaid" which is initially turned off. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 119

[Bug 22666] New: When using authority records in a bibliographic record, the order of the subfields is not sent over
by bugzilla-daemon＠bugs.koha-community.org 29 May '24

29 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22666 Bug ID: 22666 Summary: When using authority records in a bibliographic record, the order of the subfields is not sent over Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- It is possible to reorder subfields in the authority frameworks, but then, when the authority records are used in bibliographic records, the order is not transferred. How to reproduce (for MARC21): 1. Create a 'Topic term' authority 1.1 Go in Authorities 1.2 Click on 'New authority' 1.3 Choose 'Topic term, 1.4 Fill in the mandatory fields (normally 000, 003, 005, 008 and 040$c) 1.5 Click on the tab 1 1.6 Open field 150 1.7 Write in the following information - a: Villages - x: Fiction - z: Québec (Province) 1.8 Use the arrows to move the z subfield up above the x subfield (desired order: a, z, x) 1.9 Save the record 2. Use the authority in a bibliographic record 2.1 Go in Cataloguing 2.2 Click on 'New record' 2.3 Choose 'Default framework' 2.4 Fill in the mandatory fields (normally 000, 003, 005, 008, 040$c, 245$c and 942$c) 2.5 Click on the tab 6 2.6 Click on the 'tag editor' button next to the 650$a subfield 2.7 Search for 'Villages' 2.8 Choose the 'Villages Québec (Province) Fiction' authority EXPECTED RESULT: The subfields should be inserted in the same order as they are in the authority record (a, z, x) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 22613] New: Add /patrons/patron_id/checkouts endpoints
by bugzilla-daemon＠bugs.koha-community.org 28 May '24

28 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22613 Bug ID: 22613 Summary: Add /patrons/patron_id/checkouts endpoints Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com Target Milestone: --- As described in RFC, there should be endpoint in the form /patrons/{patron_id}/checkouts for getting patrons checkouts. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 48

[Bug 17455] New: Add system preference to receive acq order e-mails as BCC
by bugzilla-daemon＠bugs.koha-community.org 24 May '24

24 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17455 Bug ID: 17455 Summary: Add system preference to receive acq order e-mails as BCC 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org There is currently ClaimsBccCopy for receiving serial and acq claim notices in BCC. There should also be an option to receive order emails BCC. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 20184] New: Posibility to add a box to enter a specific page number in authorities result search.
by bugzilla-daemon＠bugs.koha-community.org 24 May '24

24 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20184 Bug ID: 20184 Summary: Posibility to add a box to enter a specific page number in authorities result search. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, It would be a nice addition if in the results page of an authorities search to add a box to enter a specific page number. It could be a box at the top of the search results table where you could enter the page number of your search. This addition would help to search more efficiently the authorities of the local bank. Patrick. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 20611] New: add the ability to set a priority for z39.50 servers
by bugzilla-daemon＠bugs.koha-community.org 24 May '24

24 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20611 Bug ID: 20611 Summary: add the ability to set a priority for z39.50 servers Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Actualy, in the configuration of Z39.50 servers we can check by default a server to launch a faster search but we can not prioritize a server for the search to be done on this server before going to search on another and so classify the result according to the servers that respond to the search. It could be a new column in the page z3950servers.pl where we could designate a number that would refer to a priority in the search results or something else like that.It would be nice to have this possibility. Thanks, Patrick. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 19421] New: Predue Notices should work like Overdue Notices
by bugzilla-daemon＠bugs.koha-community.org 24 May '24

24 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19421 Bug ID: 19421 Summary: Predue Notices should work like Overdue Notices Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently Advance due notices (pre-due) follow the patron's holding branch and it would be more beneficial that they follow the item's holding branch. When a patron takes out an item from another branch, they should receive the information and rules from the library that the item is from as it could be different from their own home branch. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 23241] New: Does misc/bin/koha-index-daemon-ctl.sh still belong in community koha?
by bugzilla-daemon＠bugs.koha-community.org 24 May '24

24 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23241 Bug ID: 23241 Summary: Does misc/bin/koha-index-daemon-ctl.sh still belong in community koha? Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We have had a daemon mode in rebuild_zebra.pl for a long time and have been using that as the default indexing daemon for years.. Should we deprecate the above script to prevent confusion for new users where indexing should just work out of the box without the need for installing external dependancies. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 24143] New: buildQuery should disable Query* on identifier search
by bugzilla-daemon＠bugs.koha-community.org 23 May '24

23 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24143 Bug ID: 24143 Summary: buildQuery should disable Query* on identifier 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: matthias.meusburger(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Currently, QueryWeightFields, QueryFuzzy, QueryStemming, QueryAutoTruncate are disabled in buildQuery in several cases: - Date of Publication - Date of Acquisition - ISBN,ISSN,Standard Number Those modifiers should also be disabled when searching on identifiers. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20