Question: How do I see student solutions?

[heades]

Related user(s):

No response

Related issue(s) or PR(s):

No response

Related project scope(s):

No response

Question?

I'm not sure how to see the students solutions. Is this in the docs? I may have missed it.

What has already been tested:

I did look at the Teach link, but not seeing a way to actually see student answers.

learn-ocaml --version

No response

git describe --long --always --abbrev=40 --tags

No response

What OS do you use?

GNU/Linux

What browser(s) do you use with learn-ocaml?

No response

Additional context:

No response

[erikmd]

Dear @heades,
Good question, it appears the possible teacher workflows are not very well documented currently…
(Just tagged your issue as kind: documentation BTW.)
To sum up, as a teacher (having a so-called "teacher token" starting with X-xxx-xxx-xxx-xxx) you can indeed browse the Teach tab then see the list of exercises and the list of students tokens:

• then double-click on any student line to see the list of all the exercises he/she participated in, including their code (provided they clicked on Grade!, Sync would not be sufficient… we plan to improve this).
• or middle-click on an exercise to trigger the "partition-view" feature → cf. e.g. slide 10/20 of this presentation of mine: https://www.irit.fr/~Erik.Martin-Dorel/exposes/2022-W12_learn-ocaml_features.pdf (unfortunately this does not seems available on macOS, cf. issue #500).
• or clone the underlying git repository of a given student → cf. e.g. slide 8/20 of the same presentation.

hoping that this helps; but feel free to ask more details

[erikmd]

Also—just to recall—, if you are teacher and admin of your learn-ocaml instance, you can also fetch/backup/… the students solutions in the ./sync subdirectory (or in the typically-mounted-in-a-volume /sync directory if you use the official docker images).

[heades]

Thanks so much @erikmd ! This helps a lot, and I now have it figured out. Sorry I didn't close this sooner.

[erikmd]

I reopen this issue as it was symptomatic of some incomplete documentation on this topic.