| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This reporter updates two pairs of user-defined fields on an Individual
Profile. The first pair are pulldown & date fields used to track the
assessment results. The second pair are updated after each chapter is
completed.
|
|
Previously scores aligned on the answer values: 0 (seeker), 2, 3, and 4
(teacher).
Now scores align halfway between: 0 (seeker), 1.5, 2.5, 3.5 (teacher)
|
|
|
|
Also moved the Playlist related tests to their own class.
|
|
* Fixing thread ordering.
* Adding a limit of 5 threads per topic.
* Changing frontend /account references to UserRecord.
|
|
|
|
|
|
Other Changes:
* JsonEncodedProvider no longer implements Provider.
* Only the first answer is shown. Others slide down.
* Switch going deeper and the feed.
|
|
Changed MessageThread so that a thread always contains one original
message.
Added support in JsonEncodedProvider for JavaTypes in addition to
classes.
Updated communityfeed.ftl to actually display questions and answers.
|
|
Previously sliders were scored as a value between 1 and 4 based on the
percentage across the screen that the slider was slid. This required you
to slide fully to the right to get a 4.
Now the slider is divided into n sections, where n is the number of answers
on the slider. With 4 answers the score will be exactly 1, 2, 3, or 4.
With more answers you may get a decimals, but the last section of the
slider will always result in a 4.
|
|
|
|
After refactoring users were required to watch all videos regardless of
their assessment score.
Also enabling strict video ordering and adding the option magicskip to
watch out of order.
|
|
|
|
|
|
Playlists are now generated from a default playlist and regularly
merged with the default playlist to get updates.
Also adding the Question tests that got left out of a previous commit.
|
|
Question and Answer can now be serialized and deserialized to/from JSON.
As such, I no longer have to pass awkward maps around. As part of this
change I have introduced a Provider interface to abstract out loading
and persisting these beans.
The scoring logic has been completed factored out of
SurveyResultsResource and into the various ScoringEngines. Tests have
been added for Question, Answer, and the ScoringEngines. A bug has been
fixed in computing the value for slider questions.
The label identifiers in the circle questions have changed from all
lower case to camel case. That is, topleft is now topLeft. Several
issues have been corrected in the circle answers where the point values
did not match the labels.
Testing and code coverage support and reports have been added.
|
|
For this fix I am moving Question and Answer from the backend into a new
model package. Question is now used in SurveyPageResource instead of the
Map. Eventually I should encode/decode the model from the json directly.
I am adding support to the Question model to find the next question
based on the answer to the current question. If the answer has a
specific nextQuestion field, that is used. Otherwise the question's
nextQuestion field is used. This is to facilitate skipping irrelevant
questions.
|
