Idea: ingestion via email? Since we already have Google oauth

[jasmeetchadha]

Three things come to mind

• Title of email = namespace
• Ingests body of email and attachments: pdf or doc or txt or md
• ability to add new documents to existing namespaces
• stores documents in the associated email or it’s Google drive

What do you think?

[dissorial]

Hmm I'm not sure that I'm a huge fan of the concept. Here's some reasons:

• I'd probably have to also implement a way to delete namespaces via email
• there would probably need to be a system to delete stored documents from google drive or wherever they are saved because it could get cluttered quickly
• it adds another layer of complexity by requiring people to use two different 'platforms', whereas the current setup allows people to do everything in the browser (i.e., on the url of that app). I think the current setup is already reasonably complex, and I'd like to avoid making it even more complex
• I'll soon be adding features like selecting chunk size and overlap before ingesting documents, which can easily be solver by adding a few inputs/sliders, but would require a lot more work if it were to be a part of your solution

Overall, however, I am planning on adding the ability to add new documents to existing namespaces.

[jasmeetchadha]

Thank you