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

[Bug 6559] New: super librarians can only assign holding to current location
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '15

06 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6559 Bug #: 6559 Summary: super librarians can only assign holding to current location Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: spalding(a)senylrc.org QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com I have 17 libraries setup as independent branches. I also have patron #5 setup as a super librarian. Prior to 3.2.6 this patron was able to access a bib record and add multiple holdings at different locations. Now since that upgrade and still in 3.4.1, that person has to change her location setting on the top right. Then has to add that item to that location, go back change her location again. Then add that location item information, there are some days she has to do this multiple times and is a major work flow issue. The default kohaadmin account is able to do this work with out any problems. -- 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 2

[Bug 6691] New: can't place hold on specific copy
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '15

06 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6691 Bug #: 6691 Summary: can't place hold on specific copy Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All URL: cgi-bin/koha/reserve/request.pl?biblionumber=504 OS/Version: All Status: NEW Severity: critical Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Once again I think this is a T:T issue - if not please reassign. When you're trying to place a hold on an item that isn't usually allowed to be put on hold (with override turned on and logged in as a superlibrarian) you get the usual errors but when you say you want to place the hold anyway nothing happens. See attached and note this is with item specific holds. -- 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 7

[Bug 6515] New: can't set advanced notice days
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '15

06 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6515 Bug #: 6515 Summary: can't set advanced notice days Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Notices AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org The Advance Notice 'Days in advance' selector shows a 0 even after choosing another value. If I edit this region and choose to be notified 10 days in advance and save, this value reverts back to 0. I tested this on master as of this morning - and am kind of hoping it's just a template issue. -- 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 6344] New: Hold priority displayed incorrectly when "Toggle Lowest Priority" option is used
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '15

06 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6344 Bug #: 6344 Summary: Hold priority displayed incorrectly when "Toggle Lowest Priority" option is used Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Hold requests AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com If I toggle the lowest priority on a hold to "pin" it to the bottom of a hold's priority list, any holds I place after that will be displayed as being of lower priority. 1. Place a hold. 2. Set that hold to "lowest priority." 3. Place another hold. This hold will appear below the first. Running build_holds_queue.pl does not affect the appearance of the priorities. Only after one of the holds has been fulfilled will the priorities display correctly. 4. Check in a copy of the on-hold title. 5. The item will be allocated for the correct patron (not the one "pinned" to the bottom of the list." 6. Confirm. Now the hold list will appear correctly: The "pinned" hold will appear at the bottom. -- 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 2

[Bug 5985] New: Incorrect date in budgets and failed to edit funds children
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '15

06 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5985 Bug #: 5985 Summary: Incorrect date in budgets and failed to edit funds children Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nunyo(a)masmedios.com QAContact: koha-bugs(a)lists.koha-community.org Created attachment 3496 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=3496 Image There are various problems: 1. When you create a budget, you can set an end date prior to the start date. 2. I can´t create funds children greater than the fund, but I can edit the children and make them bigger than the fund. 3. I can cut the fund budget but is lower than that of a child. After this, I can increase the child budget even above the total budget. And then I can also create new children over the fund budget but not above the total budget. -- 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 5

[Bug 5566] New: Misleading grouping of lost items in staff client search results
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '15

06 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5566 Summary: Misleading grouping of lost items in staff client search results Change sponsored?: --- Product: Koha Version: HEAD Platform: All URL: /cgi-bin/koha/catalogue/search.pl OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Created attachment 2931 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2931 Screenshot of the described problem If a title has multiple items with different lost statuses, the output of search results in the staff client is misleading because of the way statuses are labeled. This is true if: - items are the from the same branch - items have the same call number - items have different values for itemlost In the example screenshot 2 Athens DVDs are Lost (lost) and one is Lost (missing). These items should either be grouped by authorized value category ("LOST") or each line should output the authorized value description ("Lost","Missing") to make it clear why they are grouped separately. -- 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 5196] New: 006 subfields 01-17 should be populated depending on the 00 value
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '15

06 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5196 Summary: 006 subfields 01-17 should be populated depending on the 00 value Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Estimated Hours: 0.0 And depending on what value is selected for 006/00, there are need more options for 006/01 through 006/17 as well. All of these can be found at: http://www.loc.gov/marc/bibliographic/bd006.html. -- 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 5198] New: HOLDPLACED being logged in patron messages
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '15

06 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5198 Summary: HOLDPLACED being logged in patron messages Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Notices AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Created attachment 2601 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2601 hold placed logged on patron record When the hold placed message is sent it goes out to the librarian only. I have confirmed this in the message queue in the database. However as you see in the attachment the message is being logged on the patron record for some reason. This is confusing to librarians and should not happen. The default message also looks like it's formatted for being sent to the patrons - not to the librarians so the message should be changed to make it clear (at least in new installs) that this message goes to librarians, not patrons. -- 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 5404] New: C4::Koha::subfield_is_koha_internal_p no longer serves a purpose
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '15

06 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5404 Summary: C4::Koha::subfield_is_koha_internal_p no longer serves a purpose Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: gmcharlt(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Apparently older versions of Koha considered a MARC subfield in the frameworks that had a code longer than one character to be reserved for internal use. This no longer applies, so the routine and the last couple uses of it can be removed. -- 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 2

[Bug 5170] New: budgets not giving user error messages on fail
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '15

06 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5170 Summary: budgets not giving user error messages on fail Change sponsored?: --- Product: Koha Version: HEAD Platform: All URL: /cgi-bin/koha/admin/aqbudgetperiods.pl?op=add_form OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 When you are adding budgets if you enter something wrong (say the date) you don't get an error message in the staff client - you just get brought to the list of budgets where you don't see the budget you just tried to add. This tool needs some user friendly error messages to make it clear why the budget isn't being added. -- 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