You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, documents within an AnythingLLM workspace are displayed in a flat list with a folder to group files as they are scraped. While this works for a small number of documents, it becomes difficult to manage, navigate, and quickly find specific files as the number of documents in a workspace grows and there's no indication of how many files are in a folder and no time added, just the date.
Describe the solution you'd like
To address this, I propose implementing enhanced document organization features within workspaces. This would ideally include:
Folder System:
Ability to create virtual folders within a workspace to group related documents.
Ability to rename and delete these folders.
Ability to move documents into and between these folders (e.g., via drag-and-drop or a "move to" option).
Tagging/Categorization System:
Ability to add one or more tags (e.g., "project-alpha," "draft," "research," "urgent") or assign categories to documents.
A way to manage (create, edit, delete) the available tags/categories.
Ability to filter the document view within a workspace by selected tags or categories.
Renaming Documents:
Ability to rename the display name of an uploaded document within the AnythingLLM interface (without changing the original filename if that's too complex, just its alias in the UI).
Describe alternatives you've considered
The current alternative is to keep document counts low in workspaces or use very specific naming conventions, which is not always practical and doesn't scale well for diverse or large document sets.
Benefits of this feature
Improved Organization: Significantly enhances the ability to manage and structure large collections of documents within a single workspace.
Easier Navigation & Discovery: Makes it much faster and more intuitive for users to find specific documents.
Enhanced User Experience: Provides a more familiar and user-friendly interface, similar to standard file management systems.
Scalability: Allows users to more effectively use workspaces with hundreds or thousands of documents.
Potential for Advanced Functionality: In the future, these structures could be leveraged for more advanced RAG strategies, such as:
Scoping chat queries to specific folders (e.g., "Summarize documents in the 'Q1 Reports' folder").
Allowing agents to prioritize or focus on documents with specific tags.
Additional context
Implementing these organizational features would greatly improve the usability of AnythingLLM for users managing substantial amounts of information, making it a more robust solution for various personal and enterprise use cases.
The text was updated successfully, but these errors were encountered:
What would you like to see?
Is your feature request related to a problem? Please describe.
Currently, documents within an AnythingLLM workspace are displayed in a flat list with a folder to group files as they are scraped. While this works for a small number of documents, it becomes difficult to manage, navigate, and quickly find specific files as the number of documents in a workspace grows and there's no indication of how many files are in a folder and no time added, just the date.
Describe the solution you'd like
To address this, I propose implementing enhanced document organization features within workspaces. This would ideally include:
Folder System:
Tagging/Categorization System:
Renaming Documents:
Describe alternatives you've considered
The current alternative is to keep document counts low in workspaces or use very specific naming conventions, which is not always practical and doesn't scale well for diverse or large document sets.
Benefits of this feature
Additional context
Implementing these organizational features would greatly improve the usability of AnythingLLM for users managing substantial amounts of information, making it a more robust solution for various personal and enterprise use cases.
The text was updated successfully, but these errors were encountered: