sillsdev / sillsdev/serval

Calculate best chapter strategies for quotation denormalization during analysis

Open
#804 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
3
Forks
2
Avg merge
3d 1h
Merged PRs (30d)
3

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 PretranslationService logic and potentially parse the USFM only once with all update block handlers.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
csharp
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.