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

[Bug 10364] New: add a way to partially receive an order without creating a new order
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10364 Bug ID: 10364 Summary: add a way to partially receive an order without creating a new order Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathieu.saby(a)univ-rennes2.fr At present, if we order 3 copies of a document, and only 2 are received, Koha creates a new order with the 3rd copy. As a consequency, if we print again the basketgroup, there is a new line. I would prefer Koha not to create a new order, so that the content of baskets and basket groups will not be altered by reception. M. Saby -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 5575] New: 3.4 BibLibre circ & members improvements
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5575 Summary: 3.4 BibLibre circ & members improvements Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: paul.poulain(a)biblibre.com ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 As described on the wiki : http://wiki.koha-community.org/wiki/Enhancements_to_the_display_of_extended… http://wiki.koha-community.org/wiki/Enhance_renewals_parameters http://wiki.koha-community.org/wiki/Ergonomics_of_smart-rules_and_circulati… http://wiki.koha-community.org/wiki/Fine_tuning_of_circulation_policies_RFC http://wiki.koha-community.org/wiki/AllowOnShelfHolds http://wiki.koha-community.org/wiki/Enhancements_to_debarred_patron http://wiki.koha-community.org/wiki/Transfers_-_enhancements -- 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 104

[Bug 5765] New: patron messaging form template tests for SMS inconsistently
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5765 Summary: patron messaging form template tests for SMS inconsistently Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P5 Component: MARC Authority data support AssignedTo: gmcharlt(a)gmail.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Estimated Hours: 0.0 For the header row of the table, the test is performed on whether SMSSendDriver is defined, but for each row, the first test is on whether 'transport_sms' is defined for that notice, then whether the driver exists. If an sms transport is defined for a notice (or even if the thinks it is), this will add an extra column of '--' to the table, forcing everything over by one, and the 'do not notify' column off the table. Reversing the order of the <TMPL_IF>'s in the messaging_preference_form.inc should resolve this. -- 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 6

[Bug 7468] New: Add label to batch by barcode range
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7468 Bug #: 7468 Summary: Add label to batch by barcode range Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label printing AssignedTo: cnighswonger(a)foundations.edu ReportedBy: wrmslibrary(a)gmail.com QAContact: koha.sekjal(a)gmail.com It would be nice to be able to add an item to a label batch by barcode without having to scan the barcode. If a barcode has not yet been printed, it cannot be scanned to add the item to a label batch. Would like to be able to search by barcode range to add items to a label batch. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 2

[Bug 10203] New: print labels based on range of barcodes
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10203 Bug ID: 10203 Summary: print labels based on range of barcodes Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label printing Assignee: cnighswonger(a)foundations.edu Reporter: nengard(a)gmail.com It would be nice to enter a first and last barcode on the label creator to add barcodes in a batch to the label creator for printing. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 8042] New: Batch numbers aren't committed as used until an item is added
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8042 Priority: P5 - low Change sponsored?: --- Bug ID: 8042 Assignee: cnighswonger(a)foundations.edu Summary: Batch numbers aren't committed as used until an item is added Severity: normal Classification: Unclassified OS: All Reporter: shawn(a)pennmanor.net Hardware: All Status: NEW Version: rel_3_8 Component: Label printing Product: Koha We ran into an issue where 2 branches decided to create a label batch around the same time. Both had the blank batch screen up and they were the same batch number. We have found that the batch isn't actually committed as being used until the first item is added. In this case we had 2 branches adding items to the same batch number. This can be duplicated by creating a new batch in 2 separate browsers. If party 2 refreshes the screen after party 1 enters an item to the batch they are presented with a new batch but if they don't refresh (which most wouldn't) then both parties are editing the same batch. We have tested it in 3.6 and 3.8. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 5169] New: name/rename label batches
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5169 Summary: name/rename label batches Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Label printing AssignedTo: cnighswonger(a)foundations.edu ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 It would be very helpful if there was a way to name and rename batches of labels. Right now they're named in numerical order which can be confusing if you have a lot of batches. -- 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 1

[Bug 5686] New: search in tamil
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5686 Summary: search in tamil Change sponsored?: --- Product: Koha Version: rel_3_0 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: novamcccharles(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 i m using koha 3.00.06. Tamil search should be enabled for title search So kindly help be in solving this bug -- 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 3

[Bug 6382] New: Automatic Status Changing on Check In
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6382 Bug #: 6382 Summary: Automatic Status Changing on Check In Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Submitted on behalf of Henry Bankhead in search of feedback: We are used to being able to change at items "status" w/ horizon by just checking it in. Think of the not for loan status for example. So, if it was in mending or workroom and was checked in it would become available. Also if it was in receives status, it would move to cataloging and then to in if you checked it in twice. Originally I though Koha did this because the not for loan "status"s have numerical values. So I assumed they would move from -1, to -1, to zero (available) but evidently this is not the case. Can you see that this would be highly desirable from a workflow standpoint? What would it take to make Koha do this? -- 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 3

[Bug 9716] New: opaclayoutstylesheet and opaccolorstylesheet must be filled in for CCSR
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9716 Bug ID: 9716 Summary: opaclayoutstylesheet and opaccolorstylesheet must be filled in for CCSR Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nengard(a)gmail.com opaclayoutstylesheet and opaccolorstylesheet need to have their default values of opac.css and colors.css for the CCSR theme to work. If they are left blank they look for the css files in the prog folder. -- You are receiving this mail because: You are watching all bug changes.

1 8