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

[Bug 38508] New: Create new record get stuck in default framework
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38508 Bug ID: 38508 Summary: Create new record get stuck in default framework Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: joseanjos(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl As described here: https://chat.koha-community.org/koha-community/pl/7aqcg7is6b8s9811yosi537toh When creating a new bibliographic record: On CATALOGING, If I don't choose + New Record but choose the framework I want from the drop down list, the framework loads OK and the address is like this: addbiblio.pl?frameworkcode=MON But when I click on + New Record It will open the Default Framework (this is the normal behavior). Then I try to choose other Framework but it doesn't change. When I click on Settings the selected framework is the correct one but the structure is from the default. The address is: addbiblio.pl?frameworkcode= and change to this: addbiblio.pl?frameworkcode=# If I manually replace the # for MON, it changes the the correct Framework. THE NEXT PART WAS FIXED (Upgrading from .04 to .05 version) When I try to duplicate a record Edit as new(duplicate) it will load the default framework and the address is: addbiblio.pl?biblionumber=46163&op=duplicate I change it to: addbiblio.pl?biblionumber=46163&op=duplicate&frameworkcode=MON and it works. Maybe its related with bugs: 38168 and 37947? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 37022] New: Allowing holds on not for loan item types
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37022 Bug ID: 37022 Summary: Allowing holds on not for loan item types Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: mirjam.vantieghem(a)etf.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com - Long context: We have a number of items in our collection that are not for loan, but are available for reference. Some of them are in our closed stacks. (see Use Case in bug #35299 ) In order to consult those, our users should be able to place a hold on them from the OPAC. I am able to fix that for items that have an item type that is normally for loan by setting the "952$7 - Not for loan" status to a negative value, e.g. "-2" (from the authorized values NOT_LOAN). However, instead of setting a not for loan status for each item individually, we work with certain item types that are always not for loan on the item type level (by checking the "Not for loan" box in Administration > Item types). The "952$7 - Not for loan" status for these is "0" and it doesn't help to change it to "-2", as the not for loan status is apparently stored elsewhere because of the item type. So, a hold cannot be placed on these items. We could make the item type for loan and change the status for each item individually, but that creates other issues. E.g. during Covid time items could not be consulted in the library, so all items where exceptionally made available for loan. This was 'easy' to do, as we just needed to add a specific circulation rule for those item types and then uncheck the box for the item type to make it for loan. Afterwards we just needed to tick the box again. It has happened another time because of other exceptional circumstances that we needed to make all items temporarily for loan and it might happen again in the future. - Enhancement request: Is it possible to add an extra option to the 'not for loan' status on item type level for items that are not for loan but holdable? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31304] New: Add ability to customise availability searching
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31304 Bug ID: 31304 Summary: Add ability to customise availability searching Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently in Zebra 'limit to available' means: ## 'available' is defined as (items.onloan is NULL) and (items.itemlost = 0) Bug 25375 proposed for ES a slightly wider net: 783 onloan => undef, 784 notforloan => 0, 785 withdrawn => 0, 786 itemlost => 0, 787 damaged => 0 We should have a configuration for this, a way to allow libraries to decide which statuses are available/unavailable -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 9810] Search limit 'available' does not hide damaged, withdrawn, or not-for-loan items
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9810 Mirjam Vantieghem <mirjam.vantieghem(a)etf.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mirjam.vantieghem(a)etf.edu See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=37680 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 27973] New: Limit to currently available items should have an option to filter out notforloan statuses
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27973 Bug ID: 27973 Summary: Limit to currently available items should have an option to filter out notforloan statuses Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Many libraries find it problematic that the 'Limit to currently available' does not filter out notforloan statuses (example: ordered). It would be handy if there was a system preference that allowed librarians to choose which notforloan statuses could be filtered out. to recreate one potential problem: -do an OPAC search that includes some items with a notforloan of -1 (ordered) -click 'Limit to currently available items' -the ORDERED items remain this can be frustrating for a patron who could reasonably assume that after clicking the 'Limit to currently available' filter they would be looking only at items that are currently available to them to checkout -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 38504] New: .js files in t/cypress must be kept tidied
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38504 Bug ID: 38504 Summary: .js files in t/cypress must be kept tidied Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org xt/js_tidy.t needs to be adjusted to catch files from t/cypress -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 27340] New: We should introduce Koha::PickupLocation(s)
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27340 Bug ID: 27340 Summary: We should introduce Koha::PickupLocation(s) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Looking at the codebase, a pickup location is a combination of a branch/library, and now also a 'desk'. So it would make sense to have a special class for them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 26915] New: Koha explodes when writing off a fee with FinePaymentAutoPopup
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26915 Bug ID: 26915 Summary: Koha explodes when writing off a fee with FinePaymentAutoPopup Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org - To test activate FinePaymentAutoPopup - Create a manual fee - Write it off using the write off button on the account line (not below table) - Experience error on saving the writeoff http://localhost:8081/cgi-bin/koha/members/printfeercpt.pl?action=print&acc… Can't call method "unblessed" on an undefined value at /home/vagrant/kohaclone/members/printfeercpt.pl line 64 This problem was first found in 20.05.03 so affects stable releases as well! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 38500] New: Make warnings on "About Koha" more helpful
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38500 Bug ID: 38500 Summary: Make warnings on "About Koha" more helpful Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org A couple of ideas: 1. In the warning "The patron used for the self checkout module at the OPAC has too many permissions. They should only have self_check => self_checkout_module." it would be helpful to include the name of the syspref that holds the borrowernumber of "the patron used for the self checkout module". 2. In the same warning mentioned abve, it would be helpful if there was a link to the patron it is talking about. 3. Make all mentions of sysprefs links to that syspref. For example in this warning: "System preference 'RequireChoosingExistingAuthority' is disabled, but needs 'AutoCreateAuthorites' enabled. Otherwise catalogers can add headings that will not be linked to authorities." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 11583] Add WYSIWYG editor for HTML notices/letters
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11583 --- Comment #21 from David Cook <dcook(a)prosentient.com.au> --- Technically, this is ready for testing[1]. I'd love it if people could give this a try and give some feedback. Since it's such a self-contained change, which can be easily toggled with a system preference, I'm actually thinking about trying this out locally for one of my libraries. Heck, even if the community doesn't like it, I might run with it locally anyway. [1] The only thing keeping me from marking this as "Needs Signoff" is the *.pref file update and the database update, which can be provided if people approve of this idea. -- You are receiving this mail because: You are watching all bug changes.

1 0