Four areas of the Market data menu cover the service
Table of Contents
1. Summary
The Market data menu holds four areas. The catalogue shows what providers offer. Subscriptions and routes show what a party takes and from which source. Usage and cost show what a party used and what it costs. The simulator holds the authoring tools. The first three are the same for live and simulated sources.
2. Detail
| Area | Shows | Who |
|---|---|---|
| Catalogue | Providers, their sources with kind badges, vendor instruments, mappings, minted ids | Everyone reads. The system administrator writes. |
| Subscriptions | A party's subscriptions, rights, and the route of each | Party administrator |
| Usage and cost | Demand, delivery, bills and shadow bills, by provider and period | Party administrator reads own. System reads all. |
| Simulator | Collections, folders, generators, preview, fault injection | Simulator author |
2.1. Rules for the screens
- A source's kind is a badge and a filter, and it changes no other behaviour. See No code path may behave differently because a source is simulated.
- A source screen shows the adapter state, the demand set and the rejected ids. See The adapter lifecycle.
- A route change goes through a dialog that asks for a reason.
- The simulator area is the only one with authoring controls.
2.2. Standards
All screens follow the record screen standard and the feed screen standard. The simulator screens are described in The market simulator screens.
3. See also
- Market Data Architecture — the structure note that orders this cluster.
- A party takes a provider's feeds through a subscription — completes: the data behind the second area.
- Usage is recorded as events and priced later — completes: the data behind the third area.