Skip to content

Conversation

@dabrt
Copy link
Contributor

@dabrt dabrt commented Nov 28, 2025

Question Answer
JIRA Ticket IBX-11003
Versions 4.6, 5.0
Edition all

Describe taxonomy suggestions LTS update in developer doc

Checklist

  • Text renders correctly
  • Text has been checked with vale
  • Description metadata is up to date
  • Redirects cover removed/moved pages
  • Code samples are working
  • PHP code samples have been fixed with PHP CS fixer
  • Added link to this PR in relevant JIRA ticket or code PR

@github-actions
Copy link

Preview of modified files

Preview of modified Markdown:

@dabrt dabrt changed the base branch from 5.0 to 4.6 December 1, 2025 15:18
@dabrt dabrt changed the base branch from 4.6 to 5.0 December 1, 2025 15:21
Comment on lines 125 to 126
- when the database is reindexed, for example, after you enable the feature
- when an individual taxonomy entry is created or modified, it's embedding is updated
Copy link
Contributor

Choose a reason for hiding this comment

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

The feature needs to be enabled for both

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The first sentence says exactly that.
Here, we are stressing that right after you enable the feature, you trigger the reindex and that's when the embeddings are calculated for the first time.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok, for me it was like two cases. In the first case, we need to enable the feature. In the second, we have no information on whether it should be enabled or not. When an individual taxonomy entry is created or modified, then embedding will be calculated only when the feature is enabled.

dabrt and others added 2 commits December 3, 2025 14:41
Co-authored-by: Mikolaj Adamczyk <mikadamczyk@gmail.com>
This way you can limit field selection to meaningful text fields and avoid unsupported field types.
Like in the case of the number of suggestions, you can override this setting per AI action by editing its configuration.

### Change the embedding generation model

Choose a reason for hiding this comment

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

It needs to be mentioned that suggestions are less precise the more data is in the input. But maybe it is already mentioned in manuals of models that we are suggesting 🤔

Copy link
Contributor

Choose a reason for hiding this comment

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

Added tip in cd0a9ec

@mnocon mnocon added Wait with merge PRs that shouldn't be merged instantly Ready for MERGE and removed Needs DEV review labels Dec 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Ready for MERGE Wait with merge PRs that shouldn't be merged instantly

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants