Visvanath Ratnaweera

RESOLVED

To my original question, how to "turn around" a glossary, this answer by Daniel provides a straight solution:

An admin should be able to extract a CSV list from a glossary with Custom SQL queries report and import that to spreadsheet. See contributed example.

P.S. The solution is not entirely satisfactory for me since I can't delegate it to our supporting staff - yes, unless I polish the custom SQL and provide an interface to the non-admin, etc. If the glossary had a CSV export function, the life would have been much easier. Unfortunately the glossary provides only XML export.

I have a case of a 5th grade language class where the teacher wants the kids to practice word lists, say a list of 200 antonyms. The kids must be able to practice any number of times, Moodle should bring different (random) questions every time. The special thing is, although "only" practice, the teacher wants to monitor how much a kid practices and how focused (success rates).

One obvious approach would be to put the antonyms in to a glossary and let the glossary to quiz block generate quiz questions which will feed a random quiz. The downside of the approach is, it'll be too "dry" for 5th grade kids. The teacher is investigating the H5P line.

I know, there are all sorts of "card" based content types in H5P. But I believe the condition that the teacher wants to monitor the kids make them unsuitable. What approaches do you suggest?

Pl. note that due to the large number of possible combinations the making of questions needs to be flexible/semi-automated (like the glossary to quiz block). Consider that the list of words will change/develop over the years.

RESOLVED

Unknown to me there were a couple of tables with collations different from utf8mb4_unicode_ci that triggered this error.  The script admin/cli/mysql_collation.php --collation=utf8mb4_unicode_ci solved the problem.

Source: https://docs.moodle.org/405/en/Administration_via_command_line#Converting_character_set_and_collation

Thanks Howard and Ken. Your guess was correct: The other party downloaded the full moodledata first to their Moodle desktops using FileZilla in ASCII mode and then made the zip. So requested a new zip in binary mode (for some reason they didn't get that the panel offers to zip on the server-side).

The thing was it didn't help. On revisit days later and after purging caches the issue was fixed. I'm certain that I purged the caches the first time, but too late to confirm. Either way, the matter is happily RESOLVED.