Docs

Event Model

Each event has an event type identifier string, which tells what happened, and a reference string, which tells which object it happened to. Each event also identifies a user responsible for the event (through a Sakai session reference), and has a code which states if the event was read or write.

The event type identifiers for Mneme all start with “mneme.”. The references may be to a question, pool, assessment or submission. We also use a question-in-submission reference when submitting an answer to a particular question in a submission.

The references look like this (the “<… id>” stands for the object’s internal id):

/mneme/question/<question id>

/mneme/pool/<pool id>

/mneme/assessment/<assessment id>

/mneme/submission/<submission id>

/mneme/submission/<submission id>:<question id>

Mneme records events from authoring, publishing, delivery and grading. The events ending in “.new” are generated when something is first created. The events ending in “.edit” are generated whenever something is changed by the end-user in any way. The events ending with “.delete” are generated when something is deleted.

Authoring events refer to questions and pools:

mneme.pool.new

mneme.pool.edit

mnene.pool.delete

mneme.question.new

mneme.question.edit

mneme. question.delete

Publishing events refer to assessments:

mneme.assessment.new

mneme.assessment.edit

mneme.assessment.publish – when an assessment is published

mneme.assessment.unpublish – when an assessment is unpublished

mneme.assessment.delete

Delivery events refer to submissions and questions answered in submissions:

mneme.enter – when a new submission is started

mneme.continue – when a submission that was not completed is returned to to be worked on.

mneme.answer – for each answer made by the learner in a submission (references a question-in-submission)

mneme.complete – when the learner finishes a submission

mneme.auto_complete – when Mneme automatically finishes a submission for the learner

mneme.review- when a learner reviews a submission

Grading events refer to submissions:

mneme.grade – when a submission is graded, with score or comment, or when a submission is retracted or released to the learner.

Security Functions

Mneme is secured using three permission string:

mneme.submit

mneme.manage

mneme.grade

mneme-submit is the permission that allows an end-user to make submissions to assessments. This is given to the access / student roles. In the default Sakai authzGroup templates, this permission should be given to “access” and “Student’

mneme-manage is the permission that allows the end-user to create, edit, and otherwise manage the authoring and publishing artifacts; questions, pools and assessments. This is given to the maintain / Instructor roles. In the default Sakai templates, this permission should be given to the “maintain” and “Instructor” roles, and possibly to the “Teaching Assistant” role.

mnene.grade is the permission that allows the end-user to grade submissions. This should also be given to the maintain / Instructor roles, along with mneme-manage.

 

Notes:

Do not give the maintain roles mneme-submit. End-users in these roles will be able to test-drive assessments without this permission. Also, it is probably best to give mneme.manage and mneme.grade together; this is how we have been testing.

Sakai will *not* have these permissions in the authzGroup templates; you have to add them. You can do that manually, or using the Mneme Admin tool. See the configuration section in the Download Mneme page for more details.

 

Sakai Properties

There are a few options that can be set in sakai.properties to change how Mneme behaves.

Paging in the UI

There are four places in the Mneme user interface where a paging component is presented to the end-user to control the amount of information displayed in the view.

The page size can be set in each of these places. There can be a single page size, or a set of options for page size that the end-user can select.

A page size option of 0 means “all”, and will show all the items on a single page.

These four paging components can be set as follows:

1. To control the pager in “Grade Questions”, controlling how many question answers are on the page, use this:

pageSize@org.etudes.mneme.tool.GradeQuestionView=10

The default for “Grade Questions” is a single option of 10.

2. To control the pager in “Grade Submissions”, controlling how many submissions are listed on the page, use this:

pageSize@org.etudes.mneme.tool.GradeAssessmentView=30,100,0

The default for “Grade Submissions” is a set of options for 30, 100, and “all”.

3. To control the pager in the pool edit view, controlling how many questions in the pool are listed on the page, use this:

pageSize@org.etudes.mneme.tool.PoolEditView=10,0

The default for “Grade Questions” is a single option of 30.

4. To control the pager in the “Select Questions” view when publishing an assessment, controlling how many questions to select are listed on the page, use this:

pageSize@org.etudes.mneme.tool.SelectAddPartQuestionsView=10,0

The default for “Select Questions” is a single option of 30.

Background Processing

There are two background processes run by Mneme. Their timing can be controlled in sakai.properties.

1. To control the auto-completion thread’s timing use this:

timeoutCheckSeconds@org.etudes.mneme.api.SubmissionService=300

The default is 300 seconds (5 minutes). Set to 0 to disable.

2. To control the expired mint cleanup thread’s timing, use this:

timeoutCheckSeconds@org.etudes.mneme.api.MnemeService=43200

The default is 43200 seconds (12 hours). Set to 0 to disable.

Templates and Roles for the Mneme Admin Tool

The admin tool uses a list of standard site authGroup templates and role names for some of its features. These can be set in sakai.properties.

1. To set the list of site authzGroup templates used in your installation, use this:

templates@org.etudes.mneme.tool.InstallTemplatesView=!site.template,!site.template.course,!site.template.project

The default is “!site.template,!site.template.course,!site.template.project”.
Separate the templates in the list with a comma.

2. To set the list of “access” roles you use, use this:

accessRoles@org.etudes.mneme.InstallView=access,student

The default is “access,student”. Case does not matter.
Separate the roles in the list with a comma.

3. To set the list of “maintain” roles you use, use this:

maintainRoles@org.etudes.mneme.InstallView=maintain,instructor,teaching assistant

The default is “maintain,instructor,teaching assistant”. Case does not matter.
Separate the roles in the list with a comma.

Print Friendly, PDF & Email