Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Perth Hackfest October 2012/Reporting spec

From MoodleDocs
Revision as of 16:06, 30 October 2012 by Helen Foster (talk | contribs) (copied session notes from google doc)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Introduction/Problems

  • Better reporting within Moodle
  • More reports
  • “General solution for moodle as a whole”
  • Easier for developers to create reports
  • More configuration options to the reports
  • We need side wide reports
  • Existing spec: https://docs.moodle.org/dev/reporting_spec
  • security issues related to those reports

Requirements

  • Site-wide reporting of user data
  • Site-wide reporting of plugin data
  • Ability for users to control report appearance
  • Need to export data in multiple formats: PDF, CSV, Excel(?)
  • Permissions:
    • Access to individual reports
    • Access to specific data within the report
  • Scheduling:
    • Need to specify an exact time to send out a report
    • Hooks to make exports/scheduled reports available via CLI
  • Control over the report’s appearance:
    • via the UI
    • Need ability to generate graphics (i.e. gas gauge, bar graph, line graph, etc.)
      • Needs to generate images for no-JS and export
      • Core Dev decision to use YUI graphic library for generating static HTML graphics
    • Ability to manipulate the appearance of report content
      • Header / footer information
      • Group headings
  • We need an interface that’s nice and clicky (not nasty and typey)
  • Multiple base report “formats”:
    • Table,
    • Graphical (i.e. bar chart)
  • Must be able to display a report within a block that can go on a page
    • i.e. on My Moodle
    • could build new report “widgets” (i.e Jira dashboard)
    • could rewrite Recent Activity, Online Users and Recent Forum Posts as a report
  • Support a “report DB” option that can be defined in config.php where report data can be pulled from
    • Could also be used in other areas of Moodle (stats?)
  • Performance
    • Reports should be able to be run on a live site without significantly slowing down the site for users
    • Log start and end times of report generation (via events?)
  • Accesibility?
    • Data needs to be available to a screenreader
    • Correct ALT tags for images

User stories/Use cases

External References