Network Literacy in Practice

What Is a Graph Database?

A graph database stores information as nodes and relationships — the same building blocks you learn about in Network Literacy. The technology behind this competition is itself a network.

Nodes, Edges, Properties

In the Network Literacy framework, you learn that networks have nodes (things) and edges (connections between things). A graph database works exactly the same way. In Neo4j — the graph database this competition uses — data has three building blocks:

Nodes

The things. An entry, a school, a concept, a network topic. Each node has a label that tells you what kind of thing it is.

Relationships

The connections. "Submitted from," "demonstrates," "in domain." Each relationship has a type and a direction.

Properties

The details. A school's name and location. An entry's description and grade. Properties are the data attached to nodes and relationships.

This maps directly to Concept 2 of Network Literacy: networks have parts. The graph database simply makes those parts explicit and queryable.

How This Competition Uses Neo4j

When you submit your entry to the NetSciEd Challenge, it becomes a node in our graph database hosted on Neo4j AuraDB. Here's what happens:

Your entry becomes an (:Entry) node with your title, description, and answers.
Your school becomes a (:School) node with its name, URL, and location on the map.
The Network Literacy concepts you demonstrated are (:Concept) nodes, and your entry connects to them.
The connections between all of these — which school submitted which entry, which concepts each entry demonstrates, which entries share a domain — are all relationships in the graph.

The Live Graph page lets you see this structure directly. You can explore entries by concept, by domain, by school, or browse the entire network of networks.

Why Not a Spreadsheet?

A spreadsheet stores data in rows and columns. It can tell you that Entry #47 is from Lincoln High School. But it cannot easily show you that Lincoln High School submitted three entries across two domains, both of which share structural properties with entries from a school in Brazil.

A graph database makes these connections first-class citizens — they are as real and as queryable as the data itself. When your data is fundamentally about relationships, a graph database is the natural tool.

And that's the point: the NetSciEd Challenge is fundamentally about relationships. Between nodes and edges. Between students and networks. Between schools and concepts. The graph database doesn't just store the competition data — it embodies the Network Literacy framework.

A Sample Query

Here's what a query looks like in Cypher, Neo4j's query language. This finds all entries that demonstrate Concept 2 (Nodes & Edges) and were submitted by schools in the same country:

MATCH (e:Entry)-[:DEMONSTRATES]->(c:Concept {name: "Nodes and Edges"}), (e)-[:SUBMITTED_FROM]->(s:School) RETURN e.title, s.name, s.country ORDER BY s.country

Notice how the query reads almost like English: "Find entries that demonstrate the 'Nodes and Edges' concept, and the schools they were submitted from." The pattern-matching syntax mirrors the way you think about networks.

See it in action

Explore the live graph of competition entries, or submit your own and become part of the network.

Explore the Graph Submit Entry →