@garemoko I'm coming back around to question the use case of filtering on Activity Type -- I can see it being desired in a UI, but as I've mentioned before I don't think we should let reporting UI use cases drive the query API.

What came to mind, is a reporting system might only be doing 'high level' reporting, so it only wants to get information about "Courses" and not "Questions" etc. That strikes me as a little odd though, since reporting systems generally provide drill-down capability, for which they would need the questions as well. Again, I don't think we should be designing for "user decides they want some data, report system fetches it from LRS", so the reporting system should have already fetched all the question data for that drill down.... which leaves me with: why do we need this filter at all?