social.dracome.library.state
A reading-state record for one edition per actor. Duplicate convention: the rkey is a TID minted once at first create and never changes. Several records may exist for one actor and edition (for example from out-of-band writers); consumers SHOULD treat the record with the greatest `updatedAt` (falling back to `createdAt`) as the winner and break ties by the lowest TID, ignoring the others. This is a convention, not an enforced contract: AppViews MUST tolerate a differing winner, and may see a record's catalogTarget change over time.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | library.dracome.social |
| Indexed |
Record
record · key tidProperties
Point-in-time catalog metadata for the tracked work or edition, captured when this record was last written. Refreshed on every update.
The work and edition that this reading-state record tracks. Mutable.
Optional user-confirmed override of catalog totals (page count, chapter count, or audio duration) for this specific target.
Canonical UTC instant serialized as ISO 8601 with a trailing Z suffix.
finishedAt
string · datetimeCanonical UTC instant serialized as ISO 8601 with a trailing Z suffix.
progress
refOptional log of the actor's reading or listening progress over time for this target.
startedAt
string · datetimeCanonical UTC instant serialized as ISO 8601 with a trailing Z suffix. This records the first instant the actor entered in_progress for the current reading episode. Returns to in_progress within 14 days preserve the same startedAt.
The actor's current reading-state status for this target, e.g. wishlist, backlog, in_progress, paused, completed, or abandoned.
updatedAt
string · datetimeCanonical UTC instant serialized as ISO 8601 with a trailing Z suffix.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
A favorite/tracked marker record for one edition per actor. Duplicate convention: the rkey is a TID minted once at first create and never changes. Several records may exist for one actor and edition (for example from out-of-band writers); consumers SHOULD treat the record with the greatest `updatedAt` (falling back to `createdAt`) as the winner and break ties by the lowest TID, ignoring the others. This is a convention, not an enforced contract: AppViews MUST tolerate a differing winner, and may
-
app.atomes.readingStatus
recordWhere the reader stands with a Work. One per Work: the record key is the Work's Catalog identifier. Exists with or without a Copy. No record means unread.
-
social.dracome.library.defs
not from the namespace authorityHow an actor came to own a specific book edition, tracked on a `library.acquisition` record.
-
com.hectorsector.book.status
recordA reading status change event for a book. Records are append-only and timestamped — each status transition creates a new record rather than mutating an existing one. The current status of a book is derived by taking the most recent status record (by createdAt) referencing that book.
-
A reader's relation to one catalog edition, published from the copy they are holding. Two shapes share this collection: a position record (one per edition and format, its rkey the edition's rkey and the format's slug, rewritten as the reader moves) and an annotation record (one per note, under a TID, rewritten when the note is edited). `createdAt` is when the record was first published — the position's first save, the note's own creation — and `updatedAt` when it last changed. Written by Livtet