app.atomes.readingStatus
Where 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.
Details · record, key any
| Kind | record |
|---|---|
| Record key | any |
| Authority | atomes.app |
| Indexed |
Record
record · key anyProperties
finishedAt
string · datetimeWhen the reader finished the Work, if they said.
ISBN-13 of the Edition the reader read or is reading.
minLength: 13maxLength: 13
knownValues: unread | reading | read | abandoned
Catalog identifier of the Work; equals the record key. 'isbn:<isbn13>' when the Catalog does not know the Work.
maxLength: 128
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
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 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 rec
-
app.atomes.follow
recordA Series the reader follows, or has dropped, in one Edition Line. One per Series: the record key is the Series' Catalog identifier.
-
ink.resenha.reading
recordA reader's reading of a book BookHive's catalogue doesn't hold, or can't be matched to for certain: the home of last resort, so any book can be added to a library and reviewed. One per book. Status, dates, rating, review and progress live here as they do on a buzz.bookhive.book; the book is named in every key anyone uses, so any app that recognises one of them can show the reading. When BookHive's catalogue has the book, Resenha moves the reading there: it writes a buzz.bookhive.book with everyt
-
Shared definitions for the org.shelfcheck.* lexicon: status tokens, book identifiers, and structured author references.