Suggestions for knowledge bases

[Lucena190]

Congratulations on your work, suggestions for knowledge bases:

1 - When accessing the editing screen of a knowledge base, show the user the parameters used to create the vector database, such as: embedding model, content extraction engine (standard or tika), text divider (standard or token - tiktoken), Chunk size and overlap, image extraction (yes or no).
2 - When accessing the editing screen of a knowledge base, give the option to export and import the knowledge base. It would be interesting to implement the previous suggestion first, so that the user knows the creation parameters, can meet these requirements and continue the incremental update of this imported knowledge base.

Another proposal to consider would be to replicate this choice of parameters for assembling the vector database from the administrator panel on the editing/creation screen of the knowledge base, since each knowledge base can have its own configuration for creating a vector database.

[Lucena190]

This would prevent the loss of the entire knowledge base when we change the vectorization settings.

When including knowledge bases in a custom template, it would only allow the use of knowledge bases that are compatible with each other.

In other situations, such as adding a file to a chat or scraping websites, the current configuration of the administrator's control panel (documents) would be used.

In short, it would be interesting to have the freedom to choose different creation settings for each knowledge base.