This task has no due-date, and it can take longer, depending on your knowledge and the learning curve it represents. Also, we may re-design this workflow together.
I hope you are familiar with the workflow diagrams. If not, please search the Internet, or let me know.
You can use www.draw.io to create/save/share the diagram.
Make a high-level design that does the following (please include any steps that you consider are necessary):
Searches the sentences from any text (.txt file) that have some kind of a word representing an emotion. You will be given the big set of words that are considered to be "emotional".
Makes a REST call to a backend (Weka in Java) that classifies the kind of emotion that the text has
Asks the user whether they agree with the classification
if yes, move onto next sentence
if no, let the user choose the emotion from a given set of emotions
You can decide which component goes to backend, and which goes to a front-end.
Technology stack is entirely your choice, except the REST call to Weka, which is something I will code in my free time, and that is a separate component on its own.
This task has no due-date, and it can take longer, depending on your knowledge and the learning curve it represents. Also, we may re-design this workflow together.
I hope you are familiar with the workflow diagrams. If not, please search the Internet, or let me know. You can use www.draw.io to create/save/share the diagram. Make a high-level design that does the following (please include any steps that you consider are necessary):
You can decide which component goes to backend, and which goes to a front-end. Technology stack is entirely your choice, except the REST call to Weka, which is something I will code in my free time, and that is a separate component on its own.