Overview
TalentID ingests Alpha Timing event files into an S3 bucket, with one subdirectory (prefix) per hub. The timing laptop uploads each hub’s files under that hub’s prefix. Following a refactor, supporting a new hub now only requires adding a single entry to the_supportedRegions dictionary in the AdminController. No other code change is needed.
Prerequisites
- Access to the TalentID API repository.
- The new hub code (region code, uppercase, for example
DE). See the naming convention.
Adding the Region Mapping
Open AdminController
In the TalentID API repository, open
TalentId.API.Core/Controllers/AdminController.cs.Add the new hub to the dictionary
Add an entry to the The key is the hub code used in the import route, and the value is the S3 prefix files are uploaded under (
_supportedRegions dictionary, mapping the hub code to its S3 subdirectory in the form AlphaTiming-<CODE>:fileKey = "{subdir}/{fileName}").UK is the only exception, mapping to AlphaTiming with no suffix. Every other hub follows the AlphaTiming-<CODE> convention. Region matching is case insensitive, but the prefix value is used as written, so keep the casing correct.S3 Folder
You do not need to create the hub’s folder in the S3 bucket manually. The timing laptop creates it automatically when it pushes its first file under the hub key prefix.There is no problem if you do create the folder yourself, just make sure it is correct and matches the
AlphaTiming-<CODE> prefix exactly.