# Organise Data As mentioned previously, FrontierNav uses a graph [data model](/editing-data/data-model.md). However, as graphs are extremely flexible and lack restrictions, it helps to view the data in a [relational model](https://en.wikipedia.org/wiki/Relational_model) like a spreadsheet. That is why [Data Tables](/editing-data/data-tables.md) are the primary interface for editing data. Initially, adding data is simple: You create tables and add columns to store values. However, as you introduce relationships between tables, you may end up at a point where you need to think about how you want the data to be organised so that everything is linked in an intuitive way for people to navigate. If you have worked with Relational Databases before, like [PostgreSQL](https://en.wikipedia.org/wiki/PostgreSQL) or [MySQL](https://en.wikipedia.org/wiki/MySQL), then this should be familiar. If not, it is easy to get started. Think of it like a puzzle that you need to untangle. This process is known as [normalisation](https://en.wikipedia.org/wiki/Database_normalization). It takes practice but like most things, the more you do it, the easier it gets. ## Useful Links * [Graph](https://en.wikipedia.org/wiki/Graph_\(abstract_data_type\)) on Wikipedia * [Graph Database](https://en.wikipedia.org/wiki/Graph_database) on Wikipedia * [Relational Model](https://en.wikipedia.org/wiki/Relational_model) on Wikipedia * [Database Normalisation](https://en.wikipedia.org/wiki/Database_normalization) on Wikipedia --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.frontiernav.net/editing-data/structuring-data.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.