Story: Trade import mapping analysis
Table of Contents
This page documents a story in Sprint 13. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Document the mapping requirements between ORE portfolio XML and the ORES model; design the approach for resolving string-based ORE references.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 13 |
| Now | Completed 2026-02-25. |
| Waiting on | None. |
| Next | None. |
| Last touched | 2026-02-25 |
Continued in: ORE import wizard (sprint 14) — the analysis here surfaced that a directory-scanning wizard was the right shape; the wizard implements that.
Acceptance
- Mapping requirements documented.
- Counterparty / book / portfolio resolution decisions captured.
- Mapping-dialog design ready for implementation.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Analyse ORE trade import mapping requirements | DONE | 2026-05-20 | 2026-02-25 | Document how ORE XML trade references (CounterParty string, NettingSetId, PortfolioIds) map to ORES UUID-keyed entities. Decide: auto-create vs mapping dialog vs config file for counterparties; how to assign books (no ORE equivalent); whether to map PortfolioIds or ignore; batch import configurations. |
Decisions
- Mapping dialog over config file
- tighter feedback loop for evaluation users; config can come later.
Out of scope
- Implementation (sibling story; postponed).
See also
- Trade import mapping dialog (Qt UI) — the implementation story (BACKLOG).