Could Have Features

[xKhronoz]

Could Have Features

Could Have Feature, features that could improve the product, that are in the plan but have not been put in the works.

Could Have 🥳:

• [x] 1. Allow users to upload their own documents to be indexed and used with the platform for information retrieval.

  • [x] Persistent uploaded documents history.
    • [x] Allow persistence of the uploaded documents and generated index to cloud storage on AWS/Supabase etc with datacenter in Singapore.
    • [x] Allows user to select which documents that they have uploaded to chat with.
    • [x] Have a hard/soft limit of number of uploaded documents and size of uploaded documents.
    • [x] Allow users to request a set of documents to be part of the public chat.

• [ ] 2. A general chat option which combines allows interacting across all available documents.

  • [ ] Implement an agentic approach to aggregate the different document indexes.

• [ ] 3. Integration to email. (e.g. user can get a response via email instead of accessing the web app directly)

• [ ] 4. Authentication to use the app i.e. chat/query/search functions.

  • [ ] Add a basic form of authentication in addition to the social auth before a user can use the chat/query/search UI functions.
    • [ ] Basic Authentications:
      1. Email/Password
  • [ ] Add a verification layer such as an verification key that only JTC users know upon signing in.
    1. Prevents unauthorized/unverified users from using the app even though they are signed in.
    2. In the future this could be migrated to enterprise sign in such as via Microsoft 365 where only JTC employees can sign in.

• [x] 5. CRUD User Management. (By Admin Users)

  • [x] User Management functions.
    • [x] Management of users (Promoting/Demoting to Admin).
    • [x] Management of collections manually (Public/Private).
    • [x] Management of requests sent by users to set a collection to public/private.

• [ ] 6. Saving of chat/query history to client's browser local storage or some local/cloud database.

  • [ ] Persistent chat history.
    • [ ] Allow persistence of the chat/query history to somewhere.
    • [ ] Allow loading of persisted chat/query history from saved location.
    • [ ] Allow deletion of the persisted chat/query history.
    • [ ] Enhance the way chat history/context is being used in the chat function, such as limiting how many past messages gets captured as the chat history when the requests is being sent over to the backend.

• [ ] 7. Use SWR to replace normal fetch for GET data requests

  • [ ] Replace existing GET fetch request to use SWR instead for easy data streaming/revalidation.

[yongkfn]

Added issues 2 & 3

[xKhronoz]

Reordered features and descriptions, added feature 7.