Introduction

With the /lookback command, Hana can retrieve and consider chat history context between two specified timestamps or from a specified time delta from the current moment. This feature allows you to review past conversations and get answers based on historical context, making it easier to catch up on missed discussions or to reference previous messages. To use this command, simply provide the relevant timestamps or time delta, and Hana will fetch the necessary chat history on your behalf.

How to use

Initiate the Command: In your Google Chat, type /lookback to start the process of reviewing past conversations. This command allows Hana to access chat history between specified timestamps or from a certain time delta from now.
Specify Your Query: Clearly describe what information you need from the chat history. You can ask Hana to summarize discussions, extract specific points, or provide insights based on past conversations.

Example:

/lookback Summarize the key points from the team discussions over the last week.

Receive Analysis Results: Hana will process your request and provide you with the relevant information or summary of the chat history based on your query.

Examples

<aside> 🔥 Video will be uploaded soon. Stay connected with us

</aside>

In the above scenario a /lookback command was triggered by Nav Archer asking “Hana lookback 3 days and tell me what concerns were raised in this group. Any unresolved concerns?”

Starting New Chat Session

/lookback command triggered by @Nav Archer

Question: Hana lookback 3 days and tell me what concerns were raised in this group. Any unresolved concerns?

Conversation Look Back QnA

Over the past three days, the following concerns were raised in this group:

1. Video Upload and Hero Video Update: There was a request to upload a "summer day" video to YouTube and update the hero video with it. This task was acknowledged and agreed upon by the team member responsible.

2. Current Workload and Task Updates: There was a query about the current tasks being worked on, and it was mentioned that work is ongoing on the Hana landing page and reorganizing the Discord channel. A commitment was made to show low-fidelity designs the following day.

3. Content Alignment: A request was made to create a document to align content, which was agreed upon by the team member.

Regarding unresolved concerns, it seems that the tasks mentioned were acknowledged and agreed upon, but there is no explicit confirmation of completion for all tasks. It might be helpful to follow up on the status of these tasks to ensure they are resolved.

In the above scenario /lookback command was triggered by santhosh asking “what are we discussed from start of today and group each by respective involved persons”

/lookback command triggered by @Santhosh Kumar

Conversation Look Back QnA

Question by @Santhosh Kumar: what are we discussed from start of today and group each by respective involved persons

@Nav Archer and @Santhosh Kumar, I understand the requirement. Here’s a summary of the discussion from the start of today grouped by the respective involved persons:

### Discussion Summary

#### @Nav Archer
1. MongoDB Change Streams:
   - Asked about listening to events in MongoDB collections like entry creation.
   - Discussed converting TypeScript enums to objects.
   - Inquired about utility libraries for TypeScript enum conversion.
   - Mentioned that backend libraries are fine to use.
   - Confirmed that using a library is good but not necessary.
   - Discussed the importance of checking library documentation.
   - Highlighted the need for Hana to refer to mentioned messages.

#### @Vishal Soni
1. TypeScript Enum Conversion:
   - Mentioned that the provided library (ts-enum-util) does not have the method getNamesAndValues.
   - Suggested using JavaScript inbuilt methods for key/value pair extraction.
   - Confirmed making changes based on the discussion.
   - Agreed that using a library is not needed.
   - Discussed that using JavaScript inbuilt methods is better for their use case.

#### @Santhosh Kumar
1. NestJS and MongoDB Integration:
   - Asked for converting MongoDB Change Streams setup to NestJS framework.
   - Confirmed that the provided setup is working.
   - Requested TypeScript integration for the YourService in NestJS.
   - Asked about the scalability of the event approach and its pros and cons.
   - Inquired about handling high volumes of concurrent updates and ensuring no records are missed.
   - Discussed the impact of errors in one Change Stream event on subsequent events.
   - Questioned the use of setTimeout for reconnection and the possibility of immediate reconnection.
   - Asked about filtering Change Streams to watch for specific operations like inserts directly.

### Action Items
@Santhosh Kumar to add a ticket referring to the mentioned message as an issue with the /lookback command.

Feel free to reach out if you need any further assistance!