Get AI summaries of any video or article — Sign up free
How to put a College Reading Workflow into Tana thumbnail

How to put a College Reading Workflow into Tana

CortexFutura Tools·
5 min read

Based on CortexFutura Tools's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Create a “Concentrations” table where each concentration links to an advisor via an instance of a “Professor” tag.

Briefing

A practical way to manage college reading and coursework in Tana hinges on modeling everything as connected records—concentrations → classes → assignments, plus a separate book list—then using saved queries to keep each view automatically updated. Instead of manually tracking deadlines and reading lists, the workflow builds tables that filter themselves based on relationships between items, so “Psychology 101” can instantly show only its relevant classes, assignments, and readings.

The setup starts from a clean workspace and defines a “Concentrations” table. Each concentration gets an “advisor” field implemented as an instance of a “Professor” tag, allowing multiple professors to be linked to different concentrations. With concentrations stored as tagged items, a query can render a table of concentrations and advisors. This table becomes a navigational anchor in the sidebar, so the user always lands on the same structured overview.

Next comes “Classes,” organized under each concentration. Each class record includes fields like professor, required/recommended reading relationships, semester (using fixed options such as 2020 Spring, 2021 Fall, etc.), hours, and grade (as a number). The key modeling move is linking each class back to its concentration via an instance reference. That relationship enables filtered queries: the “Classes” table can be configured to show only classes belonging to a selected concentration (for example, only the writing-related courses under a specific concentration), rather than a complete list of every class ever created.

Assignments sit one level deeper. Each assignment is linked to a class through an instance-of-class field, and includes a due date plus a “complete” checkbox. Once assignments are connected to classes, a query can generate a “Course assignments” table that dynamically updates as new assignments are added. The workflow also supports quick filtering—such as showing only incomplete assignments (complete is not checked) or only completed ones—so the workload view stays focused.

Finally, the reading workflow uses a “Books” table built around tags and structured metadata. Each book includes a reading status (fixed options like “to read,” “finished,” and whether it’s required or recommended), author (as an author instance), genres, book format, and publication date. Books are then pulled into a “Book list” view via a query that selects all book items. Because the reading status and metadata are standardized fields, the list can be narrowed further with additional search filters.

Throughout, the workflow’s power comes from light modeling: once relationships are set correctly (concentration → class → assignment, and books as tagged records), Tana’s saved tables act like live dashboards. The result is a college system where selecting a concentration automatically surfaces the right classes, deadlines, and reading materials—without re-entering the same information in multiple places.

Cornell Notes

The workflow builds a college system in Tana by modeling relationships between concentrations, classes, assignments, and books, then using saved queries to generate automatically updating tables. Concentrations store an advisor linked to professor instances. Classes link back to concentrations and include semester, professor, hours, and grade, enabling filtered class lists per concentration. Assignments link to classes and track due dates and completion via a checkbox, letting course assignment tables update instantly and filter to incomplete or completed work. Books are stored as tagged records with reading status, author, genres, format, and publication date, then pulled into a book list via a query. This matters because it turns manual tracking into dynamic dashboards with minimal duplication.

How does the workflow structure concentrations so they can drive everything else?

It creates a “Concentrations” table where each concentration item has a “advisor” field. The advisor field is configured as an instance of a “Professor” tag, so each concentration can select the correct professor (e.g., Damon for Criminal Justice, Heather Steinman for psychology). A query over items tagged “concentration” renders a table of concentrations and their advisors, and that table is pinned in the sidebar for quick navigation.

Why link classes to concentrations instead of just listing all classes?

A class query over all items tagged “class” would return every class in the workspace. To avoid that, each class includes a field that references an instance of a concentration. Then the “Classes” table can be configured to show only classes where the concentration matches the selected concentration instance. This makes “Psychology 101 …” appear only under the psychology concentration, while writing-related classes appear under the writing concentration.

What fields make assignments usable as a live “to-do” list?

Assignments are modeled with a link to a specific class (instance-of-class), a due date, and a “complete” checkbox. Once assignments are connected to classes, a query can display “course assignments” as a table that updates dynamically. Filtering becomes simple: show only items where complete is not checked for an active workload view, or show only checked items for what’s already done.

How are books represented so reading status and metadata stay consistent?

Books are stored in a “Books” table with fields like reading status (fixed options such as to read/finished and required vs recommended), author (as an author instance), genres, book format, and publication date. The reading status and other fields are standardized so the “Book list” query can reliably pull all book items and then narrow them using filters (for example, required vs recommended, or specific formats).

What’s the main advantage of using saved queries as tables in Tana?

Saved queries act like dashboards. After the relationships are set (concentration → class → assignment, and books as tagged records), each table view updates automatically as new items are added or edited. That means selecting a concentration yields the right classes and assignments, and selecting a reading set yields the right books—without duplicating data or manually maintaining separate lists.

Review Questions

  1. What specific instance/reference fields are required to make the “Classes” table filter by concentration?
  2. How does the “complete” checkbox enable two different assignment views (incomplete vs completed) using query filters?
  3. Which book fields should be standardized with fixed options to make reading lists reliably filterable?

Key Points

  1. 1

    Create a “Concentrations” table where each concentration links to an advisor via an instance of a “Professor” tag.

  2. 2

    Model “Classes” with an instance reference back to the concentration so class lists can filter correctly per concentration.

  3. 3

    Add semester (as fixed options), professor, hours, and grade fields to each class record for consistent course metadata.

  4. 4

    Model “Assignments” with an instance reference to a class plus a due date and a “complete” checkbox to power dynamic to-do lists.

  5. 5

    Build a “Books” table with standardized reading status, author instances, genres, format, and publication date so book lists can be filtered cleanly.

  6. 6

    Use saved queries rendered as tables to create live dashboards that update automatically as items change.

  7. 7

    Filter assignment and reading tables using checkbox state and reading-status fields to keep views focused on what matters next.

Highlights

The workflow’s core move is relationship modeling: concentration → class → assignment, plus a separate books record set, so tables can filter themselves.
Saved queries configured with instance references prevent “everything in one list” problems and keep each view scoped to the selected concentration or class.
A single “complete” checkbox turns one assignments table into both a workload view (incomplete) and a progress view (completed).
Standardizing book metadata (reading status, author, format, publication date) makes reading lists reliably filterable without rework.

Topics

  • Tana Workflow
  • College Reading
  • Data Modeling
  • Saved Queries
  • Assignments Tracking