Open gjost opened 1 year ago
ddr-cmdln
- Added search_hidden
field to Elasticsearch records in branch 199-search-hidden
commit e06f3e3
.ddr-local
- Added search_hidden
to searchable fields in branch 199-search-hidden
commit 6f50622
.ddr-local
- models: Add creators search and NamesDB links on detail pages in branch 199-search-hidden
commit 9da62de
.creators
and persons
are now searched using fulltext
searching via the search_hidden
field.
Fixed in ddr-public
commit a03701e
, merged in to develop
branch, pulled to ddrstage.densho.org
Some ideas:
creators.role
, creators.namepart
, and persons.namepart
to aggregations along with topics
, genre
, etc.?.role
or a .namepart
is the only search term, do a filter search like we do for topics
. If there's a fulltext
field, do a fulltext search with name as a filter.
Mods to
ddrpublic
on the199-creators-persons
branch:creators.namepart
toSEARCH_PARAM_WHITELIST
andSEARCH_INCLUDE_FIELDS
ui.forms_search.SearchForm
.creators: ...
orpersons: ...
in place offulltext
.densho-elastictools
expects searches to always be based on afulltext
field. This branch enables searches based oncreators.namepart
andpersons
fields instead offulltext
. Unfortunately these fields are tokenized (elasticsearch_dsl.Keyword
instead ofelasticsearch_dsl.Text
) and can't be mixed with afulltext
search without some more refactoring.The team thought this change was going in a wrong direction, that users would expect to be able to type names and get results from
title
,description
, and other fields along with results fromcreators.namepart
, all using fulltext search. To make that work, we will need to create a separateelasticsearch_dsl.Text
field that contains the text fromcreators.namepart
and make that searchable.199-creators-persons
branch will be kept in place but further work will be on199-search-hidden
.