Don't pass params to server.gradeAnswer() for questions. Instead have a question class that implements this, or other things like automating the getData() pattern.

Add an interface to the client to GET /export.csv and create a similar export.json endpoint. The main question here is how to handle authentication. The link needs to include auth information in the request headers, so it needs to be generated by javascript, but it then needs to trigger a download/file-save in the browser.

Add the concept of a "course" to the system, with a CID (course ID). Courses should contain lists of users, questions, and tests. On the client side there should be a "currently active course" concept, and the server API should be augmented to take a CID parameter to operations like GET on all questions or tests, so that we just get the appropriate tests and questions.

Add a field for "related resources" in the info.json for each question and display it somewhere on the question page (presumably in the sidebar).

Eventually this should augmented by recommendation-engine-generated resources and click-throughs should be tracked.

Add more hooks where test code is called, such as for tInstance and qInstance creation. This should enable tests to do things like:

• Tests can have sub-tests with shared VIDs.
• We should have a fixed qInstance (with a fixed VID) until it is answered.

Students frequently requested being able to find out how a given practice exam question mapped back to the homework question numbering. In general this is a problem when we re-use questions and users want to be able to see the back-mappings to tests from questions.

• Don't reload whole page on link-clicks and other navigation.
• Don't serialize the loading of API data.

Add user statistics incrementally on every submission or other API request and remove current 10-minute stats computation. This will be more scalable for large courses.

Also add more per-question statistics, such as median-time-to-complete.

Clicking "New attempt at this exam", then doing a question, then grading, then clicking "Exams" in the navbar, gives a list of exam attempts with the new exam at the bottom, not at the top where it should be.

At the moment the server runs out of open files after some amount of time. This can be mitigated by increasing the open-file-handle limits and periodically restarting the server, but we should see whether we can also force long-standing connections to be terminated more quickly.

At the moment all code and HTML associated with a specific test is dynamically loaded, but perhaps this should just be hard-coded in the client, given that we don't really have all that many different types of tests?

Remove:

• qScores
• "Question" tab on client

Question performance statistics need to be imported from external sources (e.g., randexam). For now we can just do this by hand.

We should spawn helper node subprocesses and use them to run any instructor-written code (question and test server.js code). This would allow:

• Robustness to arbitrary errors in code.
• Protection of global state.
• Implementation of timeouts.

Instructors need to be able to easily access aggregate statistics, such as student score distributions on each homework, completion percentages for assessment items, etc. This should probably be done by "tests", as it is rather test-specific. We should probably also expose as much of this as possible to students, or at least allow this on a course-by-course basis.

Add a web interface allowing online editing of questions, tests, etc. This could be done by shifting question/test code into the DB, or by just directly editing the on-disk files.

There is currently code to differentiate the "effective user" from the "authenticated user", just like the unix notion of UID/EUID. This allows instructors to act as if they were a particular student, which is an easy way to see user scores, etc, without adding a special instructor view of information that a student can already see about themselves. We need to fix:

• EUID is currently reset on some page-loads and is generally a bit flakey. This needs to be fixed.
• We need a better interface for switching EUID for instructors, that should work for both large and small courses.

Should each question include set of test data so we can run automatic tests against the full system, or at least part of the system?

Add a global handler for timeouts and errors on data load (JS, images, other files) and add a generic "retry" interface to the client. This should involve both automatic and manual retries, with generic user feedback (e.g., an error div at the top of the page).

Add a separate div for questions to use as a "Answer Box" to display the true answer after grading is complete.

The names we have for various objects may not be very good. For example:

• "test" could be called "assessment" or something more generic.
• "qInstance" could be called "questionInst" so that it is more obvious what it is, and so that it won't conflict with future instance-types that also start with the letter "q".

Add API info for test and tInstance.

Currently PrairieDraw errors on missing images. Instead it should substitute a place-holder image, or just nothing.

Set up a hosted experience so that PrairieLearn can be used without having to set up dev and deployment instances for every class. This depends on:

• 10 Add courses as a concept.

• 11 Allow online editing of data.

• Actually setting up a hosted instance, perhaps at prairielearn.engr.illinois.edu or prairielearn.illinois.edu or similar.