Build an OCDS Multilingual Procurement Translation Review Workspace

Parse OCDS tender releases containing multilingual free-text descriptions. Consolidate language-suffixed party names and default language tags to unify fragmented supplier compliance records for efficient evaluation.

A multilingual procurement document translation review workspace that preserves original entity names.

Ingest simplified synthetic OCDS procurement releases containing language-suffixed party arrays and default language tags.

Extract base entity descriptions and normalize language tags using standard BCP47 codes.

Consolidate duplicate party records that differ only by translated names or regional suffixes.

Output a unified tender entity ledger linking consolidated supplier profiles to their original language variants.

Translation review workspace displaying canonical entity names alongside their parsed regional suffixes and language codes.

Simplified synthetic app records structured as OCDS JSON payloads featuring simulated name_es, name_fr, and default language fields. Starter examples below are synthetic. They are not downloaded records.

Open Contracting Data Standard Guides the extraction of language-suffixed fields and default language tags for consolidating multilingual party entities according to OCDS schema conventions.

pydantic-ai, fastapi. Ensures strict validation of BCP47 tags and schema-compliant party dictionaries when extracting canonical and translated entity names. LLM capable of mapping multilingual field suffixes to canonical party entities.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Correctly parses the default language and identifies all language-suffixed fields within a party array.

Consolidates related translations into a single canonical entity record without losing the original language variations.

Accurately maps recognized language tags to their corresponding translated strings in the output structure.

```json [ { "input": { "record_type": "simplified synthetic app record", "language": "en", "parties": [ { "id": "party-1", "name": "Water Works", "name_es": "Obras Sanitarias", "name_fr": "Service des Eaux" } ] }, "expected_output": { "canonical_id": "party-1", "default_language": "en", "consolidated_names": { "en": "Water Works", "es": "Obras Sanitarias", "fr": "Service des Eaux" }, "resolution_status": "unified" } }, { "input": { "record_type": "simplified synthetic app record", "language": "es", "parties": [ { "id": "party-2", "name": "Consultores de Software", "name_en": "Software Consultants" } ] }, "expected_output": { "canonical_id": "party-2", "default_language": "es", "consolidated_names": { "es": "Consultores de Software", "en": "Software Consultants" }, "resolution_status": "unified" } } ] ```

Entity consolidations must be verified by human reviewers before integration into official registries. Use mock external writes. Require human review before any real deployment.