Just a quick note to let you know reporting in 2.2 for SCORM has improved a lot - we now have an interactions report and a couple of others in development thanks to some work from a GSOC project this year. You can now write your own pluggable "reports" just for SCORM.

Theres a small screenshot that shows the interactions report here:
http://docs.moodle.org/22/en/Using_SCORM#SCORM_interactions_report

(but the docs probably need a bit more improvement/updating at some point)

This is something we were planning on implementing but haven't got to yet. What I was intending to do was to modify the content tab to dynamically include one content restriction for each filter in the report's source.

The filtering code already provides methods for adding the form element to a moodle form, the sql query and a human readable representation of the filter so it should be pretty straightforward.

To avoid the page becoming huge, I was going to change the UI slightly so instead of including all content restrictions the page would start with none then options would be added by the user (and would be enabled as soon as they were added). This could be done via a pulldown to allow the user to select their preferred restriction.

Simon

Hi Rafi,

That's fantastic, thank you so much for the contribution. We'll definitely include the new content restriction, and will look at which report sources could include a text filter by default.

I did find a few small issues while testing it out:

1. When the "Show records based on SCORM Title" checkbox is disabled the rest of that part of the form should be greyed out (to indicate it isn't used). That can be done using disabledIf in the moodle form definition.

2. In sql_restriction you use the $ilike variable but don't define it. That breaks the filtering options (other than contains and doesn't contain). Fix is to add:

$ilike = sql_ilike(); before the switch statement.

3. Quotes in the text field are escaped but not unescaped when the text is redisplayed, so get prepended with a backslash every time the content form is reloaded.

4. The string passed to the content option is designed to work in the context of the phase "Filter base on ...", so instead of passing in "SCORM title" it would be better to pass in "the SCORM title". This would also fix the fact that the first character is being lowercased (so it displays as "sCORM title").

5. Some whitespace and formatting issues with the code itself (whitespace at the end of lines, tabs instead of spaces, alignment).

Simon