Mneme - Docs

Auto-Completion of Submissions

Mneme runs a thread which periodically checks all open submissions to find any that need to be automatically closed. These are the submissions that have past their due dates (or accept until dates), or have exceeded their time limits. The submissions that are found are closed, with whatever answers have been submitted. The final submit date is marked as the exact moment the assessment was due or timed out.

In order to not interfere with submissions actively in progress, we use a grace period of 4 minutes; this thread will recognize expired submissions 4 minutes after their expiration time.

The thread wakes up every 5 minutes to check. This happens on each app server. This time can be configured with an entry in

sakai.properties:

timeoutCheckSeconds@org.muse.mneme.api.SubmissionService=600

This example sets the time between checks to 600 seconds, or 10 minutes. Set it to 0 to disable this function completely.

Before we show a list of submissions to learners in delivery, or to graders in grading, each submission is checked for expiration and auto-completed. This happens even if the auto-completion thread is disabled.

Clearing Expired Mints

When a new question, pool or assessment is created in Mneme, it is immediately committed to the database with a unique id but no user-specified data. Objects in this state are considered "Mint". Once the user enters a question, pool title, assessment title, or any other information, the object is no longer considered mint.

If a user creates an object, but then enters no information for the object when presented with the edit user interface, the mint object is automatically deleted. If the user abandons a newly created mint object by means other than any Mneme tool action (such as logging out, closing their browser, or switching to another tool never to return in the session), the mint object is left behind in the database. It won't be shown to the user again, but it is taking up space.

Mneme runs a thread which periodically finds expired mint objects and removes them. Because we don't know when one of these object is abandoned by the user, we wait an extremely long period of time before we decide it is expired and remove it. Any mint object that was created more than one day ago is considered to be expired.

The thread runs once every 12 hours on each app server. This time can be configured with an entry in sakai.properties:

timeoutCheckSeconds@org.muse.mneme.api.MnemeService=86400

This example sets the time between checks to 86400 seconds, or 24 hours. Set it to 0 to disable this function completely.