The admin/quiz page quickly becomes unmanageable after more than 50 results. Especially in situations where a quiz is set to unlimited, this makes it hard to actually understand the results. While the views module and possibly even the gradebook might be a way to go down the road, it would be nice to also have a quick and simple solution that does not require a dependency.

Using the pager and using tablesort would be a good start, but some other enhancements would go a long way towards making it easier to view results.

Additional options that would be nice:

  • Show the scores (assuming my other patches are accepted into the module).
  • Option to break the results up by quiz
  • To better support unlimited quizes, the "best" quiz might be a good option.
  • Filter by user.
  • When viewing a quiz result, show other attempts.

In order to get this module in a deliverable state, it might be best to work towards a quick and simple solution that will allow for additional functionality and support down the road.

Comments

nicholasthompson’s picture

nicholasthompson
Primary language English
commented

I entirely agree this needs sorting. Currently, the admin page is a quick display method I wrote just to make sure it was all working as expected.

Paging, Filtering and sorting are all on the to do list...

One thing to bear in mind is that results are stored as seriliased arrays which makes it difficult to filter by result as the entire result set has to be loaded into PHP and then cycled through using PHP - effectively turning PHP into a database.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

I'm wondering if a better approach on this one would be to Views-enable the Quiz module, and include a default View for "results" admin panel.

As to how to actually do that, I don't know off the top of my head. ;) I do owe merlinofchaos some Views docs so as soon as I figure it out, I'll post them up. But Views handles all that sortable column stuff and would also make it customizable for people who wanted to add, for example, a "node status" column to their results or something, or remove the date column, etc.

nicholasthompson’s picture

nicholasthompson
Primary language English
commented

Views would make some of that stuff easier - I agree...

However, (correct me if I'm wrong) isn't views aimed at frontend users rather than admin sections? Can you even make a view limited to an admin section? I'd assume you'd just give it a menu item thats within the administration section and the access rules would cascase onto it?

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Hi nicholas!

Nope, Views may be restricted to any role. While the 'default' Views are intended to be used by "end users" of the site, we frequently use them for things like better, more flexible admin panels for handling node administration, etc.

seanbfuller’s picture

seanbfuller commented

One additional point is that admins are not the only ones who would be viewing quiz results. In an environment where multiple teachers have multiple quizzes, maybe what we want is a “view” that only shows those quizzes that are owned by the teacher?
This would argue that any user with "create quiz" would have access to results.

As far as the views module goes, I agree that it would add a lot of functionality. I guess I don't have a good handle on the current state of views. Do we feel that it is mature enough and accepted enough to make it a requirement for this module? Is there a middle ground where we can create a simple result page and have a contrib module that works with views to enhance the experience?

Thoughts?

nicholasthompson’s picture

nicholasthompson
Primary language English
commented

I didn't know you could restrict access to views!

Sean makes a good point... Do we want to make Views a Prerequisite? Then again - nearly all websites must (surely?) use Views! I find it an essential module.

Personally - I'd vote for an integrated admin section. This is for the following reasons:
1) It avoids having Views as a required module
2) It gives 100% control over the output
3) Saves trying to code it into views which I'm pretty sure would take longer than outputting a filtered/sorted table. Then again - if Sean knows how to code it into Views, go for it (I'm pretty sure WebChick would know how, but i'm equally sure she doesn't have time!).

Maybe the Views options would be better suited for a Quiz V2?

seanbfuller’s picture

seanbfuller commented

Probably still an issue that could be easily resolved. I'd still like a "simple" version that doesn't need views, and a more advanced version that used views.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Yeah go for the simple version for now. I'll file Views integration as a separtate request, but it is pretty crucial, imo.

kylebrowning’s picture

kylebrowning commented
Category: bug » feature

I moved this to a feature request.

falcon’s picture

falcon commented
Status: Active » Closed (fixed)

I haven't read through the entire issue, but we have a brand new result page in Quiz 4. (I'm cleaning up the issue list)