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

[Bug 22802] New: When ordering form a staged file, if funds are populated per item order level fund should not be required
by bugzilla-daemon＠bugs.koha-community.org 07 Jun '23

07 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22802 Bug ID: 22802 Summary: When ordering form a staged file, if funds are populated per item order level fund should not be required Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- To recreate: 1 - Set MarcItemFieldsToOder: homebranch: 975$a holdingbranch: 975$b itype: 975$y nonpublic_note: 975$x public_note: 975$z loc: 975$c ccode: 970$c notforloan: 975$7 uri: 975$u copyno: 975$n quantity: 975$q budget_code: 975$h price: 975$g replacementprice: 975$p 2 - Create a MARC record with a 975 like: =975 \\$aCPL$bCPL$g27.99$oONORDER$q1$p22.39$7-1$yBK$hBUDGET_CODE 3 - Ensure budget code, itype, and branches are valid values for your system 4 - In a basket with create items so to 'on ordering' add the file above 5 - Try to add the order 6 - Order level fund is required -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 19696] New: HoldsQueue.t is failing randomly
by bugzilla-daemon＠bugs.koha-community.org 07 Jun '23

07 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19696 Bug ID: 19696 Summary: HoldsQueue.t is failing randomly Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org https://jenkins.koha-community.org/job/Koha_Master_D8/294/console # Failed test 'Holds queue filling 1st correct hold for default holds policy 'from home library'' # at t/db_dependent/HoldsQueue.t line 295. # got: 'ig5lWyedNiY9jjrOLHEZQMJ' # expected: 'b_8YX7Q_M7PjVyGxX9BsaKf' # Failed test 'Holds queue filling 2nd correct hold for default holds policy 'from home library'' # at t/db_dependent/HoldsQueue.t line 296. # got: 'b_8YX7Q_M7PjVyGxX9BsaKf' # expected: 'ig5lWyedNiY9jjrOLHEZQMJ' # Looks like you failed 2 tests of 44. [19:04:35] t/db_dependent/HoldsQueue.t .................................... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/44 subtests -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 21045] New: Default checkout limit by patron category for all libraries not managed by SIP2
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '23

06 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21045 Bug ID: 21045 Summary: Default checkout limit by patron category for all libraries not managed by SIP2 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: anne-claire.bernaudin(a)univ-rennes1.fr QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Hello We're on Koha 16.05, using selfcheck machines from Nedap. In our circulation rules, we defined Default checkout limit by patron category for "all libraries". This limit is only configured in the "all libraries" page, and not for each library. The Circcontrol syspref is set to "the library you are logged in at". In this configuration, the selfcheck machines, using the SIP protocol, ignore the "Default checkout limit by patron category". For example, for a patron category called "L", the limit is set to 20 documents. I'm able to check out 20 documents in library 1 through the staff client, and then to add some more check outs through the selfcheck machine. Please note that the Default checkout limit by patron category defined for all libraries is correctly managed by the staff client (for a patron having the patron category "L", I can't check out more than 20 documents, whatever library I'm logged in at). Also please note that this problem seems to happen only with selfcheck machines from Nedap. The problem apparently doesn't exist for Bibliotheca selfcheck machines. Could someone confirm this ? Thanks Anne-Claire (from Rennes, France) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 21522] New: Labels incorrectly inheriting some default Bootstrap style properties
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '23

06 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21522 Bug ID: 21522 Summary: Labels incorrectly inheriting some default Bootstrap style properties Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Our global staff client CSS should override more of Bootstrap's default label styling than it does at the moment. This is causing problems because part of the Bootstrap style is "white-space: nowrap" which prevents long text from wrapping. From the mailing list: "I’ve noticed that there’s a translation too long in french in catalogue/moredetail.pl so it’s unreadable. Cf image. Is there’s something to change in the code to allow a longer but clearer translation : Accession date -> Date d'entrée dans les collections" http://lists.koha-community.org/pipermail/koha-devel/2018-October/044845.ht… -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 22338] New: illrequests.notesopac is editable by both patron and staff
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '23

06 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22338 Bug ID: 22338 Summary: illrequests.notesopac is editable by both patron and staff Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no Target Milestone: --- Was that intended? It seems a bit weird to have a field for communnicating that both parties can edit. Especially if this field is used for information that could be contested, like a due date. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 22285] New: OPAC shows too much info about ILL requests
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '23

06 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22285 Bug ID: 22285 Summary: OPAC shows too much info about ILL requests Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no Target Milestone: --- When ILL is enabled, patrons get an extra "tab" in "my summary" in the OPAC, called "your interlibrary loan requests". This page shows a table of basic info about ILL requests for that patron, along with a button that says "View". Clicking on this button shows a lot of information about a single request. The first part of the page has a heading of "Details from library" and contains the same fields as the table on the previous page, along with a field for notes. (It looks like this field can be edited both by the patron and by librarians, which seems kind of odd, but that is better left for another bug.) The second part is labeled "Details from <supplier/backend>", and this is the problematic bit. It is identical to the information displayed to librarians in the backend, so it might contain notes that are not meant for the patron to see. The data in this section comes from Koha::Illbackends::Libris::Base:metadata(). Could it be possible to give this sub a parameter so that it would "know" if it is serving data for the OPAC or the intranet, and choose which data to display based on that? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 19044] New: Add BDS integration
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '23

02 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19044 Bug ID: 19044 Summary: Add BDS integration 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: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Some UK Koha users want to use BDS to supply their book cover images. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 18586] New: Create module to mint RDF subject URIs
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '23

02 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18586 Bug ID: 18586 Summary: Create module to mint RDF subject URIs 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In the relational database, we use biblionumber as the ID for bibliographic records, but a triplestore we need to use a RDF URI. So I'm going to put together a module with a little method for minting URIs. While we could just agree on a convention, it probably makes sense to use the convention in the module and then use the module elsewhere to keep things consistent. -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 18713] New: Add support for named graphs and rfds:seeAlso to Koha:: RDF
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '23

02 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18713 Bug ID: 18713 Summary: Add support for named graphs and rfds:seeAlso to Koha::RDF 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When I download RDFXML via OAI-PMH, I delete existing named graphs and create new named graphs. This functionality isn't specific to OAI-PMH, so I'm putting it in Koha::RDF. There is also a method for adding rdfs:seeAlso to a $subject and an $object. In my case, I'm linking a Koha record to an imported record. It's a generic relationship though, which will be useful in many other scenarios, so it's going in Koha::RDF too. -- You are receiving this mail because: You are watching all bug changes.

1 54

[Bug 22959] New: Using the help feature when in the Patron Category Admin page, should bring user to that section in the manual
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '23

01 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22959 Bug ID: 22959 Summary: Using the help feature when in the Patron Category Admin page, should bring user to that section in the manual Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff Client 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: --- With the introduction of the new help button opening up the manual in Koha 18.11, clicking on Help when in the patron category set up in the administration module does not bring the user to that portion of the manual, instead it goes to the main page of the manual. It should go here : https://koha-community.org/manual/18.11/en/html/administration.html#patron-… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1