> It's an interesting notion, albeit one that I think should be targeted
> for 3.4. The mechanism will be a bit risky, though; since the krz
> files can contain arbitrary Perl, they can do *anything* to a Koha
> database. In a sense, what you're proposing amounts to a
> general-purpose plugin syst
Hi,
On Tue, Jan 26, 2010 at 8:42 AM, Kyle Hall wrote:
> I've written a new "Custom Reports" addition for Koha to allow Koha
> users to trade more complicated reports that cannot be represented in
> pure SQL. Here's how it works:
It's an interesting notion, albeit one that I think should be targ
Also, the report_dir should be named in a fashion to guarantee uniquness.
I have used a java style naming system, so each report is named
org.ccfls.REPORT_NAME. If Biblibre created custom reports, they
would be named com.biblibre.REPORT_NAME and so on.
I should note this patch does not represent t
Hello All,
I've written a new "Custom Reports" addition for Koha to allow Koha
users to trade more complicated reports that cannot be represented in
pure SQL. Here's how it works:
Each report is downloaded as a .krz file. This filetype is just a zip
file with a specific structure ( sort of like
