September 2016 - Koha-bugs - lists.koha-community.org

[Bug 17093] New: JavaScript error on patron entry page if toolbar is not displayed
by bugzilla-daemon＠bugs.koha-community.org 14 Jan '20

14 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17093 Bug ID: 17093 Summary: JavaScript error on patron entry page if toolbar is not displayed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.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 Under some circumstances the patron entry form and toolbar are not displayed by memberentrygen.tt. For instance, if there are no libraries or patron categories defined. If this happens a JavaScript error is triggered because a check for #toolbar's position returns null. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 16766] New: Merging two records with title level holds for the same patron creates two holds on one record
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16766 Bug ID: 16766 Summary: Merging two records with title level holds for the same patron creates two holds on one record 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: 1 - Place a title level hold for a patron on a record 2 - Do it again on another record 3 - Merge these recrods 4 - See they now have two holds on one record -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 16413] New: Prototype for GetLatestAutoRenewDate and GetSoonestRenewDate should be changed
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16413 Bug ID: 16413 Summary: Prototype for GetLatestAutoRenewDate and GetSoonestRenewDate should be changed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 16344 Currently the 2 GetLatestAutoRenewDate and GetSoonestRenewDate subroutines takes $borrowernumber and $itemnumber in parameter. They refetch the patron, item and issue information but they already are available from where they are called. It would make sense to change the prototype of these 2 subroutines to accept the patron, item and issue information directly to avoid unnecessary refetches. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16344 [Bug 16344] Add a circ rule to limit the auto renewals given a specific date -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 16140] New: Only clear L1 cache when needed
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16140 Bug ID: 16140 Summary: Only clear L1 cache when needed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P2 Component: Architecture, internals, and plumbing Assignee: jweaver(a)bywatersolutions.com Reporter: jweaver(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 16044 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16044 [Bug 16044] Define a L1 cache for all objects set in cache -- You are receiving this mail because: You are watching all bug changes.

1 43

[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 17360] New: Test the installer process
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17360 Bug ID: 17360 Summary: Test the installer process Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org On bug 16554, we needed a script to test that all the .sql files were correctly inserted. It could be reuse later (and pushed?). -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 17306] New: Update scripts fail with Mysql 5.7
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17306 Bug ID: 17306 Summary: Update scripts fail with Mysql 5.7 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: gmcharlt(a)gmail.com Reporter: rsantellan(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Doing a complete migration from koha 2 to koha 3 with the update22to30.pl and updatedatabase.pl found a few problems with the consistencies of the SQL with the new MySQL 5.7. I have changed the script to be able to run, the only one that is not working properly is 3.09.00.051 that have a bad group by condition but I never have use that module and don't know how to fix it. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 17259] New: Allow batch removal of restrictions
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17259 Bug ID: 17259 Summary: Allow batch removal of restrictions 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be nice to have a ways for librarians to remove blocks of debarments (end of the school year, etc) using the batch patron modification tools -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 17198] New: KOha database resotre
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17198 Bug ID: 17198 Summary: KOha database resotre Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: gmcharlt(a)gmail.com Reporter: matsyufsms(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org HEllo I get error whever i try to restore koha.sql on new installaion Error = ERROR 1062 (23000) at line 113372: Duplicate entry 'INNODB' for key 'name' HOw cna i get about it Yusuf -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 17150] New: Cancelling holds over process needs improvement
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17150 Bug ID: 17150 Summary: Cancelling holds over process needs improvement 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 54584 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=54584&action=ed… Cancel Hold buttons I'm not seeing a bug with all of this spelled out exactly, so if I repeat something already posted, I'm sorry. It may be that some of this needs to be broken into different bugs, or is already addressed in another bug. I am linking together what I know to be part of the problem, but not the whole picture. Cancelling a hold that is over is a tedious process at best. I'll try to explain what we are seeing. So, when we go to the Holds over tab in the Holds awaiting pickup, we find the item. Issue #1 (holds01.png): Even though the buttons are different, they don't act different, they are not even necessarily accurate about the item, and they have lost functionality between 3.18 to 3.22. Issue #2: Even though a transfer might be triggered, you have to check the item in to get the slip. Waste of time. It should come up with this choice when the transfer is triggered while cancelling (holds04.png). Issue #3: Even though the item might have another hold request, it isn't revealed when you cancel the hold. So, you have to check EVERYTHING in that you cancelled to see if there is a hold, or a pending transfer. Again, this should happen when cancelling the hold. Issue #4: As mentioned in issue #1, the buttons are not very accurate about what happens next with the item. Sometimes there is a hold request at the current location (holds05.png). So, you have to check ALL of these items in to find out if they have holds. Again, this should happen when cancelling the hold. Issue #5: Even though there is a hold request for an item you are cancelling, cancelling the hold applies a transfer. So, when you check the item in after cancelling, you see a transfer to the item's home location AND the hold request (holds06.png). This is CONFUSING and crazy. Especially if it is to the same location. We end up having to cancel the hold, check the item in, cancel the transfer, check the item in again, and then trigger the hold. Why not just skip cancelling the transfer and trigger the hold? Because the transfer will still be in the system! Crazy! Issue #6: When you cancel a hold, you get bounced back to the Holds waiting tab, so you have to click back over to the Holds over tab for the next item. I think there is another bug on this one, but I can't find it at the moment. So, why don't we just use the Cancel All button (by the way, shouldn't it read "Cancel all")? Because not all the items are still in our hands. Some items end up walking out without being checked out. Issue #7: It would be great if there were a button to mark the item missing, or maybe someone calls and finds out the person has the item, so a button to check the item out to that patron would be great. Issue #8: I've noticed another little quirk. If you compare holds04.png with holds06.png, you'll see that the transfer popups are different. holds04.png has no buttons. Just links. I know that one transfer is related to the hold, which doesn't make sense because when we cancel it, it doesn't affect the hold. Issue #9: You may also notice on holds06.png, the address fits on the full line in the transfer popup, but not in the holds popup. The popup boxes are the same size, and the bullets offset in the same place, so something is off on the formatting. Issue #10: Cancelling a hold takes 2 to 3 times longer in 3.22 than it did in 3.18. This is surprising since the popups were taken away! So, ideally, if these are legitimate issues, and are addressed, this is what we would expect to see: 1: Just show a Cancel button for all items with the words "Cancel hold". What happens when you click the button should be self explanatory. Perhaps if Koha didn't have to determine the next status of the item just to create a button, the refresh of the page would improve. Hmmmmm.... 2: When you cancel a hold, if the item needs to go home, it will show the transfer popup to let you print the slip. 3: When you cancel a hold, if the item has a hold, it doesn't trigger a transfer, and only shows the hold popup, whether it is a local hold or going somewhere else. 4: Whether it has a popup or not, when done with the popup it should put you back on the same tab you were last on. 5: Buttons should be on the transfer popup. 6: Formatting should be consistent between the hold and transfer popups (I know, this is sooooo trivial). 7: We should have more options for holds that are over, than just Cancel, since there are other things that can be happening, like missing or already with the patron. A "Mark missing" button and a "Checkout to this patron" button would be nice. Sorry if this sounds like a rant. I know that how we do things isn't the way everyone does things, but this has bugged me for a LONG time, and I think these are some great improvements, even if they need to be tweaked a bit to accommodate other workflows. I will add the screens and see alsos in a moment. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20