4. Landmarks: The Node's the Thing (Even if it Never Was)

By Gene Stavrou
June 2022

The NODE construct describes an entity or a discrete object. The LANDMARK-labeled node, in particular, describes a physical entity: one that can be linked to a physical presence. Following the evolution of a public sculpture (e.g., its creation, relocation, alteration), means connecting that landmark to a place and to the entities that may have preceded and succeeded it, providing context. We generally use a node's EDGES to describe context, but the node itself has descriptors in the form of PROPERTIES.

A landmark's properties can include its physical location coordinates, identifier (name), alternate name, and start and end dates. Along with start and end are two properties that define those two dates: origin and fate. For a PERSON node, origin and fate would be the person's date of birth and death; a living person's fate would be blank. For landmarks, start and end must be placed in context. Because a landmark's instance may be moved, altered, destroyed, or rebuilt, its fate does not necessarily describe its destruction or even its end as a landmark.

What if the landmark never was?

To date, we've only considered landmarks that physically exist or have existed, allowing us to answer questions of the "what-became-of," "where-was," and "what-were-the-contemporaries-of" variety. But unexecuted plans can be historically significant as well. Noting landmarks that never existed can can sometimes answer the "what-might-have-been" questions that can place executed landmarks and land use in context. Robert Moses's proposal for a Brooklyn-Battery Bridge and its ultimate defeat helped define lower Manhattan's physical landscape and edit the city's political power structure. It also helps place Battery Park and the Brooklyn-Battery Tunnel in context. Origin for the Brooklyn-Battery Bridge's Landmark node would read "Proposed" and its fate would read "Not Built."

Recent Nodes

	Empire State Building 30-March
	Waldorf Hotel 26-March
	Cass Gilbert 25-March
	Henry Janeway Hardenbergh 25-March
	New York Life Building (1928) 24-March
	Augustus Saint-Gaudens 23-March
	Richard Morris Hunt 22-March
	Lenox Library 21-March
	Madison Square Garden (1968) 20-March
	Stanford White 19-March
	New York and Harlem Railroad Madison Square Depot 19-March
	Madison Square Garden (1925) 19-March
	Madison Square Garden (1879) 18-March
	Madison Square Garden (1890) 18-March

Recent Edges

30-March	Henry Janeway Hardenbergh architect_of Waldorf Hotel
25-March	Cass Gilbert architect_of New York Life Building (1928)
25-March	Madison Square Garden (1890) replaced_by New York Life Building (1928)
25-March	Madison Square Garden (1890) succeeded_by Madison Square Garden (1925)
24-March	Richard Morris Hunt architect_of Lenox Library
23-March	Stanford White architect_of Madison Square Garden (1890)

2. Landmarks Can Change Over Time

By Gene Stavrou
April 2022

Treebase's data structure is meant to model the real world with an eye toward generating insights and visualizations. The database itself is made up of two basic constructs. NODES represent people, places, things, and ideas. EDGES describe relationships between nodes. This month we'll be defining characteristics of the LANDMARK node type (used to describe buildings, natural landscape features, works of art, and other objects) and its relationships. A building and its architect, for example, have the relationship "[building name] designed_by [architect name]," where designed_by is the edge between the building and architect nodes.

Although a landmark can be built on a foundation or rooted to the ground, its context can change over time. The landmark node type and its related edges must be able to note that context. We'll use real-world scenarios as use cases to create the language for describing landmark nodes and relationships.

Succeeded vs Replaced

We'll start with a particularly historic New York City building: the second Madison Square Garden (MSG2), built in 1890 on the site of the first Madison Square Garden (MSG1). Image: The second Madison Square Garden. MSG2 was demolished in 1926 to make way for the new headquarters of The New York Life Insurance Company (NY Life HQ), which stands on the site today. MSG3 was built farther uptown.

In our database, we'll need to differentiate between a building's next incarnation (what succeeded it) and what took its place on its site (what replaced it). In shorthand, we'll write

[MSG1] succeeded_by [MSG2]
[MSG1] replaced_by [MSG2]
[MSG2] succeeded_by [MSG3]
[MSG2] replaced_by [NY Life HQ]

The previous NY Life Headquarters (The "Clock Tower" Building) still stands on 346 Broadway.

[NY Life Clock Tower] succeeded_by [NY Life HQ]

1. Building a History Database

By Gene Stavrou
March 2022

Atimeline is just about the simplest device available for presenting historical events over time. It's a list of related milestones organized within a timeframe—a kind of shorthand for communicating history. Image: A simple timeline is a list of related milestones.

A timeline's content can be contained within a simple information structure: one table with each row representing one event, and columns containing event name, description, and date. Image: A simple timeline's information structure. Events are curated to describe a particular aspect of history. A biographical timeline, for example, could include a person's major life events ("hatch, match, dispatch"). A war timeline might list lead-up events, declarations of war, battles and outcomes, and treaty signing. A corporate timeline might include the founder's big idea; the company's formation, mergers, acquisitions, divestitures; leadership changes; product introductions, and other business milestones over time.

Such simple timelines are curated to answer two types of questions: "when did notable events happen?" and "what is the temporal relationship between those events?" They can also be used to make a statement; the company timeline's message is often "you can trust us; we've been around for a while." Adding an aspect or two helps in answering more complex questions. The company aspect paired with a geopolitical or economic aspect, for example, might reveal that the company thrived during wartime or benefitted from housing booms. The message of a war timeline might take on a different tone when paired with information that clarifies the war's human toll over time. Image: Paired timeline aspects can display correlation.

While pairing timelines can display correlation (these two events happened at the same time), a more complex information structure is required to display causality (this event directly affected the outcome of another). History is multifaceted and discovering reasonable causal connections between seemingly disconnected elements is what gets the mind buzzing. Exploring history is an ongoing process of linking nodes via relationships and there is wonder in traversing such a model and adding context and connections as you learn. Discovering a missing piece can be like finding a portal at what was thought to be a dead end.

The Treebase graph database is intended to map history connections and make discovering relationships easier.

Nodes and Edges

Information will be organized into a collection of nodes (or vertices) and edges (relationships). Image: A graph database focuses on nodes and relationships. Nodes can be thought of as nouns in that they represent people, places, things, and ideas. Edges are like verbs, and they connect two nodes by describing their relationship. Storing historical information in this "graph" format makes it available for analysis and for communication through a variety of formats—from the simple timeline to the voice user interface. We'll start by building the database's structure and rules.

Getting Started: Landmarks

Treebase will focus initially on New York City history as a theme for developing the database rules. We'll start by developing and populating the landmark node type, which includes physical features, such as sculpture, shoreline, and streets, as well as notable buildings. Later, these nodes will be connected to other nodes (people, ideas) as well as mapping coordinates, images, and other relationships via edges. Track the ongoing addition of nodes and relationships on this page.

Dakota Apartments, Exterior Railing Detail, 1884