MaartenGr / MaartenGr/BERTopic
Include guidance for saving Representative Documents
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.8k
- Forks
- 920
- Avg merge
- 22h 24m
- Merged PRs (30d)
- 5
Description
Default saving methods #1 and #2 don't store Representative Documents. This is intentional, but prevents downstream LLM topic analysis on previously run models. Include guidance in the documentation for storing these documents in a separate dataframe for integration in future analyses.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the documentation covering default saving methods #1 and #2 and read how saved model outputs are described. Add guidance for storing Representative Documents in a separate dataframe for later downstream LLM topic analysis; done when the documentation explains the intentional omission and the integration path.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100