August 2019 - Koha-bugs - lists.koha-community.org

[Bug 17230] New: borrowers table should be better normalized
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17230 Bug ID: 17230 Summary: borrowers table should be better normalized Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I've always been bothered by the fact that we have 3 separate sets of contact information in the borrowers table: streetnumber streettype address address2 city state zipcode country email phone B_streetnumber B_streettype B_address B_address2 B_city B_state B_zipcode B_country B_email B_phone altstreetnumber altstreettype altaddress altaddress2 altcity altstate altzipcode altcountry altemail altphone These should be moved to a contacts table, which contains a 'contact_type' field corresponding to 'primary', 'B_' or 'alt' (although these also desperately need to be renamed), as well as a link to the borrower and a timestamp. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 18218] New: Contact information (borrower, branch, acquisitions), should be centralized into a single table
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18218 Bug ID: 18218 Summary: Contact information (borrower, branch, acquisitions), should be centralized into a single table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The borrowers table contains three sets of contact information -- primary (streetnumber, streettype, address, etc... no prefix), secondary (B_streetnumber, B_streettype, etc) and alternate (altcontactaddress1, altcontactaddress2, etc.)... there are also the emailpro and phonepro fields. These should be moved into a 'contacts' table. I think that it would be reasonable to re-factor the aqcontacts table so that generic contact information was in the contacts table, as well as pulling branch contact information into contacts as well. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 18261] New: Select item type not available when staff overrides hold policy
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18261 Bug ID: 18261 Summary: Select item type not available when staff overrides hold policy Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.hedstrom.mace(a)sub.su.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com With AllowHoldItemTypeSelection set to Allow, it is possible to select an item type to fill the hold. But when staff overrides a circulation policy, the ”Request specific item type” dropdown on the place hold page only lists ”Any item type”, even if there are several items with various item types attached to the bibliographic record. We believe this to be a bug. To reproduce: Set AllowHoldItemTypeSelection to Allow. Set AllowHoldPolicyOverride to Allow. Create/choose a circulation rule for a patron category of your choice, allow holds and set On shelf holds allowed to ”If all unavailable”. Find or create a bibliographic record with two or more items, with two or more item types. Check out one item. Place a hold using the patron category for which you specified the circulation rule above. This should result in a staff override as this behaviour should not be allowed by the circulation policy. Try to request a specific item type, and confirm that choosing an item type is not available, the only option being ”Any item type”. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 18454] New: Holds to pull timestamp
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18454 Bug ID: 18454 Summary: Holds to pull timestamp Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Add timestamp if hold to pull is set. We can use it for sorting by time. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 18446] New: Test to ensure a system preference in .pref file also exists in sysprefs.sql
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18446 Bug ID: 18446 Summary: Test to ensure a system preference in .pref file also exists in sysprefs.sql Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: lari.taskula(a)jns.fi QA Contact: gmcharlt(a)gmail.com Extend t/db_dependent/check_sysprefs.t to read preferences from .pref files in order to check that they are also defined in installer/data/mysql/sysprefs.sql. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 18513] New: Add test to detect errors in sysprefs.sql
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18513 Bug ID: 18513 Summary: Add test to detect errors in sysprefs.sql Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: gmcharlt(a)gmail.com Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org I would be nice to have a test to detect errors in sysprefs.sql (and maybe more like userflags.sql, userpermissions.sql...) -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 18475] New: Table 'Place a hold on a specific item' needs a tidy up
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18475 Bug ID: 18475 Summary: Table 'Place a hold on a specific item' needs a tidy up Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The table 'Place a hold on a specific item' looks outdated and the column 'Information' is not very readable. It needs a tidy up. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 18520] New: special_holidays should be unique by date and branch code
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18520 Bug ID: 18520 Summary: special_holidays should be unique by date and branch code Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Holidays Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I just found a library that had up to 7 entries in the special_holidays table for a given combination of branchcode and year, month, day. This doesn't make sense, it's not fixable in the UI, and it can cause performance issues, because all values will be checked. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 18872] New: Clicking "Place hold" on catalogue/ detail.pl triggers software error if any items have NULL homebranch
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18872 Bug ID: 18872 Summary: Clicking "Place hold" on catalogue/detail.pl triggers software error if any items have NULL homebranch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To re-create: 1) Create several items. Set homebranch to NULL on one of the items. 2) Go to the detail page for the bib record. Click "Place Hold". 3) This will trigger a software error. Here are the results from the logs: Use of uninitialized value in hash element at /usr/share/koha/intranet/cgi-bin/reserve/request.pl line 362. Use of uninitialized value in hash element at /usr/share/koha/intranet/cgi-bin/reserve/request.pl line 363. Use of uninitialized value in string ne at /usr/share/koha/intranet/cgi-bin/reserve/request.pl line 368. Use of uninitialized value in string ne at /usr/share/koha/intranet/cgi-bin/reserve/request.pl line 368. item-level_itypes set but no itemtype set for item (762357) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. No homebranch at /usr/share/koha/lib/C4/Reserves.pm line 2121. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 18879] New: Sending notices via Facebook messenger
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18879 Bug ID: 18879 Summary: Sending notices via Facebook messenger Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I saw some services that use FB Messenger for sending customer notices. What do you thing about it guys? Maybe its "cooler way" for younģer patrons. Its free for library, it can turn into interactive talk with two real people, so it can help to make better relationship between library and patrons. Description of API: https://developers.facebook.com/docs/messenger-platform -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3