Maintain reusable Cases across benchmarks
Reuse project Cases while keeping benchmark membership and frozen assessment populations distinct.
Prerequisites
Access to the Project Case and each benchmark you intend to change.
Steps
- Inspect the canonical input, materials, and classifications before selecting a Case for another benchmark.
- Use the benchmark’s dataset selection workflow to include the relevant Case. Check why it belongs in that benchmark’s intended population.
- Review representation and applicable standards for the receiving benchmark.
- Create a new Snapshot when the changed population needs to become a fixed assessment boundary. Compare against the intended Benchmark Version.
Object and state changes
The Project owns the reusable Case. Each benchmark owns its selected membership; existing Snapshots and accepted Runs retain their recorded inputs.
Success criteria
The same useful situation can support several benchmarks without hiding which population each result measured.
Common failure modes
Assuming Case existence implies dataset membership; treating an old Snapshot as if it contained a later edit.