MaartenGr / MaartenGr/KeyBERT

Collecting Use Cases of KeyBERT

Open
#154 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
4.2k
Forks
385
PR merge metrics
No merged PRs in 30d

Description

I am on a mission to collect **real-world use cases** of BERTopic, KeyBERT, and PolyFuzz. For that, I can use your help!

Sharing your use case will drive development and provide an overview for new users. These use cases will help me understand better how these packages are used, what they can do, and what they are missing. My goal is to learn from these use cases and share them on the respective packages in order to help out new users.

It does not matter whether you use any of these packages at Microsoft, a small start-up, a university, or just for fun... any and all use cases are helpful! You can write down the use cases as short or lengthy as you want. You can also share your use case anonymously!

Of course, there is also the option to provide feedback for those packages and any features you want to see in feature updates. Although I cannot promise everything will be implemented, I will take any and all feedback seriously!

You can **share your use case** by click on the **image** below or following the link **[here](https://t.co/Y2xnFo35xo)**. If you do not want to share your use case using the form, you can contact me directly through [LinkedIn](https://www.linkedin.com/in/mgrootendorst/).

[![Form](https://user-images.githubusercontent.com/25746895/214334438-b660161d-4ddd-41bf-b4dd-66951364ff60.png)](https://t.co/Y2xnFo35xo)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository files or tests are named. Start with the linked use-case form, or use the listed contact route; done means submitting a real-world KeyBERT, BERTopic, or PolyFuzz use case and any relevant feedback.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.