Club, Team and Coaching History
Preserve the team context
A club can have several teams. Club-wide history is useful, but it is not the same as the record of its first team, reserve team or a youth side.
Use the dedicated history menu items with their club and, where offered, team selection. Test both the saved default and the public selection. Historical projects and currently active teams should not be treated as interchangeable.
Club people directory
The people view can start with a configured team or the club-wide scope. Memberships, appearances and statistics follow the chosen team. A person who served several of the club's teams is not simply duplicated in the aggregate directory to manufacture a larger total.
When a familiar person is missing, inspect the recorded memberships and their validity, then the publication/access chain. A global person-to-club link does not replace every competition membership.
Coaching and staff history
The staff-history page uses the recorded role assignments and periods. Its menu options can control played/won/drawn/lost, score and period columns, and the first/last match links. These are presentation choices, not manual edits to a coach's sporting record.
First and last match links follow chronological data, not the numeric ID of an imported match. Select the intended team when the same person worked with multiple squads.
Rivalries
RC2 distinguishes exact team-pair encounters from optional club totals. Home and away records and competition breakdowns must retain the selected context. Different teams belonging to the same opponent club are not automatically the same sporting opponent.
Date presentation can be compact, ISO or localised using the offered menu option. Changing it does not change a stored match date.
Names and media over time
Clubs and teams can retain historical names and logos. Use those history records rather than globally renaming an organisation solely to make one old season look right. Do not merge two organisations merely because they share a village, venue or similar name.
Verify the public output
Test guest access, team selection, season/project context, pagination and first/last match links. Hidden parents, opponents or stages should not become visible through a history aggregate. Use Troubleshooting when a record is correctly stored but absent from the public view.
