community.lexicon.media.book.review

A review or rating of a book. Separate record keys allow multiple reviews of the same book, including rereads.

Details · record, key tid
Kindrecord
Record keytid
Authoritybook.media.lexicon.community
Commit rev3n2h5svsmh22j
Indexed

Showing version bafyreidwjlm3r5ffp5d6k32f7v3emvpb6fxzflwy7uyizmlvjft56z43ly. Show the latest

Record

record · key tid

Properties

content

union

Optional client-specific rich content, using the same open-union shape as site.standard.document.content. Each content object must include a $type identifying its format. A written review must also supply its plain-text textContent fallback.

One of

createdAt

requiredstring · datetime

Time this review was created.

Reference

rating

integer

Rating on a 1-20 scale; divide by four for a five-star display.

  • minimum: 1
  • maximum: 20

subjectRecord

string · at-uri

Optional AT-URI to an edition record for enrichment; subject.identifiers remain the matching mechanism.

Plain-text review, without Markdown. At least one of rating or nonempty textContent must be supplied. Rich content alone does not satisfy this requirement.

  • minLength: 1

#flags

object

Optional review presentation flags.

Properties

spoilers

boolean

Whether the review contains spoilers.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • Create a review of an edition at a fresh TID rkey. Separate rkeys allow multiple reviews of the same book, including rereads.

  • A review for a piece of media

  • A user's review of a book. StrongRefs the catalog book and optionally the originating bookShelving. rkey: tid. Written by the OAuth client (livtet-service) via com.atproto.repo.putRecord.

  • A review of one edition by an 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 catalog

  • how.bun.reviews.review

    record not from the namespace authority

    Record containing a review of something.