Ray Morris

>  Does anyone have experience of students being pleased they get a chance to do the same question again on a later attempt at a quiz.

Yes, with me being the student.  Think flash cards.

It is good when I need to remember the answer to that question.  Much like flash cards, I suppose.  I kept going through the quiz as practice until I remembered the information.  This is of course useful primarily for things that need to be memorized, rather than for these that only need to be understood.  One recent example is one that needed to be both understood and memorized - the normal forms of relational databases.  I already understood WHY transitive dependencies should be removed; repetition helped me memorize that's THIRD normal form, not second or fourth.

Here is a report I'm working on that breaks the score down by category, based on the categories the questions are in within the question bank.  It seems to basically work, though I'm not quite done working on it.  I'll be tidying it up over the next few weeks.  It should be installed in mod/quiz/report/categorygrades/

Thank you for posting that code, Guido Hornig.  Also thank you Tim for pointing me here when I asked about the same thing in the Quiz forum https://moodle.org/mod/forum/discuss.php?d=310679 .

I think we'll be using Guido's code. A step toward being able to do this reliably in the future may be to start including question.stamp in the Moodle XML format, and any other format in which it is reasonable to do so.  At least based on memory, I think restore uses stamp for this functionality.

I notice that the checks Tim mentioned, regarding if the user has permission to overwrite a question, etc. are already done for restore using this function:

 public static function prechek_precheck_qbanks_by_level($restoreid, $courseid, $userid, $samesite, $contextlevel) {

It may be possible to re-use the existing function. Failing that, the function is slightly portly, so it may be possible to refactor it into three smaller functions and reuse those. Failing even that, the existing function provides at least a template or example of what checks needs to be done and approximately how they can be done.

Using Moodle 2.8, we'd like to use a work flow in which people can edit/revise/correct questions outside of Moodle, then import the new version of the question bank.   We'd like the import to work much as restore works - existing questions shouldn't be duplicated, but updated. 

So in other words, we could export the questions, send them off to Joe Bob for revision, then import the changes into Moodle.  At first glance, I don't see a way to do that within the export/import functions. Is that correct, or is there a way to accomplish this which I haven't seen?

If that functionality does not currently exist, does anyone have any thoughts on the possibility of adding it?  I see that the question ID is already included as a comment in at least the GIFT and Moodle XML export files, so it seems trivial to say "if we know the question ID, call update_record(), else call insert_record".  As I recall, question restore does essentially that (though with question.stamp rather than question.id), so I suppose that validates the concept.

Could you please elaborate on which syntax you're referring to exactly, and what would break?  My original suggestion is to keep the syntax exactly the same as it already is in Moodle. We'd just be moving the display processing from the server to the client. Is Moodle doing something I missed in my CSS re-implementation?  The only "syntax" change should be that <div class=multilang ... can be used just like <span class=multilang ...    Well, there is the secret "secret" bit is that it actually allows more flexibility because you could do things like have the same text for two languages:

<span lang="en af">Jesus</span>
<span lang="es">Jesús</span>