Skip to content

Update readme.en.md#52

Open
commerce-experts wants to merge 1 commit intosearchhub:masterfrom
commerce-experts:patch-11
Open

Update readme.en.md#52
commerce-experts wants to merge 1 commit intosearchhub:masterfrom
commerce-experts:patch-11

Conversation

@commerce-experts
Copy link
Copy Markdown
Contributor

changed structure and content to reflect the new features and descriptions of smartSuggest 2.5

changed structure and content to reflect the new features and descriptions of smartSuggest 2.5
Comment thread ui/readme.en.md

## Basic settings - Fuzziness
## 1a. Query Suggestions Settings:
Ranking Rules:
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO: add description for ranking rules

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes hoped you would do that :-)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please keep in mind that remaining captions causes UI code to be adjusted...

Comment thread ui/readme.en.md
Controls the proportion of fuzzy matches in the overall result. The default is set to __precision__ which means that the module will not execute the *Fuzzy-Stages* if the stage(s)
beforehand found any suggestions, regardless if it's less than the requested amount of suggestions. Therefor it could happen that only one suggestion will be returned even if you
ask for 10. If you set the setting to __recall__, the *Fuzzy-Stages* will be executed if the previous stage(s) could not provide the requested amount of suggestions.
Scoped Query Suggestions:
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure about the wording. Currently it's different between QA UI and description. Should be aligned once a final definition has been agreed on.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes I agree - but I vote for Scoped Query Suggestions as it makes it crystal clear that this does not apply for product Suggestions

Comment thread ui/readme.en.md
Scope separator: The separator used to distinguish between queries and scoped queris when scopes are displayed in their expanded form.

## Basic settings - AI Suggestions
### CONTEXTUALIZED PRE Suggestions
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have we already agreed on the order of the UI settings components? on QA i see Pre-Suggest before Scope settings. Should be aligned to the final order

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well I don't think it we necessarily need to have the same order - since most users anyway use the help icon to directly jump to the dedicated section - BUT we should make sure they are correctly placed in terms of SuggestionType

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants