* API endpoint for certificate generation, an authenticated post with course
id requests that grading be carried out and a cert generated for
request.user in that course, using the usual grading and certificate
machinery (ie, it does not imply whitelisting, though whitelists and
blacklists will be respected)
- Logs each request as it comes in
- Calls xq.add_cert() and consequently, does grading synchronously on
this app host and then queues request for certificate agent.
- example usage:
```
curl --data "student_id=9999&course_id=Stanford/2013/Some_Class" http://127.0.0.1:8000/request_certificate
```
* Studio advanced setting added, "certificates_show_before_end", which
determines whether a course should permit certificates to be downloadable
by students before the coures's end date has passed.
- Modifications to dashboard view and templates to allow display of
certificate download links before course has ended.
(XXX: may declare failing students as failing before the course has ended.)
- To test, turn the setting on in a course which hasn't ended yet, and
force certificate generation for a student, then check their
dashboard.
Stanford had a problem a few times that certificate requests had
different values for the course display name and the course name printed
on the certificate and verification pages because of human error. This
passes the course display name on the queue to the certificate requests,
so that at least one place where the course name is reproduced (the
certificate agent's settings.py) can be eliminated.
Also removes the unnecessary pre-fetch.
For certificate generations we will continue to generate certs for
both active and inactive users.
For the report we only display active users since it was confusing
due to the instructor dashboard only displaying active users.
* -G allows explicit setting of grade condition (e.g., a string such as
'Distinction', 'Pass', 'F', 'B') for the certificate, regardless of
grader output for the user.
* -T allows explicit request of a particular certificate template to be
applied to a given user's certificate regeneration, i.e.:
-T doctor_distinction.pdf
to generate a certificate of distinction for doctors.
Quick-and-dirty end-to-end flow, functional for at least the case of one course in need of re-verification.
Ready for design to start taking a look; still needs tests and code cleanup
* output after cert_whitelist -a or -d purported to be the whitelist entries
for the requested course, but in fact were all of the entries in every
course. This commit fixes that.
* Adds regenerate_user command, which lets you run certificates for one
particular user in one particular class, regardless of whether they
have a pre-existing certificate.
There was a potential though unlikely race condition because the .save()
was after the certificate request was put on the queue.
Now calling .save() immediately after we update the
cert.
Without this, problems fail to load because they can't find how to
render themselves, and the certificate generation grading run will
get an inaccurately low count of the possible points a user could
get (anything they didn't see will be omitted), inflating their
grade during certificate calculation and making it inconsistent
with their Progress page.
This will allow you to force the certificate generation
for when certificate requests are lost and stuck in
'generating', this happens when we have xqueue issues.
