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

[Bug 6007] New: Checking 'Display only used Tags/Subfields' on MARC framework page results in unusable output
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '15

30 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6007 Bug #: 6007 Summary: Checking 'Display only used Tags/Subfields' on MARC framework page results in unusable output Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All URL: /cgi-bin/koha/admin/marctagstructure.pl OS/Version: All Status: NEW Severity: normal Priority: P5 Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 3531 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=3531 Screenshot of the problematic display When looking at tags for a particular MARC framework, if you check the 'Display only used Tags/Subfields' the page automatically reloads and the table redisplays in a way that is unusable. The table columns no longer match the header and there are no longer links for editing, deleting, etc. -- 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 17

[Bug 8796] New: patron cards not starting on designated card
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '15

30 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8796 Priority: P5 - low Change sponsored?: --- Bug ID: 8796 Assignee: cnighswonger(a)foundations.edu Summary: patron cards not starting on designated card Severity: major Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: rel_3_8 Component: Label printing Product: Koha When I put a number in "Enter starting card number" I am expecting it to start printing cards in that position the way it does in the label creator. However it always starts in the first position. I have tested and confirmed this in 3.8.4 and Master (as of this morning). -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 10222] New: Error when saving Demco label templates
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '15

29 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10222 Bug ID: 10222 Summary: Error when saving Demco label templates Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label printing Assignee: cnighswonger(a)foundations.edu Reporter: oleonard(a)myacpl.org If you open either of the Demco label templates (loaded by the sample data) and click "save" without making any changes you will get an error: Can't bless non-reference value at C4/Creators/Profile.pm line 92. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 12203] New: can't print circ receipts in Chrome
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12203 Bug ID: 12203 Summary: can't print circ receipts in Chrome Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This is in Koha 3.14.x and master. If you try to print any of the 3 receipt options on the circ page while in chrome nothing happens. It works a-ok in Firefox -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 9117] New: Reports hierarchies management improvements
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9117 Bug ID: 9117 Summary: Reports hierarchies management improvements Classification: Unclassified Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Reports Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com - Filter by groups using tabs - Filter by subgroups using a dropdown list under each tab - Allow to create new group and subgroups when building a new report or editing an existing report (no need to go through admin AV interface) + Possibility to duplicate a report (new link in the table) -- You are receiving this mail because: You are watching all bug changes.

1 52

[Bug 12217] New: Funds not matching up
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12217 Bug ID: 12217 Summary: Funds not matching up Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 28120 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=28120&action=edit Fund lists on main page See attached images. On the acquisitions main page (cgi-bin/koha/acqui/acqui-home.pl) it lists what you have ordered against a fund. When you click the amount (in my images the $238.48) it shows me what makes up that amount (cgi-bin/koha/acqui/ordered.pl?fund=3&fund_code=HDCORTH14) - but it doesn't match. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 12235] New: Logs organized inconsistently
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12235 Bug ID: 12235 Summary: Logs organized inconsistently Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org The database structure for the transaction logs doesn't work very well. When you view the "Modification log" for a patron or a bib record, you're viewing the logs for the "object" with that borrowernumber or biblionumber. However, this often has surprising results, especially in the "Catalog" module. For instance, the "Modification log" for bib record #1 will show you the logs for bib record #1...and item record #1. However, if won't show you the logs for item record #2, which is attached to bib record #1. This is a problem. While it might be fair that the "Modification log" for bib record #1 shouldn't have to show the logs for its attached items, it shouldn't show unrelated results for other items. -- A structure more in line with expectation might be something like: -System user (i.e. the librarian) -Biblionumber -Itemnumber (or maybe AttachedNumber so this could be either items or serials) -Info Or at least some other way of differentiating what is in the "object" column. I had to perform 3 different (arguably "expert") queries just to find out that item #2 from bib record #1 was checked in by patron #3. Why? First query: Retrieve bib record...don't find correct item information using bib ionumber object Second query: Retrieve item record using correct itemnumber object... Third query: Search for itemnumber in "info" column, so that it brings up the circulation transaction. -- I'm tempted to write a patch for this, but I wonder about pre-existing logs. Do we try to convert them to match a new schema, or do we ignore them, or do we back them up then wipe the table for fresh logs? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 10680] New: "Modification log" gives wrong data
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10680 Bug ID: 10680 Summary: "Modification log" gives wrong data Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When viewing a record, the "Modification log" tab on the left hand side should display the modifications for that biblionumber, but instead it will pull the modifications for the itemnumber instead. That is, if the record you are viewing has a biblionumber of 42, and you follow the "Modification log" link, you will be seeing the modifications for the item whose itemnumber is 42 instead! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 7046] New: subscription renewal period should be a pull down
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7046 Bug #: 7046 Summary: subscription renewal period should be a pull down Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Serials AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Created attachment 5938 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=5938 renew subscription length When adding a new subscription there is a pull down menu for the subscription length, but when you renew it the length is 3 text boxes which implies that you can fill them all in - or that you have to fill them all in, but I assume you're just supposed to fill in one like you do when you add a subscription. -- 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 12262] New: Searching patrons by extended attribute should be a search field
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12262 Bug ID: 12262 Summary: Searching patrons by extended attribute should be a search field 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: fridolyn.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When searching for patrons, the search is always also performed on extended attribute, even on when a field is selected (like email, phonenumber ...). And the results which matched only on an extended attribute can not be easily identified. The search on extended attribute should be a field. Or for a start the search on extended attribute could be enabled only for standard field. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3