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

Assessment created by TA of one section available to all student of that worksite

    XMLWordPrintable

    Details

      Description

      1. As admin, created a worksite and added a T&Q assessment and published it
      2. Had 3 different users access the worksite. So now I have 3 users with "access" role in the worksite

      OBSERVATION:

      Could not assign TA role to any of the users because they were not listed in the TA section. Had to change the role. So,

      3. Changed one of the users to a "maintain" role
      4. In the "Sections" tool
      a. Created 2 sections: "Discussion1" and "Lab1"
      b. assigned one of the "access" user to the 2 sections,
      c. assigned the other "access" user to the "Lab1" section only,
      d. assigned the "maintain" user as TA for the "Discussion1" section only

      5. Logged in as the TA and created an assessment and published it

      OBSERVATION:

      The published assessment is visible to both "access" users, even though the TA is only the TA for the "Discussion1" section, and the second user is not a member of the "Discussion1" section.

      ISSUE:
      =====
      In order to assign a TA to a section, the TA has to have a "maintain" role for the entire worksite.
      Need a way to limit the TA's access. HOW DOES USER2 KNOW THAT THE ASSESSMENT THAT WAS CREATED BY THE TA FOR THE "DISCUSSION1" SECTION IS NOT ONE THAT HE/SHE SHOULD TAKE, SINCE HE/SHE IS NOT IN THE "DISCUSSION1" SECTION?

      FEATURE REQUEST (See SAK-2664.)
      ===============
      I think, in the out-of-the-box (OOTB) Sakai version, a TA role should be created by default for the Project sites (in addition to "maintain" and "access").

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  flmover1 N Blackwood (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code