{"action":"created","issue":{"url":"https://api.github.com/repos/code-dot-org/code-dot-org/issues/7257","repository_url":"https://api.github.com/repos/code-dot-org/code-dot-org","labels_url":"https://api.github.com/repos/code-dot-org/code-dot-org/issues/7257/labels{/name}","comments_url":"https://api.github.com/repos/code-dot-org/code-dot-org/issues/7257/comments","events_url":"https://api.github.com/repos/code-dot-org/code-dot-org/issues/7257/events","html_url":"https://github.com/code-dot-org/code-dot-org/pull/7257","id":140159821,"number":7257,"title":"WIP assess: Long assessments over several \"levels\"","user":{"login":"breville","id":2205926,"avatar_url":"https://avatars.githubusercontent.com/u/2205926?v=3","gravatar_id":"","url":"https://api.github.com/users/breville","html_url":"https://github.com/breville","followers_url":"https://api.github.com/users/breville/followers","following_url":"https://api.github.com/users/breville/following{/other_user}","gists_url":"https://api.github.com/users/breville/gists{/gist_id}","starred_url":"https://api.github.com/users/breville/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/breville/subscriptions","organizations_url":"https://api.github.com/users/breville/orgs","repos_url":"https://api.github.com/users/breville/repos","events_url":"https://api.github.com/users/breville/events{/privacy}","received_events_url":"https://api.github.com/users/breville/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":{"login":"laurelfan","id":7763,"avatar_url":"https://avatars.githubusercontent.com/u/7763?v=3","gravatar_id":"","url":"https://api.github.com/users/laurelfan","html_url":"https://github.com/laurelfan","followers_url":"https://api.github.com/users/laurelfan/followers","following_url":"https://api.github.com/users/laurelfan/following{/other_user}","gists_url":"https://api.github.com/users/laurelfan/gists{/gist_id}","starred_url":"https://api.github.com/users/laurelfan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/laurelfan/subscriptions","organizations_url":"https://api.github.com/users/laurelfan/orgs","repos_url":"https://api.github.com/users/laurelfan/repos","events_url":"https://api.github.com/users/laurelfan/events{/privacy}","received_events_url":"https://api.github.com/users/laurelfan/received_events","type":"User","site_admin":false},"milestone":null,"comments":2,"created_at":"2016-03-11T11:25:23Z","updated_at":"2016-03-16T22:17:08Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/code-dot-org/code-dot-org/pulls/7257","html_url":"https://github.com/code-dot-org/code-dot-org/pull/7257","diff_url":"https://github.com/code-dot-org/code-dot-org/pull/7257.diff","patch_url":"https://github.com/code-dot-org/code-dot-org/pull/7257.patch"},"body":"This adds a working multi-page assessment, implemented as a level_group-type level.  It's set up to come at the end of a regular stage, and is indicated by an \"assessment\" tag in the .script, and more than one page specified in the .level_group file, like so:\r\n\r\n```\r\n  page \"first page title\"\r\n  level \"first level\r\n  level \"second level\"\r\n\r\n  page \"second page title\"\r\n  level \"third level\"\r\n```\r\n\r\nThe progress bar at the top of the level, and the drop-down stats below it, display the new extra assessment levels, though they don't exist as separate levels in the database, and are instead generated by the server's \"summarize\" family of functions.  \r\n\r\nThese extra levels make use of new routing, so that the first level is /puzzle/2/page/1, next is /puzzle/2/page/2, etc.  The level's own JavaScript takes care of jumping to the next URL in this particular scheme.  Going to \"Next page\" on any of the intermediate pages silently submits the entire set of results for that LevelGroup before navigation occurs.  The final level of the long assessment uses a more typical \"Submit\" and allows the server to tell it what comes next.\r\n\r\nOnce submitted, all dots become purple, and \"Unsubmit\" becomes available on the final page, and prompts for confirmation when clicked.\r\n"},"comment":{"url":"https://api.github.com/repos/code-dot-org/code-dot-org/issues/comments/197580827","html_url":"https://github.com/code-dot-org/code-dot-org/pull/7257#issuecomment-197580827","issue_url":"https://api.github.com/repos/code-dot-org/code-dot-org/issues/7257","id":197580827,"user":{"login":"laurelfan","id":7763,"avatar_url":"https://avatars.githubusercontent.com/u/7763?v=3","gravatar_id":"","url":"https://api.github.com/users/laurelfan","html_url":"https://github.com/laurelfan","followers_url":"https://api.github.com/users/laurelfan/followers","following_url":"https://api.github.com/users/laurelfan/following{/other_user}","gists_url":"https://api.github.com/users/laurelfan/gists{/gist_id}","starred_url":"https://api.github.com/users/laurelfan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/laurelfan/subscriptions","organizations_url":"https://api.github.com/users/laurelfan/orgs","repos_url":"https://api.github.com/users/laurelfan/repos","events_url":"https://api.github.com/users/laurelfan/events{/privacy}","received_events_url":"https://api.github.com/users/laurelfan/received_events","type":"User","site_admin":false},"created_at":"2016-03-16T22:17:08Z","updated_at":"2016-03-16T22:17:08Z","body":"The teacher dashboard impact:\r\n* on the \"student progress\" page, multipage levels will be expanded (because this uses user_stats)\r\n* on the \"section progress\" page, multipage levels will be one level. Including when you click to expand a stage.\r\n\r\nI assume that's what's designed and it makes sense if we're thinking that the section progress view is designed for an \"overview\". However it could be confusing that the expanded stage view looks so much like the user_stats view but will have a different number of levels."}}