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

[Bug 7156] New: singleBranchMode description wrong
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '14

11 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7156 Bug #: 7156 Summary: singleBranchMode description wrong Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: nengard(a)gmail.com QAContact: ian.walls(a)bywatersolutions.com CC: gmcharlt(a)gmail.com This preference says it doesn't let people give their branch in the OPAC, but when it was set to don't allow i couldn't change the branch in the staff client. -- 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 1

[Bug 6896] New: searching an acq date finds due date instead
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '14

11 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6896 Bug #: 6896 Summary: searching an acq date finds due date instead Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org In searching for 09-05-2011 acquisition date, I get items due on 09-05-2011. It looks like somehow the date due is getting dumped into the acqdate search index. What these search results appear to be saying is that my system doesn't have any items that are shown as acquired on 2011-09-05. The results should be empty, but the checked out items are showing instead. -- 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 8673] New: Create new authority
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '14

11 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8673 Priority: P5 - low Change sponsored?: --- Bug ID: 8673 CC: gmcharlt(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: Create new authority Severity: major Classification: Unclassified OS: Linux Reporter: hend.eleraky(a)bibalex.org Hardware: Other Status: NEW Version: rel_3_6 Component: Staff Client Product: Koha Created attachment 11773 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=11773&action=edit duplicate authority error i tried to create new authority with no data [as a testing case] when i click on save i got an error to enter the mandatory fields then i click again on save i get "duplicate authority record :ahmed" although i don't have an authority record "ahmed..... [i searched for it in authorities i get results so i deleted them all .... i still get results for authority "ahmed " but i when i click on "Details" i get "record doesn't exist " ] Attached a screen shot showing this problem Also, when i try to return to the original authority by clicking on "original authority" i got an error >>> 2nd attachment shows this issue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 8188] New: OPAC allow hold date in future is controlled by staff-side preference
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '14

11 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8188 Priority: P5 - low Change sponsored?: --- Bug ID: 8188 CC: gmcharlt(a)gmail.com Assignee: koha.sekjal(a)gmail.com Summary: OPAC allow hold date in future is controlled by staff-side preference Severity: major Classification: Unclassified OS: All Reporter: oleonard(a)myacpl.org Hardware: All Status: NEW Version: master Component: Hold requests Product: Koha The OPAC's "Allow hold date in future" feature only works if the "AllowHoldDateInFuture" preference is enabled. Enabling the "OPACAllowHoldDateInFuture" preference has no effect. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 7025] New: C4::Items depends on C4::Reserves (which in turn depends on C4::Items...)
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '14

11 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7025 Bug #: 7025 Summary: C4::Items depends on C4::Reserves (which in turn depends on C4::Items...) Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org C4::Items uses a single subroutine from C4::Reserves, CheckReserves(), in a single on of it's subroutines, GetItemsInfo(). The only data exported is in the field "count_reserves" which gives the reserve status. This in turn is only used in opac/opac-detail.pl to display "on hold" in the holdings table if the item is currently waiting on the holds shelf to be picked up. There are no other uses of this information. We can remove CheckReserves() from GetItemsInfo(), and add a different call in opac/opac-details.pl to get whether the particular item is on hold or not. This will remove a circular dependency, likely speeding up the overall code (as we won't need to load all of C4::Reserves every time we load C4::Items). -- 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 8307] New: Set a value for items when receiving
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '14

11 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8307 Priority: P5 - low Change sponsored?: --- Bug ID: 8307 Assignee: koha-bugs(a)lists.koha-community.org Summary: Set a value for items when receiving Severity: enhancement Classification: Unclassified OS: All Reporter: jonathan.druart(a)biblibre.com Hardware: All Status: NEW Version: unspecified Component: Acquisitions Product: Koha If the system preference AcqCreateItem is "Create an item when ordering", we would like to set a value for items. For example you could define status for the field items.notforloan (995$o for UNIMARC) with 4 = On order, 5: On treatment. Then, it would be great to fill the item field 995$o with "5". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 50

[Bug 11323] New: AcqItemSetSubfieldsWhenReceived
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '14

11 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11323 Bug ID: 11323 Summary: AcqItemSetSubfieldsWhenReceived Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathieu.saby(a)univ-rennes2.fr QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 11237] New: Clarify explanation for the new pref AcqItemSetSubfieldsWhenReceived
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '14

11 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11237 Bug ID: 11237 Summary: Clarify explanation for the new pref AcqItemSetSubfieldsWhenReceived 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: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The explanation for the pref AcqItemSetSubfieldsWhenReceived (introduced by bug 8307) is wrong. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 11786] New: Improve RDFa schema.org mappings in prog and bootstrap
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '14

11 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11786 Bug ID: 11786 Summary: Improve RDFa schema.org mappings in prog and bootstrap Change sponsored?: --- Product: Koha Version: 3.14 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: dan(a)coffeecode.net QA Contact: testopia(a)bugs.koha-community.org Created attachment 25393 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=25393&action=edit Improves schema.org RDFa mappings (assumes 11310 is merged first) Building on bug 11310, which brings the RDFa structured data implementation of schema.org mappings from prog to bootstrap, the attached patch improves both the prog and bootstrap themes in the following ways: * Provides more granular author attributes (one "author" property per author in records with multiple contributors; wrap in a Person or Organization type instead of using a simple literal value) * Uses "byArtist" instead of "author" for music recordings to respect schema.org preferences * Uses alternateName instead of alternativeHeadline, as the former is a better parallel to the "name" property -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 11671] New: Restructure patron lists add form for improved usability
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '14

11 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11671 Bug ID: 11671 Summary: Restructure patron lists add form for improved usability Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/patron_lists/list.pl?patron_list_id= OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Patrons Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I think it's a potential usability problem that the patron lists "add patron" form has a duplicated submit button. Having one button placed at the top next to the add function implies that this button might be *only* submitting the new patrons, not the deletions which could be triggered by having checked a checkbox. I think the process of adding a patron should trigger the display of an "add" submit button which only submits the additions, not any deletions. The button at the bottom of the list should be clearly labeled and only submit deletions. -- You are receiving this mail because: You are watching all bug changes.

1 15