Birth Year Truncation in .CSV export

[dradspinner]

Bug: CSV Export Truncates Birth Years (1986 → 86)

🐛 Summary

CSV export truncates 4-digit birth years to 2-digit using modulo 100 operation, causing data loss and century ambiguity.

Example: Runner born in 1986 exports as "86" in CSV

🔍 Bug Location

File: code/oImportExport.cpp
Line: 176

📝 Current Code (Broken)

row[OEbirth] = conv_is(di.getInt("BirthYear") % 100);

✅ Proposed Fix

row[OEbirth] = conv_is(di.getInt("BirthYear"));

Change: Simply remove the % 100 modulo operation.

🧪 Test Case

1. Create runner with birth year 1986
2. Export to CSV
3. Current Result: CSV shows 86
4. Expected Result: CSV shows 1986

💥 Impact

• Data Loss: Century information is permanently lost in CSV exports
• Ambiguity: Cannot distinguish between 1986 and 2086 (both become "86")
• Import Problems: Other systems receiving the CSV cannot reliably determine actual birth years
• Age Calculations: Incorrect age calculations due to missing century

📊 Real-World Examples

• Runner born 1975 → exports as 75 (could be 1975 or 2075)
• Runner born 2008 → exports as 8 (could be 1908, 2008, or 2108)
• Runner born 1999 → exports as 99 (could be 1899, 1999, or 2099)

🎯 Why This Fix is Safe

• Backward Compatible: Systems expecting 4-digit years will work correctly
• Forward Compatible: Future years beyond 2099 will export properly
• Data Preservation: No information is lost
• One Line Change: Minimal risk of introducing new bugs

⚡ Priority: HIGH

This is a simple one-line fix that resolves significant data loss. The fix is:

• ✅ Easy to implement
• ✅ Low risk
• ✅ High impact
• ✅ Affects all CSV exports

📁 Files to Change

• code/oImportExport.cpp (Line 176 only)

---

Bug discovered through practical orienteering event management and confirmed via source code analysis.