The back-end project now has a database. Every word that is consulted through the V2 endpoint of the transcribe action, its transcription is taken from the database using the CMU Pronouncing Dictionary. What is consulted is saved in the database as well for future use (like consulting which word is most sought so we can create some projects from it, like a robot that informs people through our social medias). By default, the dictionary only has entries for EN-US. As EN-GB is needed too, a routine was created to fill the database using the Transcriber Wrapper. It can be consulted in the create_dictionary.py file. A new endpoint was created to allow the front-end side to send suggestions from the user. The Django Admin (see admin.py) has some features that allow the administrator to apply a suggestion, and to see what was the most sought words given the current admin filter.
The front-end project was adapted to use the new endpoints as well as some updates in the UI. Most of the logic related to transcription, such as show stress, was implemented on the front-end project, so the user does not need to consult the back-end server again to see how is the transcription with or without stress marks.