http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12478
--- Comment #150 from Jonathan Druart <[email protected]> --- (In reply to Robin Sheat from comment #148) > (In reply to Jonathan Druart from comment #147) > > I don't understand the problem with the structure, you could have several > > mappings (it's an arrayref of hashrefs). > > Oh, yes, you're right. I missed that bit. > > > With this structure I could insert exactly the same data in the tables > > (except if I missed something...). > > It's just that it's not a natural representation from a database theory > point of view. Why are the various MARC forms lumped together like that? Why > should a schema change be necessary when (god forbid) a new flavour is > added? Actually, that could be important as if we want to add support for > different things into ES, say importing a feed from a journal provider or > whatever, you could use a flavour to mark how the source is mapped into > elasticsearch. Additionally, it promotes redundancy as you are forced to > repeat things to have all the required combinations, which always causes an > icky feeling :) Erk, of course! I did not c/p the correct structure I have in my document! It was: { biblio => { title => { # name label => 'Title', type => 'string', mappings => [ { suggestible => 1, facet => 1, sort => 0, marc_type => 'marc21', marc_field => '245a', }, { suggestible => 1, facet => 1, sort => 0, marc_type => 'unimarc', marc_field => '200a', }, [ and normarc of course :) ] ] }, } -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
