🚀 Feature: Sources with complete filesystem

[dartpain]

🔖 Feature description

Currently sources store data in vectorstores separated by chunk.
I propose that we save files using application/storage/base.py and keep the location stored in source object.

• On upload store file location in source object mongodb
• Every chunk should have filename metadata to know where its from
• Should be able to add and delete files and folders from sources
• Rename Documents to Knowledge Bases in the UI

🎤 Why is this feature needed ?

To allow users more freedom in managing their sources

✌️ How do you aim to achieve this?

Store file locations in source, with uploaded source folder structure.
Store extra details in metadata
Add endpoints to add and delete files from source
Design UI

🔄️ Additional Information

👀 Have you spent some time to check if this feature request has been raised before?

• I checked and didn't find similar issue

Are you willing to submit PR?

None

[ManishMadan2882]

Thinking about improving how we display knowledge base sources (files, URLs, and directories). Tables are functional but can be dense. Proposing we explore a card-based UI.

Each card would represent a source:

• Files (DOCX, PDF, PPTX): Show title, file-type icon, and actions
• URLs: Display title, domain, sync actions, sync metadata.
• Directories: Use a folder icon, show directory name, maybe item count (e.g., "5 items"), last modified date, and an 'Open' action that would navigate into the directory (showing its contents, possibly as more cards or a list).

This approach could boost scannability, visual appeal, and make it easier to handle these diverse source types consistently. It should also provide a clear way to navigate through directory structures.