# \#schema

**URL:** https://the.fmsoup.org/tag/schema/546.md

[Latest](https://the.fmsoup.org/latest.md) · [Categories](https://the.fmsoup.org/categories.md) · [Tags](https://the.fmsoup.org/tags.md)

---

## [How to structure this Database?](https://the.fmsoup.org/t/how-to-structure-this-database/3366)

<div class="topic-metadata">

**Author:** [@JasonMark](https://the.fmsoup.org/u/JasonMark)\
**Replies:** 13\
**Last updated:** [February 8, 2023, 8:07pm UTC](https://the.fmsoup.org/t/how-to-structure-this-database/3366 "2023-02-08T20:07:57Z")

</div>

OK I feel like this should be easy but I have a little bit of COVID brain, can someone please help me figure out how to structure this database. GOAL: I need to track student progress in a class in a portal like this: …

---

## [Layout Context](https://the.fmsoup.org/t/layout-context/2445)

<div class="topic-metadata">

**Author:** [@steverichter](https://the.fmsoup.org/u/steverichter)\
**Replies:** 5\
**Last updated:** [August 31, 2021, 8:04pm UTC](https://the.fmsoup.org/t/layout-context/2445 "2021-08-31T20:04:49Z")

</div>

Given a standard customer-invoice-line\_item schema, anchor buoy, and three TOGs, which TO would you use to create a layout and portal to view line items associated with a specific customer?