Story: ORE import wizard

Table of Contents

This page documents a story in Sprint 14. It captures the goal, current status, acceptance criteria, and the tasks that compose it.

Goal

Deliver a comprehensive ORE Import Wizard that scans entire ORE directory structures and brings their portfolios + books + trades into ORE Studio.

Status

Field Value
State DONE
Parent sprint Sprint 14
Now Completed 2026-03-01.
Waiting on None.
Next None.
Last touched 2026-03-01

Continued from: Trade import mapping analysis (sprint 13) — the analysis from sprint 13 informed a larger directory-scanning wizard shape than the single-file dialog originally planned.

Continued in: Fix ORE import bugs (sprint 15) — real-data import surfaced the currency-type, status, and activity-type bugs cleaned up there.

Acceptance

  • Seven-page wizard live, accessible from File menu + Portfolio Explorer toolbar.
  • Directory scan + hierarchy build + trade import work end-to-end.
  • Re-import modes (add-only / new temporal version) supported.

Tasks

Task State Start End Description
Add ORE Import Wizard DONE 2026-05-20 2026-03-01 Seven-page QWizard: directory scan, hierarchy build, trade import. ore_directory_scanner classifies files; ore_hierarchy_builder constructs portfolio + book hierarchies with naming + dedup; ore_import_planner generates the import plan; asynchronous scan; batched trade imports with live progress; accessible from File menu + Portfolio Explorer toolbar.

Decisions

Wizard, not a single-file dialog
the analysis from sprint 13 surfaced the directory-scan shape; the wizard fits that.
Asynchronous scan + batched import with progress
avoids blocking the UI on large directory trees.

Out of scope

  • FpML XML export (separate workstream).
  • Counterparty auto-resolution beyond name matching.

See also

Emacs 29.1 (Org mode 9.6.6)