[Koha-bugs] [Bug 12478] Elasticsearch support for Koha

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12478

--- Comment #143 from Jonathan Druart <jonathan.druart at bugs.koha-community.org> ---
Robin,
Maybe I have not drunk enough tea this morning but...
I am trying to improve the mappings area to have a consistent interface to
manage them.
The idea is to 1) move the elastic_mapping.sql to a elastic_mapping.json file
(easier to modify and read), 2) provide methods to serialize/unserialize
mappings and then 3) introduce a backup/import/reset mappings feature and
finally 4) make easier the mapping progression to get a good basis to use ES.

I have managed to create a json file from the sql file, the structure is
something like:

{
  biblio => {
    title => {
      label    => 'Title',
      type     => 'string',
      mappings => [
        {
          suggestible => 1,
          facet       => 1,
          marc21      => '245a',
          unimarc     => '200a',
          normarc     => '245a',
        },
      ]
   },
}

And I have some questions :)
- Do you agree with the idea?
- Don't you think the index_name should be a column of the search_fields table?
- Some of the fields don't have a type, should we assign "string" as the
default value?
- wordings: 'sortable' and 'facetable' sounds more appropriate than 'sort' and
'facet'
- (/me is clearing his throat) I think that all the mappings of a field should
be removed if the field is removed. In other word, there is a 1-n relationship
beetwen search_field and search_marc_map, which means that the join table
(search_marc_to_field) is not needed and we could simplify the structure
removing it.

I am going to wait for an answer before starting anything :)

-- 
You are receiving this mail because:
You are watching all bug changes.