Overview The progress tracking system allows users to track their consumption status across all six media types. Each media type has specialized tracking models that capture viewing/reading/playing progress with appropriate granularity.
Progress Models TrackGeek uses two types of progress tracking:
Watch/Read Models : Legacy models for anime, manga, TV shows, movies, and books with episode/chapter trackingProgress Models : Unified progress tracking for all six media types with standardized status tracking
Progress Status Enum All progress models use the ProgressStatus enum for consistency:
enum ProgressStatus { Watching Playing Reading Completed Paused Dropped Planning }
Source : prisma/schema.prisma:633-641The status names are context-aware. “Watching” applies to anime/TV/movies, “Playing” to games, and “Reading” to books/manga.
Watch Status Enum Legacy watch models use the WatchStatus enum:
enum WatchStatus { Watching Completed Paused Dropped Planning }
Source : prisma/schema.prisma:523-529Read Status Enum Legacy read models use the ReadStatus enum:
enum ReadStatus { Reading Completed Paused Dropped Planning }
Source : prisma/schema.prisma:587-593Database Schema Anime Progress
Manga Progress
TV Show Progress
Movie Progress
Game Progress
Book Progress
AnimeProgress Model Tracks anime watching progress with status tracking. model AnimeProgress { id String @id @default ( uuid ()) status ProgressStatus userId String animeId String createdAt DateTime @default ( now ()) updatedAt DateTime @updatedAt user User @relation ( fields : [ userId ], references : [ id ] ) anime Anime @relation ( fields : [ animeId ], references : [ id ] ) @@unique ( [ userId , animeId ] ) @@index ( [ userId ] ) }
Source : prisma/schema.prisma:643-656AnimeWatch Model (Legacy) Legacy model with episode tracking: model AnimeWatch { id String @id @default ( uuid ()) season Int episode Int status WatchStatus userId String animeId String startedAt DateTime ? completedAt DateTime ? createdAt DateTime @default ( now ()) updatedAt DateTime @updatedAt user User @relation ( fields : [ userId ], references : [ id ] ) anime Anime @relation ( fields : [ animeId ], references : [ id ] ) @@unique ( [ userId , animeId ] ) @@index ( [ userId ] ) }
Source : prisma/schema.prisma:531-548Each user can only have one watch record per anime (enforced by unique constraint).
MangaProgress Model Tracks manga reading progress with status tracking. model MangaProgress { id String @id @default ( uuid ()) status ProgressStatus userId String mangaId String createdAt DateTime @default ( now ()) updatedAt DateTime @updatedAt user User @relation ( fields : [ userId ], references : [ id ] ) manga Manga @relation ( fields : [ mangaId ], references : [ id ] ) @@unique ( [ userId , mangaId ] ) @@index ( [ userId ] ) }
Source : prisma/schema.prisma:658-671MangaRead Model (Legacy) Legacy model with chapter and volume tracking: model MangaRead { id String @id @default ( uuid ()) status ReadStatus chapter Int ? volume Int ? userId String mangaId String startedAt DateTime ? completedAt DateTime ? createdAt DateTime @default ( now ()) updatedAt DateTime @updatedAt user User @relation ( fields : [ userId ], references : [ id ] ) manga Manga @relation ( fields : [ mangaId ], references : [ id ] ) @@unique ( [ userId , mangaId ] ) @@index ( [ userId ] ) }
Source : prisma/schema.prisma:614-631TvShowProgress Model Tracks TV show watching progress with status tracking. model TvShowProgress { id String @id @default ( uuid ()) status ProgressStatus userId String tvShowId String createdAt DateTime @default ( now ()) updatedAt DateTime @updatedAt user User @relation ( fields : [ userId ], references : [ id ] ) tvShow TvShow @relation ( fields : [ tvShowId ], references : [ id ] ) @@unique ( [ userId , tvShowId ] ) @@index ( [ userId ] ) @@map ( "TVShowProgress" ) }
Source : prisma/schema.prisma:673-687TvShowWatch Model (Legacy) Legacy model with season and episode tracking: model TvShowWatch { id String @id @default ( uuid ()) season Int episode Int status WatchStatus userId String tvShowId String startedAt DateTime ? completedAt DateTime ? createdAt DateTime @default ( now ()) updatedAt DateTime @updatedAt user User @relation ( fields : [ userId ], references : [ id ] ) tvShow TvShow @relation ( fields : [ tvShowId ], references : [ id ] ) @@unique ( [ userId , tvShowId ] ) @@index ( [ userId ] ) @@map ( "TVShowWatch" ) }
Source : prisma/schema.prisma:550-568MovieProgress Model Tracks movie watching progress with status tracking. model MovieProgress { id String @id @default ( uuid ()) status ProgressStatus userId String movieId String createdAt DateTime @default ( now ()) updatedAt DateTime @updatedAt user User @relation ( fields : [ userId ], references : [ id ] ) movie Movie @relation ( fields : [ movieId ], references : [ id ] ) @@unique ( [ userId , movieId ] ) @@index ( [ userId ] ) }
Source : prisma/schema.prisma:689-702MovieWatch Model (Legacy) Legacy model for movie completion tracking: model MovieWatch { id String @id @default ( uuid ()) status WatchStatus userId String movieId String startedAt DateTime ? completedAt DateTime ? createdAt DateTime @default ( now ()) updatedAt DateTime @updatedAt user User @relation ( fields : [ userId ], references : [ id ] ) movie Movie @relation ( fields : [ movieId ], references : [ id ] ) @@unique ( [ userId , movieId ] ) @@index ( [ userId ] ) }
Source : prisma/schema.prisma:570-585Movies don’t have episode tracking since they’re single units of content.
GameProgress Model Tracks game playing progress with status tracking. model GameProgress { id String @id @default ( uuid ()) status ProgressStatus userId String gameId String createdAt DateTime @default ( now ()) updatedAt DateTime @updatedAt user User @relation ( fields : [ userId ], references : [ id ] ) game Game @relation ( fields : [ gameId ], references : [ id ] ) @@unique ( [ userId , gameId ] ) @@index ( [ userId ] ) }
Source : prisma/schema.prisma:704-717Game progress uses the “Playing” status to indicate active gameplay.
BookProgress Model Tracks book reading progress with status tracking. model BookProgress { id String @id @default ( uuid ()) status ProgressStatus userId String bookId String createdAt DateTime @default ( now ()) updatedAt DateTime @updatedAt user User @relation ( fields : [ userId ], references : [ id ] ) book Book @relation ( fields : [ bookId ], references : [ id ] ) @@unique ( [ userId , bookId ] ) @@index ( [ userId ] ) }
Source : prisma/schema.prisma:719-732BookRead Model (Legacy) Legacy model with chapter and volume tracking: model BookRead { id String @id @default ( uuid ()) status ReadStatus chapter Int ? volume Int ? userId String bookId String startedAt DateTime ? completedAt DateTime ? createdAt DateTime @default ( now ()) updatedAt DateTime @updatedAt user User @relation ( fields : [ userId ], references : [ id ] ) book Book @relation ( fields : [ bookId ], references : [ id ] ) @@unique ( [ userId , bookId ] ) @@index ( [ userId ] ) }
Source : prisma/schema.prisma:595-612Status Transitions The progress system supports natural status transitions based on user behavior:
Status Definitions
User is actively consuming the media. This is the primary active state.
Anime/TV/Movie : Currently watchingManga/Book : Currently readingGame : Currently playing
User has finished the media in its entirety. This is a terminal state indicating full consumption. Completion automatically triggers feed events and can unlock achievements/medals.
User has temporarily stopped but intends to continue. Progress is preserved. Can transition back to active state or forward to Completed/Dropped.
User has discontinued and doesn’t intend to continue. Progress is preserved but consumption ceased. Dropped items can still be reviewed and are counted in user statistics.
User intends to start but hasn’t begun yet. This is the initial state. Common for:
Upcoming releases
Backlog management
Wishlist tracking
Progress Features Unique Constraints All progress models enforce a unique constraint on [userId, mediaId] to ensure:
One progress record per user per media item
No duplicate tracking entries
Clean update patterns
Example from AnimeProgress (prisma/schema.prisma:654):@@unique ( [ userId , animeId ] )
Automatic Timestamps Every progress record maintains:
createdAtupdatedAt
Legacy Models: Temporal Tracking The legacy Watch/Read models track consumption timeframes:
startedAtcompletedAt
Legacy Models: Granular Progress Watch/Read models track precise position:
Anime/TV Shows
Manga/Books
Movies
seasonepisode Allows resuming at exact position in episodic content.
chaptervolume Both fields are optional since not all manga/books use both. No granular progress needed - movies are atomic units.
Completion Tracking Completion is tracked differently across models:
Progress Models Status-based completion:
const isCompleted = progress . status === ProgressStatus . Completed ;
Watch/Read Models Multiple indicators:
const isCompleted = watch . status === WatchStatus . Completed || watch . completedAt !== null ;
Integration with Feed System Progress updates can trigger feed events to notify followers:
| Event Type | Trigger |
|-----------|---------||
| NewProgress | User updates status to Watching/Reading/Playing |
| NewWatch | User marks anime/TV show as watching (legacy) |
Feed Event Schema (prisma/schema.prisma:230-251):enum FeedEventType { NewFollower NewFavorite NewList NewListItem NewReview NewWatch NewProgress } model FeedEvent { id String @id @default ( uuid ()) type FeedEventType userId String metadata Json ? createdAt DateTime @default ( now ()) user User @relation ( fields : [ userId ], references : [ id ], onDelete : Cascade ) reactions Reaction [] @@index ( [ userId , createdAt ] ) }
User Statistics Progress data powers user statistics and achievements:
Completion Rate Percentage of started items marked as completed
Total Watched Count of anime/TV/movies with Completed status
Total Read Count of manga/books with Completed status
Total Played Count of games with Completed status
Current Watching Count of items with Watching status
Backlog Size Count of items with Planning status
Indexing Strategy All progress models are indexed on userId for efficient queries:
This enables fast retrieval of:
All progress for a user
Status-filtered queries (e.g., “show me all watching”)
Aggregate statistics
Best Practices
Upsert Pattern Use upsert operations to handle create/update seamlessly due to unique constraints
Cascade Deletes Progress records cascade delete when user or media is deleted
Status Validation Validate status transitions to prevent invalid states
Feed Events Consider which status changes should trigger feed events
Migration from Legacy Models If migrating from Watch/Read models to Progress models:
Map WatchStatus/ReadStatus to ProgressStatus
Preserve createdAt and updatedAt timestamps
Store granular progress (episode/chapter) in metadata if needed
Migrate temporal data (startedAt, completedAt) to metadata
Maintain unique constraints on [userId, mediaId]