When viewing a question an anonymously released assessemnt the title bar says "Item Display - Author mode." The Table of Contents says Table of Contents. Not sure why this is, but this is probably going to confusing some users. Occurs on our nightly build as well as on Stanford's stand alone instance.
I'm going by these specs:
Just want to let you know that the published url for anonymous user has been implemented based on the following spec that Lance sent us last week. The only thing that I didn't do is item 6. I am not sure if cookie is the way to do it as people do share computers in public clusters. I need more time to think about it and decide how we can add this to 2.0 so we can keep track of the attempts. OK?
At 02:57 PM 2/9/2005, Speelmon, Lance D wrote:
Let me see if I can help clear things up regarding anonymous assessment delivery.
1. If assessments are published to the "Anonymous" target, the URL is the only form of navigation that anonymous users have to find the assessment.
2. The generated URL will be used by both anonymous and authenticated users.
3. If a user accesses the URL and the assessment has been published to "Anonymous" then the user would begin the assessment without any additional input.
4. If a user accesses the URL and the assessment has not been published to "Anonymous" then the user would be prompted for authentication, and then taken to the begin assessment screen.
5. We suggest that a new Agent (and AgentId) is generated for each anonymous test taking session. This will help identify unique response sessions; i.e. if the assessment is published to "Anonymous", and the user is beginning the assessment via the URL, then the number of attempts is effectively infinite. However, if the user is not using the URL, then number of attempts can be enforced as the user is identifiable.
6. Number of attempts and Anonymous delivery are somewhat incompatible. The only way I can think to possibly address this issue is to use a browser cookie in an attempt to track state.
7. Remember that we also have an "Authenticated Users" publishing target which can be useful if the behavior described above does not suit the needs.