Details
Improvement
New
Minor
Description
For resolver purposes the following data are needed in json format for every submission(report):
- time of submission
- submitter data (probably login or/and id)
- task id
- submission score
- id of first test not marked as "OK"
( optionally - list of tests and verdicts )
- time of submission
- submitter data (probably login or/and id)
- task id
- submission score
- id of first test not marked as "OK"
( optionally - list of tests and verdicts )
Activity
Paweł Dietrich
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
For resolver purposes the following data are needed for every submission(report):
- time of submission - submitter data (probably login or/and id) - task id - submission score - id of first test not marked as "OK" ( optionally - list of tests and verdicts ) |
For resolver purposes the following data are needed in json format for every submission(report):
- time of submission - submitter data (probably login or/and id) - task id - submission score - id of first test not marked as "OK" ( optionally - list of tests and verdicts ) |
Hide
Tomek Waleń
added a comment -
Permalink
Tomek Waleń
added a comment - Do you think about additional command for exporting reports (i.e. as CSV or collection of JSONs) or something in web-interface (like current export of submissions)?
Show
Tomek Waleń
added a comment - Do you think about additional command for exporting reports (i.e. as CSV or collection of JSONs) or something in web-interface (like current export of submissions)?
Tomek Waleń
added a comment - Do you think about additional command for exporting reports (i.e. as CSV or collection of JSONs) or something in web-interface (like current export of submissions)? I asked Bartek if he would prefer to have it generated manually or available on some endpoint and he responded that "it is fine to be manually extracted, but an endpoint would be nice".
I think in terms of endpoints an API endpoint would be great; in terms of manual export button "Download summary" in django-admin submissions view is proper place for it. Also a ./manage.py command can be handy.
(When I think about it: with any two of those places, the third one can be achieved with little work.)
I am not convinced yet whether it should be a global feature of PA only.
I think in terms of endpoints an API endpoint would be great; in terms of manual export button "Download summary" in django-admin submissions view is proper place for it. Also a ./manage.py command can be handy.
(When I think about it: with any two of those places, the third one can be achieved with little work.)
I am not convinced yet whether it should be a global feature of PA only.
Show
Paweł Dietrich
added a comment - I asked Bartek if he would prefer to have it generated manually or available on some endpoint and he responded that "it is fine to be manually extracted, but an endpoint would be nice".
I think in terms of endpoints an API endpoint would be great; in terms of manual export button "Download summary" in django-admin submissions view is proper place for it. Also a ./manage.py command can be handy.
(When I think about it: with any two of those places, the third one can be achieved with little work.)
I am not convinced yet whether it should be a global feature of PA only.
Paweł Dietrich
added a comment - I asked Bartek if he would prefer to have it generated manually or available on some endpoint and he responded that "it is fine to be manually extracted, but an endpoint would be nice".
I think in terms of endpoints an API endpoint would be great; in terms of manual export button "Download summary" in django-admin submissions view is proper place for it. Also a ./manage.py command can be handy.
(When I think about it: with any two of those places, the third one can be achieved with little work.)
I am not convinced yet whether it should be a global feature of PA only.
