SHOREX · DATA ADAPTOR

Wire sources, map data, see how it flows

SHOREX · DATA ADAPTOR

The shorex toolset, and the shape it all runs on

Jump into any tool below, or read the lifecycle: how a season nests down to a single bus, colored by phase — the structure every downstream tool inherits.

Stages as nested object boxes with slim close-in and post-recon sections, colored by phase; tool icons pinned to the stages each tool reaches STAGE 1 · SEASON Season the planning horizon STAGE 2 · CLOSE-IN STAGE 3 · VOYAGE Voyage STAGE 6 · PR VOYAGE STAGE 4 · CLOSE-IN STAGE 5 · TOUR DAY Tour Day STAGE 6 · PR TOUR DEPARTURE Departure(s) bus-level dispatch units STAGE 7 · POST-CRUISE Post-Recon final settlement After all tour and voyage actuals are captured (slims to the left), final GL postings, credits, and loyalty close out the books. PHASE Pre-Cruise Operational Post-Cruise slim sections = transitional close-in (Stage 2/4) and per-level post-recon (Stage 6)
B1
ADAPTOR · connections & the cell matrix

Configure connections and the cell matrix

Source connections (B1A) feed the model; the matrix (B1B) wires each track × stage cell to a source. The canonical model and its field mappings live on the Canonical Model tab.

B1A · CONNECTIONS Source systems wired up for this tenant · health, role, contributed entities

Source systems shown here are for tenant solstice. Full adapter operations — reconciliation queue, dead-letter, canonical entity browser — live in the standalone shorex-adaptor/ page.

B1B · CELL MAPPING Click a cell to inspect; matrix wires each track × stage to a source connection from 01A
Data sources
Global defaults · all ships, all seasons
Dispatch Tour Day
FIDELITY LADDER reaches Operating
SOURCES (PRIORITY ORDER)
C1
CANONICAL MODEL · the schema & how sources fill it

The canonical model and its field mappings

The entities the adaptor produces (C1A) and the source-field-to-canonical-field mapping behind each one (C1B).

C1A · CANONICAL ENTITIES The schema the adaptor produces · each entity has one authoritative source, with others contributing fields
C1B · FIELD MAPPING Each (source × entity) pair has its own mapping · expand to see the field table
TARGET APP
VALUES
PREVIEW

This is the operations view — find where your data lives two ways: Check your data need answers “where should this come from?”, and Operational flow walks one tour, then the live flow. The structural map — season down to a single bus — now lives on the landing page.

CHECK YOUR DATA NEED · point in time × part of ops

Where should this data come from?

Pick the part of the process in focus — get the source systems to use, and why. The everyday tool for answering “where’s my data?”

1 What detail level?
2 What are you working on?
OPERATIONAL FLOW · one tour, then the live flow

The lifecycle two ways — follow one tour, then explore the live flow

First the linear story of a single excursion from catalog to settlement; then the interactive operational diagram — click any node to see which systems feed it and how active each track is.

STORYBOARD One excursion, catalog → settlement · phase color · how often each step changes
1 season many voyages many tour days departures bus-level dispatch
FLOW DIAGRAM How one excursion fans out, Season → Post-Recon · click a node to drill in