Calculate best chapter strategies for quotation denormalization during analysis
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start by reading PretranslationService and the post-processing path that handles pretranslations. Trace how USFM fetching currently recalculates chapter strategies and how the model could expose stored results. Done means post-processing calculates and stores the strategies, while USFM fetching can use them and visibility into non-denormalizable chapters is available.
Written by the indexing model from the issue text.
Description
Currently, we have no visibility into how often quotation denormalization is not usable on particular chapters. The only place this information is captured is in a remark on the draft. Also, we recalculate these best chapter strategies for a book every time USFM is fetched.
If we calculated these in advance during post-processing (i.e., once we have the pretranslations), we would:
- have visibility into what chapters are denormalizable (could add a warning potentially as well)
- but have to store these strategies in the model somehow;
- increase the time it takes to run postprocessing by probably a few seconds
- but decrease the time and computational expense of fetching USFM;
- and also be able to simplify the
PretranslationServicelogic and potentially parse the USFM only once with all update block handlers.
- Dominant language
- C#
- Stars
- 3
- Forks
- 2
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 3
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.
More from sillsdev/serval
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·