May 2017 - Koha-bugs - lists.koha-community.org

[Bug 16580] New: Explain the link between the autoBarcode preference and the cataloging plugin
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '19

02 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16580 Bug ID: 16580 Summary: Explain the link between the autoBarcode preference and the cataloging plugin Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you have the 'barcode.pl' plugin enabled for the barcode field in your MARC framework, but the 'autoBarcode' preference is turned off, the plugin will appear to be active but won't do anything. I think there ought to be text explaining the connection, to be shown both on the system preference itself and when the barcode plugin is selected during framework editing. Or is there a time when one does something without the other? -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 18001] New: LocalHoldsPriority can cause multiple holds queue lines for same hold request
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '19

31 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18001 Bug ID: 18001 Summary: LocalHoldsPriority can cause multiple holds queue lines for same hold request Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If LocalHoldsPriority is enabled, and a record level request has more than one item that could fill that hold, there is a possibility that a holds queue row will be generated for the request for each of the available items! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 18322] New: Add facets for ccode to zebra
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '19

30 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18322 Bug ID: 18322 Summary: Add facets for ccode to zebra Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: brendan(a)bywatersolutions.com, jonathan.druart(a)bugs.koha-community.org, katrin.fischer(a)bsz-bw.de, marjorie.barry-vila(a)ccsr.qc.ca, nick(a)bywatersolutions.com, testopia(a)bugs.koha-community.org, tomascohen(a)gmail.com Depends on: 17169, 18068 Blocks: 18235 If we're going to add it for elasticsearch, it ought to also be there for zebra ;) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17169 [Bug 17169] Add facets for ccode to elasticsearch https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18068 [Bug 18068] Elasticsearch (ES): Location and (home|holding)branch facets mixed https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18235 [Bug 18235] Elastic search - Configurable facets -- You are receiving this mail because: You are watching all bug changes.

1 52

[Bug 17248] New: Koha::AuthorisedValues - Remove GetKohaAuthorisedValueLib
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '19

28 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17248 Bug ID: 17248 Summary: Koha::AuthorisedValues - Remove GetKohaAuthorisedValueLib Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 17216 Blocks: 15799 The subroutine C4::Koha::GetKohaAuthorisedValueLib just retrieves a description (lib) for a given authorised value. We can easily replace it using: Koha::AuthorisedValues->search({ category => $cat, authorised_value => $av })->lib or Koha::AuthorisedValues->search({ category => $cat, authorised_value => $av })->opac_description Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15799 [Bug 15799] Move authorised values related code into Koha::AuthorisedValues - part 2 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17216 [Bug 17216] Add a new table to store authorized value categories -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 18549] New: There should be a warning that logging out of Koha will leave browser session logged in to OAuth
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18549 Bug ID: 18549 Summary: There should be a warning that logging out of Koha will leave browser session logged in to OAuth Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org >From bug 16892 Nick: For CAS we have casLogout - can we have something similar here? I think disconcerting if a patron signs in via google, signs out of Koha and walks away leaving their google auth intact unintentionally Mark: This is the problem. If you have multiple tabs, let's say gmail in one, and Koha in the other. If Koha does a forced logout, then your gmail tab will be affected. This is the problem that is widely known. I was thinking of actually doing another bug to drop-down choose what kind of log out. Martin: A federated logout is actually pretty rare in my experience, though it is possible. As you say Mark, it 'feels' strange to the user that logging out of seemingly unrelated apps can have the knock on effect of logging out apps in other tabs that happen to share an aouth2 openid connect identity provider. On a related note, I'm not sure I saw any code out end to support such a federated logout triggered by another service in our end either... but perhaps I missed it ;) Nick: Perhaps if OAuth is activated just a note added that when you log out of Koha you may still be logged in via google? I agree a user with many tabs open may not expect this, but a patron using a shared machine in the library who signs in to place a hold or renew may never visit their email or expect that they have signed in to that. I think a pop-up when logging out to say "Hey, you are logged in to google, and they know lots of stuff about you" wouldn't hurt, who can say if it would help :-) Mark: Perhaps this type of discussion should happen on another bug report, as this bug has nothing to do with logging out. :) Also, yes, some sort of warning should be displayed, somewhere, somehow. Nick: It can happen here now :-) -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 18710] New: Wrong subfield modified in batch item modification
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '19

17 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18710 Bug ID: 18710 Summary: Wrong subfield modified in batch item modification Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In Tools > Batch item modification, one can modify or delete a subfield. When deleting a subfield et modifying another, the wrong subfield gets modified. -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 16111] New: RSS feed for OPAC search results has wrong content type
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '19

10 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16111 Bug ID: 16111 Summary: RSS feed for OPAC search results has wrong content type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org As a result of (ancient) commit f6e1214c, OPAC search result RSS feeds come over with the content type text/html. It should be at least text/xml, and with the demise of Internet Explorer 6, arguably application/rss+xml. The cause: prior to that commit, setting the CGI parameter format to rss2 resulted in passing "rss" as the content type parameter to output_with_http_headers; after that commit, rss2 was no longer properly recognized when setting that parameter. The main user-visible consequence is that clicking on the RSS link in Chrome (when no feed-reader plugin is installed) renders the feed as HTML rather than XML. -- You are receiving this mail because: You are watching all bug changes.

1 115

[Bug 18707] New: Background jobs post disabled inputs
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '19

08 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18707 Bug ID: 18707 Summary: Background jobs post disabled inputs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org For example, in Tools > Batch item modification input of deleted subfields are disabled. This form is posted using background job via JS code. Looks like this JS code converts a POST form into a GET URL, including inputs that are disabled : koha-tmpl/intranet-tmpl/prog/js/background-job-progressbar.js function submitBackgroundJob(f) { ... $(':input', f).each(function() { ... -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 18514] New: Allow library to search their Koha and Overdrive collections using ElasticSearch
by bugzilla-daemon＠bugs.koha-community.org 04 Oct '19

04 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18514 Bug ID: 18514 Summary: Allow library to search their Koha and Overdrive collections using ElasticSearch 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: chris(a)bigballofwax.co.nz QA Contact: testopia(a)bugs.koha-community.org Building on the Elasticsearch and Overdrive work, this feature will allow users to run a cronjob to populate their elastic index with collection information from Overdrive. This makes both local Koha records, and Overdrive ones searchable. This bug will add the code to fetch and index the records, and to search and display them in the OPAC Subsequent bugs will add the detail display to the staff side -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 16284] New: Borrower Previously Checked Out: Serials
by bugzilla-daemon＠bugs.koha-community.org 12 Sep '19

12 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16284 Bug ID: 16284 Summary: Borrower Previously Checked Out: Serials Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.sassmannshausen(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In discussion of Bug 6909, Radek Šiman raised the following additional concerns around CheckPreviousCheckouts functionality: "Inspecting the last attachment 50286 [details] [review] I cannot find if periodical biblios are well processed. This special case concerns a scenario where a borrower is about to get another item of the same periodical title. In such a situation we need to check if the same item was already issued and not the same biblio only. There are borrowers ckecking-out several items if the same title at once. It seems to me that the current solution would ask for N-1 items to "Checkout anyway?". We should ask for repeating items of periodicals only." This bug is for the discussion and resolution of this additional feature. Best wishes, Alex -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 47