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

[Bug 16113] New: Specify due date for batch check out
by bugzilla-daemon＠bugs.koha-community.org 05 Mar '19

05 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16113 Bug ID: 16113 Summary: Specify due date for batch check out 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: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, Currently , we can not manually select a due date in the batch check out tool. This could be a system preference like specifyDueDate or SpecifyReturnDate. Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 21720] New: Convert C4::Circulation::AddIssuingCharge to use Koha::Account->add_debit
by bugzilla-daemon＠bugs.koha-community.org 05 Mar '19

05 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21720 Bug ID: 21720 Summary: Convert C4::Circulation::AddIssuingCharge to use Koha::Account->add_debit 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org All account handling should go via the Koha::Account class. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 21728] New: Update C4::Reserves::ChargeReserveFee to use Koha::Account->add_debit
by bugzilla-daemon＠bugs.koha-community.org 05 Mar '19

05 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21728 Bug ID: 21728 Summary: Update C4::Reserves::ChargeReserveFee to use Koha::Account->add_debit 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org All account handling should go via the Koha::Account class. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 21722] New: Update C4::Accounts::chargelostitem to use Koha::Account->add_debit
by bugzilla-daemon＠bugs.koha-community.org 05 Mar '19

05 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21722 Bug ID: 21722 Summary: Update C4::Accounts::chargelostitem to use Koha::Account->add_debit 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org All account handling should go via the Koha::Account class. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 20649] New: C4::Auth should use C4::Context->IsSuperLibrarian()
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '19

04 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20649 Bug ID: 20649 Summary: C4::Auth should use C4::Context->IsSuperLibrarian() Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Depends on: 20479 We had a lot of trouble with superlibrarian checks in the past, which is why we introduced C4::Context->IsSuperLibrarian(). C4::Auth should use it instead of: 06 && $flags && $flags->{superlibrarian} != 1 http://git.koha-community.org/gitweb/?p=koha.git;a=blobdiff;f=C4/Auth.pm;h=… Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20479 [Bug 20479] Superlibrarians cannot log into opac -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 19635] New: OAI-PMH deleted records are now default and are listed first
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '19

04 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19635 Bug ID: 19635 Summary: OAI-PMH deleted records are now default and are listed first Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It seems bug 15108 made some changes to which records are served up first by the OAI server. When making a basic request with no token, i.e.: http://localhost:8080/cgi-bin/koha/oai.pl?verb=ListRecords&metadataPrefix=m… You get any deleted records first. When continuing if you have more than 50 deleted records the resumptionToken also includes deleted records We have services harvesting the entire catalog that don't expect deleted records first. I am not seeing a way to prevent them, and wonder if they should not be served first. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 21252] New: Koha::Patron->do_check_for_previous_checkout should take Koha::Item as parameter
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '19

01 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21252 Bug ID: 21252 Summary: Koha::Patron->do_check_for_previous_checkout should take Koha::Item as parameter 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 21401] New: Account offsets should save the transacting library
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '19

01 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21401 Bug ID: 21401 Summary: Account offsets should save the transacting library 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[Bug 19460] New: Limit total number of checkouts allowed per patron by patron category code
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '19

28 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19460 Bug ID: 19460 Summary: Limit total number of checkouts allowed per patron by patron category code Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: kyle(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Goal of development: Limit total number of checkouts allowed per patron by patron category code Work to be done: 1) Add new circulation rule "Max checkouts ( global, most restrictive )" to circulation rules. 2) Modify C4::Circulation::TooMany to respect this new rule 3) Modify script and template to show errors relating to this new rule -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 21247] New: Cannot add more than one emoji across the entire database as a tag
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '19

27 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21247 Bug ID: 21247 Summary: Cannot add more than one emoji across the entire database as a tag Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Well I suppose that's not really fair - you can add them but you can only see the first one in the approval list, and on the detail/results pages. To replicate: Add a tag, such as 😍 to a biblio in the OPAC try to add another emoji, such as 🎶 In my 18.05, this won't work and the second tag is never inserted into tags_approval, though it is inserted into tags_all. It seems to be mysteriously approved as under the first emoji added, as well. I checked the DB encoding, it seemed correct. The database I was testing with was an upgraded one, 3.20 -> 18.05.02 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6