Choose a workflow
How to use this tool Click to expand
User Guide (one page) - Open in new tab; use Print -> Save as PDF for a PDF copy.
1. Upload Outcomes source, Translation table, myWSU, and optional campus-family rules file (JSON/text/CSV/Excel) to prefill parent keys for campus variants.
2. Match Options: Pick Translation input/output columns. Default validation mode is Key + name comparison (switch to Key only if needed).
3. Name comparison (if used): Pick Outcomes and myWSU name columns; set threshold (default 0.8) and ambiguity gap (0.03).
4. Select Columns, Keys, and Roles: Pick included columns; mark key columns for Outcomes and myWSU; optionally map roles (School, City, State, Country). Include City/State for high-confidence matching.
5. Click Validate Mappings, then use Bulk edit before export for context-aware edits (quick family chips, top/bottom pagination, Apply Scope). 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 review and download output. In the editor panel, upload Prior Validate Workbook and/or Review Session JSON to resume work.
6. Click Download Full Report.
7. The Final_Translation_Table has auto-matched row pairs (Valid + High_Confidence_Match) in normal/all-row review scope. In Missing mappings only scope, Final_Translation_Table is scoped to missing-mapping review output. You must use Review_Workbench to set decisions for rows needing review. Set Decision (Keep As-Is, Use Suggestion, Allow One-to-Many, Ignore) and set Reason Code for risky decisions (Use Suggestion with manual key, Allow One-to-Many, Keep As-Is on Duplicate_Target rows). If you use Use Suggestion, either Suggested Key (from C1/C2/C3) or Manual_Suggested_Key must be filled, and Update Side must be Input/Output/Both. For intentional many-to-one (for example, Texas A&M campuses to one parent), use Keep As-Is on Duplicate_Target rows. Use Translation_Key_Updates (What changed) to verify all key changes before publish.
8. Excel requires 365 or 2021+. Before updating the Outcomes Translation Table: verify changes in Translation_Key_Updates (What changed) -> copy Final_Translation_Table -> paste as values only into a new sheet -> sort and double-check -> only then update. Publish only after QA_Checks_Validate blocking checks pass (including risky decisions without reason code and duplicate checks).
1. Upload Outcomes source and myWSU
2. Match method: Key columns or Name columns (key optional in name mode)
3. Name comparison (if used): Pick name columns; set threshold and ambiguity gap
4. Select Columns, Keys, and Roles: Pick included columns; optionally map roles. Key columns required only for key matching
5. Click Generate Translation Table -> download Excel
6. See Review_Instructions_Create sheet in the 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 (e.g., name, state, country)
4. Click Generate Join Preview -> download Excel
5. Review the joined table to verify Outcomes and myWSU data align correctly before publish
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.
Outcomes Source
Excel or CSV
Outcomes Translation Table
Excel or CSV
myWSU Tables
Excel or CSV
Campus-Family Rules
Optional - prefill parent keys
JSON, text, CSV, or Excel
Analyzing mappings...
Total Mappings
0
Valid Mappings
0
0%
Errors Found
0
0%
Errors exclude one-to-many groupings
Data Quality
0%
Overall Score
Error Distribution
Mapping Logic Preview
| # | Source key | Target key | Classification | Mapping logic |
|---|
Error Reporting Logic
Not found = Translate key value exists, but is not present in the source key list (Outcomes or myWSU). Existing translate tables are assumed to have complete key pairs.
Translate input key value exists but is not a valid Outcomes key (data entry error, stale key, or wrong key column selection).
Translate output key value exists but is not a valid myWSU key (data entry error, stale key, or wrong key column selection).
Output key is missing in myWSU, but one high-confidence replacement key was found using name/location evidence.
Multiple different source keys map to the same target key, merging multiple Outcomes records into one myWSU record.
A single source key maps to multiple target keys, creating conflicting mappings.
Names in Outcomes Source don't match names in myWSU (below the similarity threshold). Review these mappings to confirm they are correct.
Names are close to multiple candidates within the ambiguity gap. Tighten the gap to flag more ambiguous cases, or raise the threshold to be stricter overall.
High-confidence Outcomes-to-myWSU name/location pairs where the translate input and/or output is missing. Use this sheet to add likely missing mappings.
Key Point: The app validates your Translation Table as the integration map. System check catches blank keys first; validation then flags key lookup and mapping-quality errors. Fix these errors in your source system to ensure reliable data sync between Outcomes and myWSU.
Matching Rules + Examples
Abbreviations/aliases: Common short forms are expanded (e.g., U -> University, CC -> Community College, Cal State -> California State).
Location evidence: City/state/country fields, city-in-name, and parenthetical or hyphen suffix location tokens are used to confirm matches.
High-confidence override: If location rules confirm a match, it can be accepted even when similarity is below threshold.
Examples from this run will appear after validation.