Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-25240

Statiscs for user posts read

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: RESOLVED
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Messages Tool
    • Labels:
      None
    • Environment:
      all
    • Previous Issue Keys:
      MSGCNTR-317

      Description

      We would like to suggest two features be added to the statistics portion of the Forums tool. These have to do with instructors being able to assess the degree to which Forum posts are being created and read.

      a. Add two columns to the existing screen: "Authored Posts Read by Others" and "Percent Authored Posts Read by Others". These two would add a dimension for the degree to which a Forum poster is reaching his or her audience and engaging others in reading the posts. It would also help a faculty member identify students that aren't getting their fair share of feedback from other students. Of course both columns should be sortable, just as the current columns are sortable.
      b. Add the ability to look at statistics for a specific forum or a specific topic (or, if you want to go all the way, for a specific thread). One method would be to add a "statistics" link to each forum and topic that would take the user to the current screen, but only display statistics for the subset indicated. The rationale is similar to the rationale above, but it would allow a professor to narrow the analysis down to a specific assignment or discussion topic. The data could be presented on a screen similar to the current Statistic screen.

      As an interesting sidenote – the ability to "Mark All as Read" causes some issues for professors, since the posts weren't really read. Currently professors look for "read" timestamps that are very close to each other and that therefore probably indicate the use of the Mark All as Read technique.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                maintenanceteam Core Team
                Reporter:
                arwhyte Anthony Whyte
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Git Source Code