Bug Reports

There is a list of LMS bug reports here

If you notice a problem with the LMS please look at this list to check that the problem has not been reported already. If you wish to report a new problem request a new feature please use the main Ask for help link.

There is a list of LMS new feature requests here

Auto reating report show status from rating system

It would be possible to show the status of an event in the rating system. This could be done either by using the emails sent by the rating system or by doing a query on the rating database.

EMAILS:
But I thought there was an e-mail being sent back to the LMS which gave a one-line report on each file in the submission in a format which was supposed to be machine readable. Essentially the format is:

<event_code> : <status> <results_officer_address>

The values of the event code then being OK, FAILED, UNKNOWN PLAYERS, and NOT COMMITTED - the last only appearing if a submission is made with check_and_report_only selected.

QUERY:

The status is not directly available in a table. Maybe it ought to be!

There is away to extract the data from a table but it requires parsing a field which contains a JSON value. Whether that is easier than parsing an e-mail is up to you.

You know the event code and the submission number, so the query you need (broken into components for readability!) is :

https://rating.englishchess.org.uk/v2/submit/dump_table.php?
format=json&
table=submissions2&
where=event_code=%27LN00004688%27%20and%20submission_no=20&
columns=event_code,submission_no,issues

The issues field is a (possibly empty) json list, each element being an error message string. The format of each string is the message number (3 digits), followed by the literal string ' - ', followed by the text of the message. The mapping from status codes reported in the summary to the contents of the issues field is:

OK: issues list is empty
UNKNOWN PLAYERS: no error code other than 101 or 103 present
NOT COMMITTED: no record found in submissions table (should imply check_and_report_only was requested)
FAILED: all other cases

A quicker check would be to include the date_time_committed column in the query; if that field is null then the status would be OK. However, that would not distinguish between UNKNOWN PLAYERS and FAILED, and from the perspective of an LMS Results Officer (specifically one who is not a Rating Officer) user the critical difference is whether or not the status is FAILED, since UNKNOWN PLAYERS amounts to OK once Matt deals with the new players.

Hope this helps.

Dave

Assigned to
Category
Enhancement Request
Status
New
Priority
Low