RE: SPAM- [Koha-devel] New KOHA3 API -design issue

[Tümer Garip]

Hi Michael,
Good point.
They do not do the same thing though. There are three different
framework structures currently in KOHA. Until we decide to join them all
together to one MARC-KOHA-ZEBRA framework I did not want to repeat the
same process of koha=>zebra conversion for three. Thats why it exists.
But probably the next step will be to join them into one table.Both has
cons and pros.
That why this thread has been started.

-----Original Message-----
From: Michael Hafen [mailto:address@hidden 
Sent: Friday, July 14, 2006 6:41 PM
To: Tümer Garip
Subject: Re: SPAM- [Koha-devel] New KOHA3 API -design issue


I have one question at this point:

If Koha_attr does what frameworks does, then why is the frameworks table
still used?  Wouldn't it be easier to drop the framework table and use
Koha_attr table as a drop in replacement?

Or have I misunderstood the purpose of the Koha_attr table?

Ok, so that was actually three closely related questions.  ;)

Keep up the good work.