# Core concepts

> Configurations, collections, tables, fields, projects, locations, records, depth links and flags.

Log captures the same structured data as the rest of GIMLabs. A handful of
concepts explain everything you see in the app.

## Configuration

A **configuration** is the profile that defines the tables, fields, units, lists
and collections your company's data uses. It is what makes the forms in Log match
how your team works. Administrators manage configurations in
[Product OS](https://os.gimlabs.io); in Log it is chosen when a project is
created.

## Collection

A **collection** is a way of working at a location - for example *trial pitting*,
*monitoring* or *window sampling*. A location can use one or more collections, and
the tables and fields you see change to match the collection you are working in.

## Table

A **table** is a named block of data - *Location Details*, *Samples*, *In-situ
Tests*, and so on. The table menu lists each table and how many records it holds.
Tables can be **nested**, too: some records open a further table of their own -
see [Child tables and depth links](/log/logging-data/child-tables).

## Field (column)

A **field** is a single value on a record - *Depth*, *Sample reference*, *SPT N
value*, and so on. Each field has a **type** (text, number, list, date and more)
that decides how you enter it. Fields can be **required**, can show or hide based
on other answers, and can carry defaults. See
[Fields and entry helpers](/log/logging-data/fields).

## Project

A **project** is the site or investigation you are working on. You pick a project
first, and everything after - locations, records - belongs to it.

## Location

A **location** is a single point of investigation within a project - a borehole,
trial pit or monitoring point. A location is **Open** while you work on it and
**Closed** once you mark it complete.

## Record

A **record** is one row of captured data - one sample, one stratum, one test. You
add, edit and flag records in the grid, and they sync to the cloud.

## Depth link

A **depth link** pulls values from a depth-related table onto the record you are
entering - for example showing the stratum description for a sample's depth. See
[Child tables and depth links](/log/logging-data/child-tables).

## Flag

A **flag** marks a record for review - a description you are unsure of, say - with
a note, a **priority** and a **status**. See
[Flags](/log/logging-data/flags).