[Koha] Koha with a proprietary frontend?

[Joe Atzberger]

Jonas --

You can remix GPL code w/ your own proprietary code as much as you like, as
long as you don't distribute the result (as proprietary code).

The task of swapping in a new front end might be fairly difficult though.
It could be easier to work on configuring and expanding Koha to emulate the
appearance and functionality in your current OPAC.

The first thing to do is install a stock version of Koha and start playing
around with it, so you can see how the OPAC interface is structured.

--Joe Atzberger
LibLime

On Wed, Aug 13, 2008 at 1:34 PM, Jonas Karlsson <
Jonas.Karlsson at kommunicera.umea.se> wrote:

> Hello,
>
> I ask on behalf of a a Swedish library that wants to replace it's current
> ILS with an open-source one as part of an open-source initiative and is
> considering Koha. The (potential) problem is that they have recently had a
> custom web-based frontend (opac) created that they are very happy with and
> do not want to replace with Koha. This frontend is a proprietary solution
> that neither they nor the company that helped
> them write it want to take open source.
>
> In other words, they want to use the Koha backend with their own frontend
> (they do realize that they will most likely have to change their frontend to
> interface properly with Koha.)
>
> Would this be a problem from either a legal standpoint (as Koha is
> GPL-licensed) or a technical standpoint (i.e. is Koha's frontend and backend
> so tightly integrated it would be difficult to do this)?
>
> Has anyone on this list done something like it?
>
> Yours,
> Jonas Karlsson
> _______________________________________________
> Koha mailing list
> Koha at lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.katipo.co.nz/pipermail/koha/attachments/20080813/77cfa51e/attachment.htm