liveBook · Manning

Map

As explained in Investing for Programmers

A lookup table is a structured mapping that associates source identifiers or attributes with corresponding standardized values.

A dictionary is a key–value structure for associating an identifier with metadata or a standardized value. In an asset monitor, a lookup table maps broker tickers to portfolio, asset type, and platform-specific ticker names, keeping merged data consistent. section 6.4

Practical uses include:

  • Mapping exceptional identifiers, such as a broker ticker to its Yahoo Finance or Google Finance equivalent. section 6.4
  • Representing structured API payloads with properties, formatting, and content for Notion pages. section 9.2.2

Asset identifier lookup

A lookup record can retain `BRK.B` as the broker ticker and store `BRK-B` for Yahoo Finance. Missing platform-specific values fall back to the broker ticker before the metadata is merged into the positions DataFrame.

How Investing for Programmers covers it

How deep it goes
Explains mapping roles and demonstrates schemas, DataFrame merging, fallback values, and nested API payloads without discussing dictionary internals.
Examples
Demonstrates ticker mappings, asset metadata records, Notion title properties, page blocks, and chunked content payloads.
What it assumes
Assumes basic identifiers, tabular data, and API concepts while demonstrating the required mapping structures through concrete schemas.
What you can do after
Apply via Python to organize metadata, merge lookup information, and send structured content through an API.
How it connects
Connects dictionaries with lookup tables, pandas DataFrames, SQLite, JSON, REST APIs, and metadata.

Also explained in

Compare how 42 books explain Map →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Investing for Programmers. The section links point to the parts of the book it draws on.