MaartenGr / MaartenGr/BERTopic
Online topic modeling vs dynamic topic modeling
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.8k
- Forks
- 920
- Avg merge
- 22h 24m
- Merged PRs (30d)
- 5
Description
Hi @MaartenGr,
I try to implement BERTopic on large transcripts. Hope to get some advice from you. Thanks!
I am working on Financial Announcement related data. There are approximately 15 million sentences every year. I want to know what topics are covered in the transcripts over time. First, I plan to use several years (at least 2~3 years) data to build a basic BERTopic model and check the overall topics. Since we want to have more granular and stable topics which we can treat as a base, we use long period of data here. At the same time, I want to update the model every quarter with the quarterly new transcripts coming in. For example, if we train our basic model using data between 2018- Match 2020. We hope our model will automatically add topics such as "covid" (Covid related topics started to pop out in our transcripts) when we fill-in data in 2020Q2 to update the model. We also want to keep those old topics in order to track their trend over time.
I noticed that there are many possible tools I can use such as dynamic topic modeling, online topic modeling, or manual topic modeling(?). If we estimate the model over time, how do we identify a rising theme while not losing existing themes due to model randomness? Do you have any suggestions about which way is more suitable in this case?
Another question is about online topic modeling vs dynamic topic modeling. If I use dynamic topic modeling here, whether it will only give me the change of topic representation (keywords) over time instead of showing some new emerging topics at current time points? If I am using online topic modeling, whether feeding in different size of data for each loop makes sense? How to make sure that topics from basic topic(Tn) will be relatively stable?
Thanks again for your help!
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
Start by reviewing BERTopic's online and dynamic topic modeling approaches in the project documentation. The issue needs a concrete implementation scope, including how quarterly data should be supplied, how existing topics should remain trackable, and what behavior would count as a successful update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100