Child pages
  • Conditional Release of Entities
Skip to end of metadata
Go to start of metadata

UPDATE: Work has started on this idea. See for details.

Like in other LMSs, Sakai should support conditional release of elements.


Prof. Martin requires his students to read his syllabus and get at least 90% on a quiz he has prepared to assess what their students understand of it. Students are allowed to retake the quiz as many times as needed to get the required passing grade.

Diego (a student in Prof. Martin's course) doesn't see anything in his course site but a link to the syllabus, and a link to a Quiz called "You must pass this quiz before accessing course material for week 2". Diego looks at the site files in the Resources tool, thinking he could bypass this requirement, but still doesn't see anything but the PDF syllabus file.

Diego reads the syllabus and attempts the quiz for a first time. He gets 80%. Nothing happens, he has to do it again.

Diego passes the quiz on his second attempt, and a new link appears in his menubar, linking to all class material for the next week, including resources and learning activities.

Examples of Release Triggers

  • Completion of a quiz.
  • Satisfactory grade on a quiz.
  • Submission of an assignment.
  • View of a page (requires tracking)
  • Release of the grade of an assignment.
  • Information in a Gradebook/Post'Em column.
  • Date/time.
  • Filtered by user/group/section.
  • Post on a forum topic by a user.
  • Group membership.
  • Alphabetical order (Example: Last name starts with a "P" or higher).
  • A combination of the previous triggers.

Permission Scheme

Could we have some sort of "cascading permission scheme" to deal with permissions?

  • Item permissions
    • Page permissions
      • Entity permissions

Children permissions could override parent permissions.