[GH-ISSUE #816] [FEAT]: Renaming source documents #476

Closed
opened 2026-02-22 18:19:40 -05:00 by yindo · 2 comments
Owner

Originally created by @timothycarambat on GitHub (Feb 26, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/816

What would you like to see?

At times, the source document name being shown can be incorrect, ambiguous, or otherwise not great. You should be able to click on such a document and select "rename". This only changes the property in the documents/ folder, but will help greatly in organization.

Originally created by @timothycarambat on GitHub (Feb 26, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/816 ### What would you like to see? At times, the source document name being shown can be incorrect, ambiguous, or otherwise not great. You should be able to click on such a document and select "rename". This only changes the property in the `documents/` folder, but will help greatly in organization.
yindo added the enhancementfeature request labels 2026-02-22 18:19:40 -05:00
yindo closed this issue 2026-02-22 18:19:40 -05:00
Author
Owner

@atljoseph commented on GitHub (Apr 26, 2024):

First off… Awesome product with lots of potential.

It is crucial for the people curating documents to be able to accurately identify and correlate between documents they are curating locally vs documents that have been already uploaded to the system. Random file names === context switch. Context switch === human performance loss. Human performance loss === lower quality source documents. Lower quantity source docs === not as good of a product. Please make it easier for document curators to do their magic. In a system containing hundreds of documents, this really becomes a no-brainer.

Also, if it is not possible yet to replace document embedding in the vector store (other issue), then this feature request becomes even more important.

  • How can someone recognize a doc they uploaded if you change the name?
  • If you let them change the name, at least they’d be able to version it.

Seems the easiest way to allow users to rename between the upload and indexing steps. Like, if they could edit the names inside the grid. And the names should default to something very close to the original document name, even if character transformation is performed on the name.

Lastly, am curious. Does your locally running API have an endpoint to post document(s) with a customized name?

@atljoseph commented on GitHub (Apr 26, 2024): First off… Awesome product with lots of potential. It is crucial for the people curating documents to be able to accurately identify and correlate between documents they are curating locally vs documents that have been already uploaded to the system. Random file names === context switch. Context switch === human performance loss. Human performance loss === lower quality source documents. Lower quantity source docs === not as good of a product. Please make it easier for document curators to do their magic. In a system containing hundreds of documents, this really becomes a no-brainer. Also, if it is not possible yet to replace document embedding in the vector store (other issue), then this feature request becomes even more important. - How can someone recognize a doc they uploaded if you change the name? - If you let them change the name, at least they’d be able to version it. Seems the easiest way to allow users to rename between the upload and indexing steps. Like, if they could edit the names inside the grid. And the names should default to something very close to the original document name, even if character transformation is performed on the name. Lastly, am curious. Does your locally running API have an endpoint to post document(s) with a customized name?
Author
Owner

@atljoseph commented on GitHub (Apr 28, 2024):

Also, I’ve noticed that the docs on the right side (which are indexed) do not seem retain any link to the origin folder. So, it might be difficult to tell one file from another if they have the same or similar name. I know it’s one of those things where whatever decision you make won’t end with everyone being happy, but maybe just the original filter they came from?

One last tweak here, maybe? If entering a GitHub url, maybe the folder name should start with github-, then repo name and branch name.

@atljoseph commented on GitHub (Apr 28, 2024): Also, I’ve noticed that the docs on the right side (which are indexed) do not seem retain any link to the origin folder. So, it might be difficult to tell one file from another if they have the same or similar name. I know it’s one of those things where whatever decision you make won’t end with everyone being happy, but maybe just the original filter they came from? One last tweak here, maybe? If entering a GitHub url, maybe the folder name should start with github-, then repo name and branch name.
yindo changed title from [FEAT]: Renaming source documents to [GH-ISSUE #816] [FEAT]: Renaming source documents 2026-06-05 14:35:30 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#476