Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Model a matching instead of fill-fin for xAPI tracking #9

Open
garemoko opened this issue Jan 2, 2017 · 1 comment
Open

Model a matching instead of fill-fin for xAPI tracking #9

garemoko opened this issue Jan 2, 2017 · 1 comment

Comments

@garemoko
Copy link

garemoko commented Jan 2, 2017

Currently this content type is modelled as a fill-in question for xAPI. This works, but it would be better to model it as a matching question so that all possible options can be listed as interaction components, even if the question is submitted without all options completed.
@thomasmars
Copy link
Member

Yeah, I suppose it does fit the matching definition better.
I have created an issue for fixing this at: https://h5ptechnology.atlassian.net/browse/HFP-433

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@garemoko @thomasmars