-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Biii Full-text search does not look into EDAM tags #137
Comments
http://test.biii.eu/search?search_api_fulltext=%22rigid+registration%22 |
Ok: now testing after having edited the PROCESSORS of the serach INDEX -> Added entity linked and Added hierachical index -> that should solve both searching in terms AND inheritance of parent terms |
new procedure Under testing -In the 'Fields' tab for your active index (ex: Administration->Configuration->Search and metadata->Search API) |
Sounds like solved, but only when logged (config export to be done) |
Fixed: was actually only a cache matter I Believe , today the same Search return the same results for both Anonymous and not Anonymous users |
it should be solved again, @delestro @joakimlindblad could you check? |
"multimodal AND interactive" is a subset of multimodal where entries also mention interactive |
Search in EDAM keywords seems to work again :-) The last comment I do not fully understand though. The free text search seems to OR all words together, if I search for "multimodal AND interactive" the top hit is a text with many occurrences of the word "and". The mentioned search in synonyms ("Added synonyms as well") seems to not work though. An example is search for "visualisation" gives Catmaid - which has "visualisation" and "image visualisation" set, whereas search for the narrow synonym "plotting" does not, nor does "rendering" (exact synonym of image visualisation). |
Good point I did not re add synonym
For and my mistake I am looking for the correct syntax for it
… Le 4 mars 2020 à 00:56, Joakim Lindblad ***@***.***> a écrit :
Search in EDAM keywords seems to work again :-)
Both when logged in and when not.
The last comment I do not fully understand though. The free text search seems to OR all words together, if I search for "multimodal AND interactive" the top hit is a text with many occurrences of the word "and".
The mentioned search in synonyms ("Added synonyms as well") seems to not work though. An example is search for "visualisation" gives Catmaid - which has "visualisation" and "image visualisation" set, whereas search for the narrow synonym "plotting" does not, nor does "rendering" (exact synonym of image visualisation).
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
use function, should use synomyns (to be double checked, may be add field synomym :entity ratehr than synonym ) ;same for topics. Relate to NEUBIAS#137
Please note that Tracking rebuild AND reindexing (and drush cr) is needed for correct new indexing in search api |
important was missing rendered item. Need to REBUILD TRACL INDEX, and run reindexation, and drush cr before seing effects NEUBIAS#152 NEUBIAS#141 NEUBIAS#137
@joakimlindblad could you check if your points are now satisfied? I reindexed and cache-recreated biii.eu. |
First part of the issue is solved. Second part (related to Synonym search) is closed as duplicated of #202 |
Problem: Free text search does not report hits on used EDAM tags.
Issue: Free text search should reports hits on used EDAM tags, they are relevant!
Example: In free text search, if searching for an EDAM topic (e.g. "Multimodal Imaging") we get fewer hits (almost no) than if we, in advanced search, show what is listed under the Topic "Multimodal Imaging".
Search: https://test.biii.eu/search?search_api_fulltext=multimodal finds 2 hits!
Search: http://test.biii.eu/all-content?type=All&field_has_topic_target_id_1%5B%5D=4774&field_type_target_id=All finds 10 hits.
Example 2: See the "smoothing" first subtopic of Issue #108
Note: This Issue is a specification of the first subtopic of issue #108 (thus a narrowing of the composite #108 issue), with an intention to elevate its priority.
The text was updated successfully, but these errors were encountered: