[Feature]: DataCollector should collect unique_id by default
- Dominant language
- Python
- Stars
- 42
- Forks
- 18
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
### 🤔 Problem Description
When collecting agent reporters (e.g., wealth), the current implementation only collects the values of the requested column but not the unique agent IDs. This makes it difficult to trace values back to the corresponding agent, especially when debugging, analyzing distributions, or joining with other data sources.
Without unique IDs, it’s unclear which agent each value belongs to, leading to ambiguity and potential data misalignment.
### 💡 Proposed Solution
_No response_
### 🔄 Alternatives Considered
_No response_
### ➕ Additional Context
_No response_
Contributor guide
Research direction
Start by locating the DataCollector entry point and the agent reporter collection path. Verify how requested columns are currently gathered, then define done as collecting each agent's unique_id by default alongside the requested values and add or update coverage for that behavior if tests are present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100