Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Incomplete timestamps in reports #152

Open
hgeorgsch opened this issue Oct 20, 2019 · 1 comment
Open

Incomplete timestamps in reports #152

hgeorgsch opened this issue Oct 20, 2019 · 1 comment
Assignees
@sushanthko
Labels
bug Something isn't working good first issue Good for newcomers report capquizreport sub-plugin

Comments

@hgeorgsch
Copy link
Contributor

In the statistics reports, the timestamp is written as a string using writing the date in badly localised format and the time using a 12-hour clock without specifying am/pm. (This seems to be the same for openoffice, CSV, and HTML display.)
What is important is that the timestamps

  1. be unambiguous,
  2. be formatted as complete date/time fields in libreoffice
  3. be easily parsed as timestamps by standard python libraries.
@hgeorgsch hgeorgsch added bug Something isn't working good first issue Good for newcomers labels Oct 20, 2019
@hgeorgsch hgeorgsch added the report capquizreport sub-plugin label Aug 3, 2020
@sushanthko
Copy link
Member

sushanthko commented Aug 13, 2020 •
edited
Loading

The timestamps in both questions and attempts reports seem to have been specified with AM/PM. Below are some entries from the .csv files.
"Time created" - "20 January 2020 10:34:33 PM"
"Time answered" - "20 January 2020 10:34:33 PM"
"Time reviewed" - "20 January 2020 10:34:41 PM"
@hgeorgsch

@sushanthko sushanthko self-assigned this Aug 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sushanthko sushanthko

Labels
bug Something isn't working good first issue Good for newcomers report capquizreport sub-plugin
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hgeorgsch @sushanthko