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

[Bug 14377] New: Indicate that a record is suppressed in staff client
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '16

20 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14377 Bug ID: 14377 Summary: Indicate that a record is suppressed in staff client 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: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Would be nice if in the staff client there was some indication that a record you are viewing is suppressed in the OPAC. This would be an XSLT customization. -- You are receiving this mail because: You are watching all bug changes.

1 40

[Bug 7034] New: De-nesting C4::Branch
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '16

20 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7034 Bug #: 7034 Summary: De-nesting C4::Branch Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: paul.poulain(a)biblibre.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org Blocks: 6875 Creating a specific bug report for this particular bit of cleanup. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 4

[Bug 13143] New: add a useful koha-passwd command, to show a password for a Koha instance
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '16

20 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13143 Bug ID: 13143 Summary: add a useful koha-passwd command, to show a password for a Koha instance Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org add a useful koha-passwd command, to show a password for a Koha instance -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 14167] New: Add Koha::Logger based on Log4perl
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '16

20 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14167 Bug ID: 14167 Summary: Add Koha::Logger based on Log4perl Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Koha needs a better logger, and it seems like the best solution would be to take advantage of Log4perl which is already a fully featured logger. We use Log4perl to selectively decide what statements should be logged, and where they should go! -- You are receiving this mail because: You are watching all bug changes.

1 79

[Bug 12750] New: koha-create should be able to configure SRU server for the created instance
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '16

20 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12750 Bug ID: 12750 Summary: koha-create should be able to configure SRU server for the created instance Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 12748] New: Serials - two issues with status of "Expected"
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '16

20 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12748 Bug ID: 12748 Summary: Serials - two issues with status of "Expected" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When on the “Serial collection information” page for a serial (e.g. /cgi-bin/koha/serials/serials-collection.pl?subscriptionid=24) and “Generate next” is clicked, the issue that previously had a status of “Expected” changes to “Late” and a new issue is generated with a status of “Expected”. When the serial with the status of “Late” is selected, and click on “Edit serials” and change the late item's status to “Expected” then one ends up with 2 issues with the status “Expected”. If the status of either of these “Expected” issues is changed to something else (e.g. “Arrived” or “Delete”) it generates a new issue with an “Expected” status, one can never get back to just having one issue “Expected”. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 14406] New: When adding messages in patron account, only first name is shown in pull down
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14406 Bug ID: 14406 Summary: When adding messages in patron account, only first name is shown in pull down Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When you add a note to a patron account using the 'Add messages' link on the details tab in the staff patron account, you are shown a pull down that says: - Other librarians - Katrin (firstname of the patron) I think this is not unusual and not in sync with how we label other similar note fields and features. Suggestions: - Staff / staff client / Internal note - OPAC / full name of the patron etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 10014] New: printcirculationslips missing documentation or obsolete
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10014 Bug ID: 10014 Summary: printcirculationslips missing documentation or obsolete Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de CC: gmcharlt(a)gmail.com System preference printcirculationslips only shows up in the local use tab and misses documentation. If this is still functional we should document it or else remove the pref. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 13703] New: batchRebuildBiblioTables.pl should also update from database to MARC Record.
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13703 Bug ID: 13703 Summary: batchRebuildBiblioTables.pl should also update from database to MARC Record. 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: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When adding a new column to biblio or biblioitems and populating it with legacy data, the MARC Record needs to be updated to match the values in DB, so they can be indexed for searching. Upgrading the batchRebuildBiblioTables.pl -script to make updates upstream (DB columns to MARC Record) and downstream (MARC Record to DB columns), based on the "Koha to MARC mappings". -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 13153] New: Waiting hold checked in at different library doesn't re-route item to correct library
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13153 Bug ID: 13153 Summary: Waiting hold checked in at different library doesn't re-route item to correct library Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal 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 It seems that if an item is triggered at a location as waiting for pickup, if that item falls into the hands of another library by mistake, Koha doesn’t know what to do with it. It just records a local use. It doesn’t try to transfer home or to the library it should be waiting at. Correct behavior should be that if it is scanned at another location other than where the system thinks it is, it should trigger a transfer to where it should be. Right now, the only way to get the item back on course is to go to the holds for that item and change the waiting to priority 1 again, and change any other priorities back one level, if any, and then check the item in again. To reproduce: 1) Place a hold on an item for a patron at LibraryA 2) Check the item in at LibraryA 3) Confirm the hold at LibraryA, the item is now a waiting hold 4) Set your logged in branch to LibraryB 5) Check the item in at LibraryB 6) Notice there is no request to transfer the item to LibraryA I think what should probably happen is the hold status should go from Waiting (W) to In Transit (T), and a transfer should be created. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6