ClipPrepare a small CSV or TSV
Use separate columns for the lookup code, the value you want to store, and helpful details. A sports roster might contain number, display name, team, season, and role. For a documentary, the code could be a short speaker identifier. Keep an unchanged copy of the source roster.
Map the columns
Import the file as a lookup or code-replacement table. Choose the code column and the name/value column, then include detail columns that distinguish otherwise ambiguous entries. Inspect several rows before accepting the map, including duplicate codes and missing values.
The lookup import is not a general clip-metadata importer. A DAM export containing one row per video cannot be treated as a roster merely because both files use CSV.
Bind the lookup to the intended field
Select the palette key or layer that should invoke the lookup and target the subject-related field. Test the interaction on one clip, checking both the displayed value and the project cast. Replace a roster table in place only after confirming that the new columns preserve the expected code and value meanings.
Review the identity evidence
Two athletes can share a number across teams, seasons, or roles. A visible number is a useful clue, while a face crop, appearance, and project context provide other evidence. A helmet can hide the face entirely. Confirm an association only when the combined evidence supports it, and keep uncertain appearances unresolved.
Check a second editor's lookup
Ask someone else to use the palette against the same sample. They should see enough detail to choose the correct record without relying on your memory. Keep the source roster and project configuration together so the next person can understand how names entered the log.