Utilize Sentiment Analysis for identifying and/or applying a desired "tone" for content generation
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start by reviewing the existing AI service integrations and the related issues #489, #81, and #117. Compare the available sentiment-analysis services and define a small proof of concept that measures existing content, stores adjustable tone values, and evaluates whether prompts produce visibly different tones before proposing formal integration.
Written by the indexing model from the issue text.
Description
Is your enhancement related to a problem? Please describe.
As related to (perhaps a corollary of) #489 and as mentioned in #81 and #117, we could look to leverage Sentiment Analysis as an alternative to the approach referenced in 489 to identify the "tone" for a site and as input to a prompt for content generation to ensure future content generations align to that "tone".
Designs
Various sentiment analysis tools are available within AI service providers we already integrate with (e.g., Watson's NLU emotion and sentiment text analytics features, Azure's Language sentiment analysis feature), with other AI providers that we've considered (e.g. Amazon's Comprehend sentiment feature), and likely others that would arise with some searching on the topic.
The concepts that we could explore with a rough proof of concept / prototype to see if this could work as an alternative for #489 is as follows:
- utilize Sentiment Analysis on the existing site content to identify the average plotting of said content across various sentiment scales (formal-to-informal, humorous-to-non-humorous, academic-to-non-academic, happy-to-sad, optimistic-to-pessimistic, etc.) and store that as the site "tone"
- present those averages of existing content on those different sentiment options with the ability to adjust where the content ideally exists on respective scales to match the "desired tone" for a site
- utilize the stored sentiment option scales in prompting for content generation to attempt to affect the resulting output from an AI Service provider to match the "tone" for site content
Describe alternatives you've considered
One approach for a proof of concept here would be to have stored values for where sentiment options are on respective scales and send the same prompt for content generation with wildly different scale values to see if the resulting output content varies and appears to match the "desired tone" for the sentiment option scale values. If that appears to work, then building out the proof of concept further for assessment before building more formally into ClassifAI would be helpful.
Code of Conduct
- I agree to follow this project's Code of Conduct
- Dominant language
- PHP
- Stars
- 714
- Forks
- 68
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 23
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from 10up/classifai
-
wpvc
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
wpvc
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Register ClassifAI functionality with the Abilities APIPossibly taken @nhrrob claimed this 10 days ago. Openhelp wanted
Difficulty 4/5 3-5 days Newbie friendliness 48/100
10up/classifai#1249 · 1 assignee ·
Maintainers usually reply within 1 day
-
OpenAI usage tracking: Project ID setting is ignoredPossibly taken @dajiaohuang claimed this 30 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
BYOK Openai modelsOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Exclude module `require-dev` and `autoload-dev` from the generated `composer.json`Possibly taken @keiserjb claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
uiowa/uiowa#10310 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mailcow/mailcow-dockerized#7677 · 1 comment ·
Maintainers usually reply within 1 day
-
a11y
Difficulty 2/5 1-3 hours Newbie friendliness 67/100