MAQ-Observations / MAQ-Observations/pre-processing
Improve submission logging
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Would be nice to improve the submission logging of the Post2API scripts and get some kind of log file with unsuccessful submits that gets reported (emailed) once its growing.
Another nice feature would be to once in a while take this log file and make some kind of script that automatically tries to repost this data.
Since August 2024 both the SQL database and the preprocessing/posting server are very stable but you never know what might pop up in the future and this could give a head start.
This could also help in the future if somehow any of the three sites is temporarily down or has no stable connection with WURnet.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Post2API preprocessing and posting scripts to understand how submissions currently reach the SQL database and the three sites. Clarify the scope for recording unsuccessful submits, emailing a growing log, and optionally retrying them. Done should include an agreed failure-log and reporting behavior, with retry automation included only if that scope is confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100