fix thread replies parent-child relationship

[jrakibi]

No description provided.

[adamjonas]

Status of this?

[jrakibi]

Status of this?

This PR was just for testing and can be closed. It currently supports nested replies, but only one level of nesting, as I showed in the previous demo.

I’ve updated the way we handle nested replies locally to support multiple levels of nesting on both the scraper and summarizer.

I’ll open two new PRs after completing some local testing with sample data. Once I’m confident they won’t break anything (since I’m not sure we have a backup), we can validate them against our data in Elasticsearch

[jrakibi]

Closing this PR in favor of #74

The threading functionality is now implemented through these three PRs:

• Summarizer: bitcoinsearch/summarizer#74 – Threaded XML generation
• Scraper: bitcoinsearch/scraper#100 – Thread parsing and data extraction
• UI/Frontend: bitcoinsearch/tldr#526 – Threaded conversation UI

All these three PRs must be merged together.

- We'll perform the data migration on Elasticsearch to update existing documents with the new threading structure
- Merging is not required to test, we can populate/update Elasticsearch by running the scraper job on the branch