Normalize isolate join and suspected_organism in assembly metrics #67
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
suspected_organismvalues, causing the UI to collapse many entries into an "Unknown" bucket instead of the real species./api/assemblies/metricsresults robust to whitespace and empty-string differences betweenassemblies.isolate_idandisolates.sample_id.Description
suspected_organism = func.nullif(func.trim(Isolate.suspected_organism), "")and return it in the assembly metrics payload inapp/app.py.outerjointo matchtrim(Assembly.isolate_id)withtrim(Isolate.sample_id)so joins succeed even when IDs have surrounding whitespace.app/app.pyand only affect the/api/assemblies/metricsquery projection.Testing
black .which reformattedapp/app.pyand completed successfully.pytest tests/which collected 9 tests and produced3 passed, 6 failedwith failures due tosqlite3.OperationalError: no such tablein the test environment, indicating missing DB tables rather than a regression in the changed code.suspected_organismand joins using trimmed IDs).Codex Task