Re: [Koha-devel] Frameworks in rel_2_2

[Joshua Ferraro]

On Wed, Jul 26, 2006 at 09:57:22PM +0200, Henri-Damien LAURENT wrote:
> Joshua Ferraro a écrit :
> > Hi Paul,
> >
> > Mainly a question for you. It looks to me like it's possible in
> > rel_2_2 to define different mappings to the koha tables for 
> > different frameworks such that the editor ends up saving data
> > to different fields depending on the definition. However, I don't
> > see any search facility that uses frameworks to discover which
> > fields to search. As a result, if you create an record using a 
> > framework that has mappings that disagree with the default
> > framework, I'm assuming that the fields won't be searchable.
> > If I'm correct, then we need to either: not allow frameworks to 
> > disagree on koha mappings or create a way to search using the
> > alternate frameworks (seems very difficult).
> >
> > Let me know what you think ...
> >
> > Cheers,
> >
> >   
> Seems you are right for the first part :
> > As a result, if you create an record using a 
> > framework that has mappings that disagree with the default
> > framework, I'm assuming that the fields won't be searchable.
> For the second,
> >  not allow frameworks to 
> > disagree on koha mappings or create a way to search using the
> > alternate frameworks (seems very difficult).
> >   
> It doesnot sound to me (at first glance) THAT difficult to me as long as
> we use marc_biblio which contains a link with the biblio_framework.
> BUT we would have to store somewhere a hash of frameworks and
> tags/subfields with all the mappings (if exists)
> With mod_perl, this wouldnot be time consuming but without, could be ???
> (I don't know)  ...
I guess one question is, is there ever a use for having different
mappings for different frameworks? What purpose is there having this
option?

> And maybe, since you are designing an API, it could be the moment to
> think over using XML files rather than Mysql to store frameworks.
> But this is another story... :D
For the 3.0 API, I question whether we need as many mappings at all.
It seems like we only need mappings for fields that Koha directly
uses for circulation, reserves, etc. That is, bibid, authid, itemtype,
etc. It may also be useful to have MARC::Record's $record->title() 
and $record->author() (and other such) stored purely for debugging
purposes (not used for display or search in any way, unless as a
failover).

-- 
Joshua Ferraro                       SUPPORT FOR OPEN-SOURCE SOFTWARE
President, Technology       migration, training, maintenance, support
LibLime                                Featuring Koha Open-Source ILS
address@hidden |Full Demos at http://liblime.com/koha |1(888)KohaILS