Review and promote missing FSN in <locale> using translation + conflict checks

[filiperochalopes]

User story

As a curator, I want to identify concepts missing a FULLY_SPECIFIED name in a given locale and decide whether to promote an existing name to FSN so locale coverage improves without creating duplicates or conflicts.

Use case

Run a query for a locale (e.g., fr), export translation requests, compare translations with the best OpenMRS English name, and decide whether to promote or fix.

Requirements

• Provide a workflow based on the SQL output to triage candidates where the locale has no FSN:
  • Use translation to English for promote_name_foreign.
  • Compare translated English with english_name_from_openmrs.
• Promotion decision rules:
  • If translation semantically matches english_name_from_openmrs, then the name can be promoted (when eligible).
  • If translation does not semantically match, then fix the locale name before promoting.
• Handle conflicts:
  • If eligible_to_promote = 0 (preferred or FSN name conflicts with other concepts), then do not promote directly.
  • For eligible_to_promote = 0, choose an alternative solution:
    • Use a different name on the same concept, OR
    • Create a new concept (when needed).

Acceptance criteria

• Given SQL results for a locale, the curator can identify:
  • rows where translated English differs from english_name_from_openmrs and require review/fix before promotion
  • rows where eligible_to_promote = 0 and require a non-promotion resolution path
• Given a row where translation semantically matches and eligible_to_promote = 1, the workflow supports promoting the locale name to FULLY_SPECIFIED.
• Given a row where eligible_to_promote = 0, the workflow results in either selecting a different name on the same concept or creating a new concept.