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

[Bug 21591] New: Data inconsistencies - Item types and biblio level
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '20

20 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21591 Bug ID: 21591 Summary: Data inconsistencies - Item types and biblio level Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 bug 21150 added a script to check for missing item level itemtypes - it doesn't like when both the item and the record are missing itemtype -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 22328] New: Inconsistent behavior throughout acquisitions for determining whether or not an item as been received
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '20

20 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22328 Bug ID: 22328 Summary: Inconsistent behavior throughout acquisitions for determining whether or not an item as been received Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- When an aqorders line has quantityreceived>0 but datereceived is NULL, fund totals shows inconsistently across acquisitions. To test: - create an order with quantityreceived=1 and datereceived NULL (this may need to be done from the command line) - find the relevant fund in the All Available Funds table at acqui-home.pl, note that the order is reflected in the Spent total - Click through to spent.pl for the relevant fund, note that the order is not reflected here - Click through to ordered.pl for the relevant fund, note that the order is not reflected here either I'll acknowledge that it shouldn't really be possible for an item to have a quantityreceived without a datereceived -- I haven't yet figured out how the library I found this on did it -- but the inconsistent logic is an issue nonetheless. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 24012] New: Display 'Locked' budget in red
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '20

20 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24012 Bug ID: 24012 Summary: Display 'Locked' budget in red Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I find it illogical that the 'Locked' in locked budget is displayed in green. Shouldn't it be displayed in red? To reproduce: 1- Go to Administration 2- Click on Budgets 3- Add a new budget and check the 'Lock budget' box 4- Click on the 'Inactive budgets' tab 5- Note that 'Locked' is displayed in green -- You are receiving this mail because: You are watching all bug changes.

1 33

[Bug 24306] New: Add debug option to koha-indexer
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '20

20 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24306 Bug ID: 24306 Summary: Add debug option to koha-indexer 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Would be nice to be able to raise logging level and see errors from the indexer -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 21066] New: Use opac_news.timestamp as a real timestamp or add opac_news.updated_on ?
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '20

20 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21066 Bug ID: 21066 Summary: Use opac_news.timestamp as a real timestamp or add opac_news.updated_on ? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org I would propose to use the opac_news.timestamp field readonly and fill/update it automatically via SQL. Or do we still need the original publish date and add a modified/updated_on timestamp? What do you think? -- You are receiving this mail because: You are watching all bug changes.

1 56

[Bug 25639] New: Add search queries to HTML so queries can be retrieved via JS
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '20

20 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25639 Bug ID: 25639 Summary: Add search queries to HTML so queries can be retrieved via JS Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org For integrations or custom code it would be nice to have access to the search strings used in Koha to the html, like loggedinbranch etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 25828] New: Update cpanfile for 20.05 release cycle
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '20

19 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25828 Bug ID: 25828 Summary: Update cpanfile for 20.05 release cycle Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com This patch updates the cpanfile for the 20.05 release cycle -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 25958] New: Allow LongOverdue cron to include/exclude specified lost values
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '20

18 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25958 Bug ID: 25958 Summary: Allow LongOverdue cron to include/exclude specified lost values Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When lost items are not marked as returned, they are still subject to the long overdue cron, so an item that has already been marked Lost may automatically roll to Long Overdue. In some cases, a library may not want that lost value to change. This becomes especially important with the introduction of Claims Returned, which uses a variety of lost. I'd like to see two options added to the cron. The first to take a list of lost values that are subject to long overdue, the second to take a list of lost values that are not subject to long overdue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 25167] New: Fix to a fix wrong inventory results
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '20

18 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25167 Bug ID: 25167 Summary: Fix to a fix wrong inventory results 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: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Hi, Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12913 solves the case when notforloan filter is not used, but it breaks the case when a filter is used. Regards Didier -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 26487] New: Add all MARC flavours for not-onloan-count search field
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '20

18 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26487 Bug ID: 26487 Summary: Add all MARC flavours for not-onloan-count search field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com In admin/searchengine/elasticsearch/mappings.yaml the search field not-onloan-count is defined for MARC21 on 999x. This should be for all the MARC flavours, like in Zebra config. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14