General Discussion
#10205
Replies: 1 comment
-
Put it simply, after entering a specific model, I can create a separate knowledge base, update and iterate it, which saves me the trouble of searching through all knowledge bases. At the same time, I can also select a public knowledge base within the model (i.e., a knowledge base that can be referenced and is common to all models). In this way, private knowledge bases and public knowledge bases are clearly distinguished, facilitating the creation of models. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Self Checks
Content
Hello, Dify development team, I am a loyal user of Dify. Recently, I encountered an issue or a pain point while using it, which has been quite bothersome for me. When I use Dify to create multiple models, each model utilizes different knowledge bases. As these continue to accumulate, the number of knowledge bases grows, making it very cumbersome to search through the vast amount of content in the knowledge bases every time I set up a new model. This is actually very user-unfriendly. However, it would be a much better experience if I could directly jump to the corresponding private knowledge base within the model. For instance, when I click on Model A, I can edit Model A's private knowledge base, which would be a great experience, while still having access to the public knowledge base. In fact, the problem could be solved by maintaining the original knowledge bases and labeling each one as private or public. Additionally, being able to edit the private knowledge base directly from within the model would be a fantastic experience.
Beta Was this translation helpful? Give feedback.
All reactions