Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-75535

Create "Files" custom report source

    XMLWordPrintable

Details

    • MOODLE_401_STABLE
    • MOODLE_401_STABLE
    • Hide

      Note: testing is easier on a brand new site, although can be tested equally on an older site, but there will likely be a lot more data being reported on

      Create some files

      1. Log in as admin
      2. Navigate to Profile
      3. Edit profile
      4. Add a User picture and save
      5. Create a new course
      6. Add a Course image and save

      Create report

      1. Navigate to Reports in user menu
      2. Create new report from Files report source
        • Ensure Include default setup is checked
      3. Confirm presence of the following columns, with accurate data (note: as per start of testing instructions, there may be many more rows than just the files you created if using an existing site with historical data):
        • Context
        • Full name
        • Filename
        • Type
        • Size
        • Time created
      4. Open Conditions in editor
      5. Confirm File > Directory condition is equal to No
      6. Confirm no directory entries are present in the report
      7. Set File > Directory condition to Is any value and apply
      8. Confirm directory entries are now present in the report
      9. Set File > Directory condition value back to No and apply
      10. Delete the following columns from the report:
        • User > Full name
        • File > Type
        • File > Time created
      11. Set aggregation for File > Filename column to Count
      12. Set aggregation for File > Size column to Sum
      13. Confirm report now shows count of files, and sum of filesize for each context
      14. Open Sorting in editor
      15. Sort by Size descending
      16. Confirm report is ordered correctly
      17. Add the following columns to the report:
        • File > Plugin
        • File > Area
        • File > Item ID
      18. Confirm report now shows count of files, and sum of filesize for each context/plugin/area/itemid
      Show
      Note: testing is easier on a brand new site, although can be tested equally on an older site, but there will likely be a lot more data being reported on Create some files Log in as admin Navigate to Profile Edit profile Add a User picture and save Create a new course Add a Course image and save Create report Navigate to Reports in user menu Create new report from Files report source Ensure Include default setup is checked Confirm presence of the following columns, with accurate data (note: as per start of testing instructions, there may be many more rows than just the files you created if using an existing site with historical data): Context Full name Filename Type Size Time created Open Conditions in editor Confirm File > Directory condition is equal to No Confirm no directory entries are present in the report Set File > Directory condition to Is any value and apply Confirm directory entries are now present in the report Set File > Directory condition value back to No and apply Delete the following columns from the report: User > Full name File > Type File > Time created Set aggregation for File > Filename column to Count Set aggregation for File > Size column to Sum Confirm report now shows count of files, and sum of filesize for each context Open Sorting in editor Sort by Size descending Confirm report is ordered correctly Add the following columns to the report: File > Plugin File > Area File > Item ID Confirm report now shows count of files, and sum of filesize for each context/plugin/area/itemid

    Description

      The purpose of this report is to provide an overview of the Moodle stored files, allowing admins to easily identify courses/activities which are consuming a lot of file space. It can also be used to identify licenses used across the site, identifying those missing attribution

      The new file entity will also be used in future reports on elements with associated/attached files

      Columns

      1. File
        • Name
        • Size
        • Path
        • Type
        • Author
        • License
        • Context
        • Plugin
        • Area
        • Item ID
        • Time created
      2. User
        • <everything from user entity>

      Conditions/filters

      1. File
        • Directory (boolean)
        • Drafts (boolean)
        • Name
        • Size
        • License
        • Time created
      2. User
        • <everything from user entity>

      Note, we need the sum/average aggregation improvements from MDL-75191 in order to improve report data, e.g. when calculating entire filesize of given context/filearea/etc

      Attachments

        1. MDL-75535_1.png
          MDL-75535_1.png
          170 kB
        2. MDL-75535_2.png
          MDL-75535_2.png
          180 kB
        3. MDL-75535_3.png
          MDL-75535_3.png
          177 kB
        4. MDL-75535_4.png
          MDL-75535_4.png
          86 kB
        5. MDL-75535_5.png
          MDL-75535_5.png
          83 kB
        6. MDL-75535_6.png
          MDL-75535_6.png
          123 kB

        Issue Links

          Activity

            People

              pholden Paul Holden
              pholden Paul Holden
              Roberto Bravo Roberto Bravo
              Sara Arjona (@sarjona) Sara Arjona (@sarjona)
              Angelia Dela Cruz Angelia Dela Cruz
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day, 1 hour, 15 minutes
                  1d 1h 15m

                  Clockify

                    Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.