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

[Bug 6536] Z3950 Search Enhancements: SRU targets and additional XSLT processing
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '22

22 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6536 --- Comment #114 from David Cook <dcook(a)prosentient.com.au> --- *** Bug 8075 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8067] HTML blocks in sysprefs should be definable for multiple languages
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '22

22 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8067 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook(a)prosentient.com.au Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from David Cook <dcook(a)prosentient.com.au> --- *** This bug has been marked as a duplicate of bug 22318 *** -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 22318] New: Extend Koha news feature to include other content areas
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '22

22 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22318 Bug ID: 22318 Summary: Extend Koha news feature to include other content areas Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- There are many content areas in Koha where we currently use a single system preference to define a block of HTML which is embedded in the OPAC or Staff Client. Using system preferences for this requires that we either use only one language for the content or we use a convoluted system of CSS hiding/showing based on language. We already have a system in place for handling this better: The Koha news feature. We could add additional "display locations" for the various system preferences which could be migrated here: OpacNavRight, opacheader, OpacMainUserBlock, OPACMySummaryNote, OpacNav, OpacNavBottom, etc. This would allow libraries to define both language-specific and library-specific content for these areas of the interface. Being able to define start and end dates for content display would be really useful too. I imagine it would be inefficient to add multiple lines to, for instance, opac-main.pl for each "location," like so: my $OpacNavRight = GetNewsToDisplay( "OpacNavRight_".$news_lang, $homebranch ); Perhaps a template plugin and a block like this? [% PROCESS koha_news news => GetKohaNews( location => news_lang, library => homebranch ) %] I'd love to hear what y'all think. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 72

[Bug 8123] Cronjob to pre-populate/update patrons using LDAP
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '22

22 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8123 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WISHLIST Status|Patch doesn't apply |RESOLVED CC| |dcook(a)prosentient.com.au --- Comment #5 from David Cook <dcook(a)prosentient.com.au> --- It's an interesting idea but it's been over 10 years with no movement, and I don't know that a cronjob would make sense. Perhaps a migration script... -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8366] Meaning of "All" in issuing rules
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '22

22 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8366 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook(a)prosentient.com.au --- Comment #15 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Katrin Fischer from comment #13) > I am sorry, but I don't understand the difference for itemtypes. > We've had no issues with the terms here so far. Currently Koha uses "All". Yeah I don't understand the difference either. While the circulation rules can be confusing, I don't think it's because of the term "All"? I think people just struggle with the concept of rules matching on a 1st rule found basis rather than all rules applying always. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 1091] Do a second search with shorter terms if there are no results found
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '22

22 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1091 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=22605 Resolution|--- |WONTFIX CC| |dcook(a)prosentient.com.au --- Comment #4 from David Cook <dcook(a)prosentient.com.au> --- This is a very old enhancement request, and I can't see it working well in practice. Instead, I think an Edit Search like in Bug 22605 is a much more usable path forward. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9991] De-duplicate "no cover image available" (currently in lieu of prioritizing cover image sources)
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '22

22 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9991 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Cook <dcook(a)prosentient.com.au> --- *** This bug has been marked as a duplicate of bug 26933 *** -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 7854] preferences.pl: cannot have choice options of yes and no
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '22

22 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7854 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |RESOLVED CC| |dcook(a)prosentient.com.au Resolution|--- |INVALID --- Comment #4 from David Cook <dcook(a)prosentient.com.au> --- It's been over 10 years, we're not using YAML::Syck anymore, I'm not sure I understand this one anyway. I think the HTML forms are based off the .pref files rather than the database, although I could be wrong. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 7916] Events module
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '22

22 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7916 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |dcook(a)prosentient.com.au Resolution|--- |WONTFIX --- Comment #1 from David Cook <dcook(a)prosentient.com.au> --- Description is vague and hasn't been updated for over 10 years -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8013] During installation setup KOHA_CONF and PERL5LIB path in sip_run.sh
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '22

22 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8013 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook(a)prosentient.com.au Status|ASSIGNED |RESOLVED Resolution|--- |INVALID --- Comment #2 from David Cook <dcook(a)prosentient.com.au> --- I don't think hard-coding those values into a shell script would make sense. Typically, one should use the Debian packages. If not using the Debian packages, then creating a service file where hard-coded values could be added might make sense (unless it's systemd which has nice template options) -- You are receiving this mail because: You are watching all bug changes.

1 0