Validate Translation Tables - User Guide

1. Upload Outcomes source, Translation table, myWSU, and optional campus-family JSON rules to prefill parent keys for campus variants.

2. Match Options -> pick key columns (Translation input/output), validation mode (Key only or Key + name; default is Key + name).

3. Name comparison (if used): pick Outcomes/myWSU name columns, threshold (default 0.8), ambiguity gap (0.03).

4. Select Columns, Keys, and Roles -> pick included columns, key columns, optional role mapping (School, City, State, Country). Include City/State for high-confidence matching.

5. Validate Mappings -> review cards -> optional Bulk edit before export (context grid + suggestion dropdown + reason code + quick family chips + synced top/bottom pagination controls). The bulk-edit button is a one-time opener per run; after first click the editor stays available for that run and re-opens on re-validate, and Start Over resets it. Use Review Scope (`All review rows`, `Uploaded Translate rows only`, `Missing mappings only`) to control both in-app rows and download scope. Upload Prior Validate Workbook and/or Review Session JSON in the editor panel to resume prior work. For duplicate/one-to-many rows, suggestions are capped to top 5 location-valid matches. Optional Save session/Load session -> Download Full Report.

The Final_Translation_Table includes both:

• Auto-matched rows (Valid and High_Confidence_Match).
• Rows you approve in Review_Workbench (errors, mismatches, duplicates, and missing mappings).

You must use Review_Workbench to decide which review rows are copied into the final table.

1. Review_Workbench (main decision sheet; sortable/filterable). C1/C2/C3 columns show candidate options inline (Key: Name - City, State, Country | Score); enter C1, C2, or C3 in Selected Candidate ID to pick.

• Keep As-Is: copy current keys to final. Row still counts toward duplicate-key QA; use when the row does not create a duplicate.
• Use Suggestion: copy with effective key (Manual_Suggested_Key if you enter one, otherwise Suggested_Key from candidate selection). When candidates are blank, enter a valid myWSU key in Manual_Suggested_Key.
• Allow One-to-Many: copy as approved exception. Row is excluded from duplicate-key QA; use when you intentionally allow duplicate keys (e.g., many-to-one mapping).
• Ignore: do not copy to final.
• Reason Code: required for risky decisions: Use Suggestion with manual key, Allow One-to-Many, and Keep As-Is on Duplicate_Target rows.

Intentional many-to-one: Duplicate_Target + Keep As-Is is exempt from duplicate output QA (B14), for example Texas A&M campuses to one parent key. Duplicate input (B13) and duplicate-pair (B15) checks still block.

Unhide Candidate_Pool/Candidate_Reference: Right-click tab bar -> Unhide -> select sheet. Use when you need to inspect candidate details.

2. Final_Translation_Table: auto-matched rows + approved review rows (not sortable directly).

3. Translation_Key_Updates (What changed): only key pairs that differ from current. Use this to verify all changes before publish.

4. QA_Checks_Validate: all blocking checks must pass before publish.

Scope behavior: `Uploaded Translate rows only` excludes Missing_Mappings from review/export. `Missing mappings only` keeps only Missing_Mapping review rows, scopes Final_Translation_Table to missing-mapping review output, and suppresses non-missing diagnostic tabs in that workbook.

Blocking QA highlights: B10 risky decisions without reason code, B13 duplicate input keys, B14 duplicate output keys (with intentional many-to-one exemption), B15 duplicate pairs.

Final step before updating Outcomes Translation Table:

1. Copy Final_Translation_Table.
2. Paste as values only into a new sheet.
3. Sort and double-check the pasted values.
4. Only then update the Outcomes Translation Table.

1. Upload Outcomes and myWSU. 2. Match method: key or name (key optional in name mode). 3. Select columns -> include columns, optional roles. 4. Generate Translation Table -> download Excel. See Review_Instructions_Create in workbook.

1. Upload Outcomes source, Translation table, and myWSU. 2. Key selection -> pick Outcomes key, Translation input/output columns, and myWSU key. 3. Select columns -> pick which Outcomes and myWSU columns to include. 4. Generate Join Preview -> download Excel. Review the joined table to verify Outcomes and myWSU data align correctly before publish.

Review by exception. Check QA before publish. Use Suggestion: verify Suggested Key/School/City/State/Country first. Re-import: upload prior Validate workbook to resume; after download, summary shows applied, conflicts, new rows, orphaned. Privacy: your uploaded files are processed locally in your browser and are not uploaded by this app; the page loads JavaScript libraries from public CDNs.