Closed jonathanvila closed 3 years ago
Hi @jonathanvila - just a couple of cosmetic issues The API section of the README has 'design de API' and 'postgre' Also it's not clear (to me) from the data model how the translation will work for the question categories and questions. We can talk that through on the next stand-up. I'm probably missing something. Thanks
:+1 I will fix those typos.
Translation : the idea is that translation will be based in a plain text dictionary. So every text stored will have a translation text and the backend will do a full text search for every text ( question, answer, etc... ) to see if there is a translation in the requested language.
Translation table example :
Translation group = 1 Text = "Esta es mi primera pregunta" Language = ES
Now the questionaire/assessment stores the language with it was created,and the texts in that language. The user requests for that assessment but now in Spanish. Backend will search "This is my first question" , "EN" , and will take the value for the row with the Translation group found, "ES" , and will return this to the user, so "Esta es mi primera pregunta". Basic idea is that we have groups of texts in different languages,representing the same meaning. Obviously backend will have a defaulting mechanism to return the text in "EN" if the language requested doesn't exist. And it also allows addition of new languages in any moment.
Already merged in other PRs
Added README with information :