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

Add configuration to expose content-review errors to the UI

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 20.0
    • Fix Version/s: 19.3, 20.0
    • Component/s: content review
    • Labels:
      None
    • 19 status:
      Resolved
    • Property addition/change required:
      Yes
    • Test Plan:
      Hide
      1. Submit to a content-review enabled assignment in a manner that will result in an error status. E.g. if you're using Turnitin, submit a paper with fewer than 20 words.
      2. Run the queue job / report jobs as appropriate until the paper enters an error status.
        • That is, your contentreview_item enters a status other than 1 (pending submission), 2 (pending report), or 3 (complete), and hopefully the last_error column will be populated.
      3. When viewing the student's submission, hover the cursor over the originality report that is in an error state. Ensure the hover text ends with something like:
        "Latest response from Turnitin: the submission contains less than 20 words"

      Then set contentreview.expose.errors.to.ui=false in sakai.properties, and ensure that message is no longer visible

      Show
      Submit to a content-review enabled assignment in a manner that will result in an error status. E.g. if you're using Turnitin, submit a paper with fewer than 20 words. Run the queue job / report jobs as appropriate until the paper enters an error status. That is, your contentreview_item enters a status other than 1 (pending submission), 2 (pending report), or 3 (complete), and hopefully the last_error column will be populated. When viewing the student's submission, hover the cursor over the originality report that is in an error state. Ensure the hover text ends with something like: "Latest response from Turnitin: the submission contains less than 20 words" Then set contentreview.expose.errors.to.ui=false in sakai.properties, and ensure that message is no longer visible

      Description

      For content review errors, we currently swallow any messages from the content review service, and instead display messages from our own message bundles such as the following:
      "An error occurred while submitting this item to the originality checking service."

      It can be beneficial to show content-review errors to end users so that they can understand and resolve issues on their own, such as "the submission contains less than 20 words", "the due date has passed", etc.

      Add configuration in sakai.properties allowing institutions to display these messages to end users

        Gliffy Diagrams

          Zeplin

            Attachments

              Activity

                People

                Assignee:
                bbailla2 Brian Baillargeon
                Reporter:
                bbailla2 Brian Baillargeon
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Git Integration