Tuesday Notes
Here are the Tuesday notes, links to be moved.
Notes
General ideas about the program
- separate back-end from front-end
- separate linguistic (declarative) information from the procedural code
The solution
- The language-dependent file be declarative
- The language-independent file be procedural
- We must also change the structure of the database
- Abstract ling features, menu items
Users' comments
B-A
Leksa
Missing in Leksa: levels
You click on Clothes and get traditional Saami clothes, before the basic clothes.
So: Levels of vocabulary.
I like Morfa-C
Now you choose working on bisyllabics, trisyllabics.
Morfa-S is useful for some people, but for verbs it is good that
They need as much linguistic input as possible.
The learning path:
We had the function of letting the teacher see what the student did.
Also, if it not organised as a test, 50% of the students will not do it.
The last time it was work on this, B-A was working with a class, and saw
Today's solution is actually already better.
Leksa:
More info
Sound
Audio files
Erlend
The site oahpa.no
There is no explanation on what Oahpa really is.
On http://oahpa.no there are logs of links, but no explanation
If I know that davvi means "North" I would perhaps press that link,
I find it hard to navigate on the Oahpa pages.
I need a home page with the rehearse links along the other links, like
The tasks were also too hard for me, they demanded that I wrote exactly correct.
The names Vasta, Sahka, Leksa are not in the dictionary. I assumed they were North
All the words on the Oahpa pages should be in NDS. Also all words in Kursa
There are all too many links on the http://oahpa.no pages. We want more pages, less links.
The dictionary
I use the dictionary a lot, it is good. The placename have been a great help.
I miss the autocomplete feature.
When I studied Russian I did not have access to these features.
Why Giellatekno and Oahpa? What is Oahpa, anyway?
There is no link to Kursa, neither from http://oahpa.no/davvi/ nor from the
The structure of Oahpa 2.0.
- backend (data processing)
- exercise generation
- database installation
- user authentication
- exercise generation
- frontend
- different games, how they look like on the screen, etc.
Using FST live or not?
Logging the user actiivity should also be possible when inlogging is done via Google or FB account, or even if the user is not logged in.
Oahpa for mobile devices
Technical: We can use e.g. Bootstrap to build a mobile version.
User interface
Not possible to have so many menus from left to right. E.g. Morfa-S - maybe we can decrease the number of menus. Interface language and dialect will be chosen on the front page. The task will be defined by max two menus.
On mobile devices we should go more for clicking on words instead of typing a lot of characters. Multiple choice instead of free input.
Vasta-S or Morfa-C for mobile devices:
Vasta mobile: users build up sentences with existing words on the screen, but we shouldn't show non-existing wordforms (wrong illative suffix) or non-existing sentences, have to be careful about exposing users to incorrect input
One of the answers is correct, the others contain one or more other forms of the given lemmas.
So:
- as little information on the screen as possible
- clicking on words/menus instead of typing long text
We have a scheme about features and tasks.
Presenting five exercises at once is arbitrary.
Present all words coming in the next task/level, the student can even print it out.
If we take the exercises one by one then after ten answers the user gets the feedback: you have done all 10 correct! Then the next ten words will be on the next level.
Levels in morfa could constrain possible wordforms to draw from, ex. start with Verb 1p, then later add 2nd person
The Kursa / Oahpa sme and sma Grammars -- we want them as .pdf and .epub (!)
Core MorfaS forms:
- Prsent Sg1, Sg2, Sg3, + then: Pl1, Pl2, Pl3
- Then Past, then other modes later on
- Number: Singular before plural
Two paths to "the top"
- By reading "the book" (the Kursa or similar): Start on chapter 7, and get
- By doing the exercises from scratch, and going up one level to the next,
- getting "money", cheering hippopotamuses, a new colour on your karate belt
- getting "money", cheering hippopotamuses, a new colour on your karate belt
- guiding the student
- default: packages with different kinds of grammar/vocabulary, on different levels, going from one level to the next: A1-2-3-4... B1-2-3-4... C1-2-3-4...
- also possible to go to a particular exercise
- links from course material
- default: packages with different kinds of grammar/vocabulary, on different levels, going from one level to the next: A1-2-3-4... B1-2-3-4... C1-2-3-4...
Teacher interface for adding forms that are often misspelled, with comments to the student.
new task types
existing task types
- leksa: translation - word -> word
- morfa-s: inflection - word -> wordform
- mobile: fancy solution to avoid writing
- mobile: fancy solution to avoid writing
- morfa-c: inflection - sentence -> sentence
- numra: translation - numeral -> text, text -> numeral
- vasta: inflection - sentence lemmas -> inflected sentence
- mobile: fancy solution to avoid writing
- mobile: fancy solution to avoid writing
- sahka: dialogue
new task types
- dictation: audio -> word / sentence. + potential for analyzing input for feedback
- dictation: audio -> multiple choice / minimal pairs of new sounds
- images: image -> text/word, text/word -> image.
- could use vasta machinery, but presenting images instead
- could use vasta machinery, but presenting images instead
- translation: defining language of question and answer/user input
- feedback on writing
getting going?
- produce a demo for Russian, with a subset of words, to test with students & instructors
Database structure outline for linguistic features and menus
wednesday
- blank page and colored pens: technical planning project structure based on the above notes
- how much ped data to copy to new pedagogical directory icall