-
Notifications
You must be signed in to change notification settings - Fork 11.9k
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
Add file download function to chat assistant #9547
Comments
Hello @Erincrying, can you specify the scenarios and use case of this features. Because for documents that are public on the Internet, there is no permission problem when downloading, such as papers on arxiv. When it comes to the knowledge base, there will be a permissions issue. |
I hope to use it together in the team. When the team leader uploads the file to the knowledge base, others can add the knowledge base through the chat assistant to query relevant knowledge. At this point, the robot's answer will reference relevant files and prompt which file is being referenced. I hope to download the files uploaded by the leader locally by clicking on the reference file, without having to request the files from the leader |
Wait a moment, I am currently re deploying dify. I can send a screenshot later to illustrate the scenario I want to express |
Currently, when you open the Citation&attribution feature, retrieved chunks will be displayed. Click Link to knowledge to jump to the knowledge base with one click. Do you have permission to this knowledge base? If you do not have permission at this step, you will have the same problem with document download. |
|
This knowledge base is set to be visible to certain team members. Do these team members have this permission? I hope that the authorized team members who click on it will not show me the segmented file fragments, but can choose to download the original file directly. Authorized members can click on the reference file to download the source file |
Yes, that's the permissions issue we're concerned about. Because there are specific documents which are not shown to everyone. For authorized members, you can click into the knowledge base to see the full text. But for users without permission, we are unable to provide complete documentation in this case. |
The current method is that for members who do not have permission, clicking to jump to the knowledge base will prompt a permission error. Consistency can be maintained here, where unauthorized members are still unable to download source files and receive error prompts, while authorized members (i.e. those who can jump to the knowledge base) can provide a method for downloading source files |
In response to this demand, we may add a document download function to the knowledge base in the future. The priority is not very high at the moment. |
Okay, I hope the reference files in the chat assistant can also be downloaded directly because we plan to open the application as an API and return the download stream of the source file directly in the response. It is said that RAGflow has a similar function. If this function is added, please let me know. Thank you very much!! |
@Yawen-1010 I'm sorry to bother you again, but I urgently need to fulfill this request. Can you tell me how to debug front-end code and some files I started using? I haven't developed front-end and back-end code yet, but I urgently need to implement it, so I'm sorry to bother you |
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
I hope to add a download function to the reference files in the answers after adding the context of the knowledge base to the chat assistant.
When others add the knowledge base to the context, the agent will provide me with corresponding answers and referenced files. However, when I tried to download the specific files, I found that this feature was not available. I hope it can be provided
2. Additional context or comments
No response
3. Can you help us with this feature?
The text was updated successfully, but these errors were encountered: