Change Details

This task is listing some improvements that seem necessary before the first deployment. It can be split in several tasks if needed. The observations contained in this task are mostly based on testing and observing users testing the demo system. Special:NewLexeme - lemma field: include basic information about what is expected for the lemma. Could be "the shortest form of the word" - language of the lexeme field: include info about the user should do and where the list is taken. Could be "will be taken among the Wikidata items. You can start typing then select a value" - lexical category field: include info about the user should do and where the list is taken. Could be "Example: noun, verb, adjective... This will be taken among the Wikidata items. You can start typing then select a value" - language of the lemma: this field appears upper than the field that the user just filled (language of the lexeme) which is somehow confusing, since the usual order to fill a form is top to down Edition page - When editing the lemma and its language, the language field should propose a selector, and maybe the similar info as stated above - When adding a new Form, the representation field should display info about what the user is supposed to enter here. (for a verb, they may wonder if they should enter the subject) - It's currently possible to add several representations in one form? In the data model, it is stated as only one representation. We should either remove this feature or change the data model. - the language field of a representation should give information about what the user should do, especially providing the syntax for adding an augmented version of the language code. Something like "You can enter an ISO code (ex: "en") or describe the language more precisely by adding a Wikidata item to it, for example "en-x-wikidata-Q43747" to describe the internet slang in English." - grammatical feature field: should provide info about what to enter in there, like "for example: normative, comparative, past tense. They will be selected among Wikidata items. Start typing, click on a value to select it." To be continued...

This task is listing some improvements that seem necessary before the first deployment. It can be split in several tasks if needed. The observations contained in this task are mostly based on testing and observing users testing the demo system. Special:NewLexeme - lemma field: include basic information about what is expected for the lemma. Could be "the shortest form of the word" - language of the lexeme field: include info about the user should do and where the list is taken. Could be "will be taken among the Wikidata items. You can start typing then select a value" - lexical category field: include info about the user should do and where the list is taken. Could be "Example: noun, verb, adjective... This will be taken among the Wikidata items. You can start typing then select a value" - language of the lemma: this field appears upper than the field that the user just filled (language of the lexeme) which is somehow confusing, since the usual order to fill a form is top to down Edition page - When editing the lemma and its language, the language field should propose a selector, and maybe the similar info as stated above - When adding a new Form, the representation field should display info about what the user is supposed to enter here. (for a verb, they may wonder if they should enter the subject) - It's currently possible to add several representations in one form. In the data model, it is stated that there is only one representation. I guess this is about the multilingual values. It should be explained clearly what the user should enter (or not enter) here. - the language field of a representation should give information about what the user should do, especially providing the syntax for adding an augmented version of the language code. Something like "You can enter an ISO code (ex: "en") or describe the language more precisely by adding a Wikidata item to it, for example "en-x-wikidata-Q43747" to describe the internet slang in English." - grammatical feature field: should provide info about what to enter in there, like "for example: normative, comparative, past tense. They will be selected among Wikidata items. Start typing, click on a value to select it." To be continued...

This task is listing some improvements that seem necessary before the first deployment. It can be split in several tasks if needed. The observations contained in this task are mostly based on testing and observing users testing the demo system. Special:NewLexeme - lemma field: include basic information about what is expected for the lemma. Could be "the shortest form of the word" - language of the lexeme field: include info about the user should do and where the list is taken. Could be "will be taken among the Wikidata items. You can start typing then select a value" - lexical category field: include info about the user should do and where the list is taken. Could be "Example: noun, verb, adjective... This will be taken among the Wikidata items. You can start typing then select a value" - language of the lemma: this field appears upper than the field that the user just filled (language of the lexeme) which is somehow confusing, since the usual order to fill a form is top to down Edition page - When editing the lemma and its language, the language field should propose a selector, and maybe the similar info as stated above - When adding a new Form, the representation field should display info about what the user is supposed to enter here. (for a verb, they may wonder if they should enter the subject) - It's currently possible to add several representations in one form?. In the data model, it is stated that there is only one representation. it is stated as only one representationI guess this is about the multilingual values. WeIt should either remove this feature or change the data modelbe explained clearly what the user should enter (or not enter) here. - the language field of a representation should give information about what the user should do, especially providing the syntax for adding an augmented version of the language code. Something like "You can enter an ISO code (ex: "en") or describe the language more precisely by adding a Wikidata item to it, for example "en-x-wikidata-Q43747" to describe the internet slang in English." - grammatical feature field: should provide info about what to enter in there, like "for example: normative, comparative, past tense. They will be selected among Wikidata items. Start typing, click on a value to select it." To be continued...