Concepts
Scryer’s UI and docs reuse a small set of terms. Learn them once and the rest of the app reads consistently.
- Core Model: facets, catalogs, libraries, titles, wanted items, releases, imports, history, and monitoring.
- Acquisition And Routing: indexers, download clients, quality and delay profiles, rules, routing, and search.
- Indexer Coverage: how Scryer searches each wanted item once per indexer, then relies on RSS.
- Extensibility: plugins, provider instances, and the provider catalog.
- Operations: permissions, notifications, subtitles, media servers, requests, the recycle bin, jobs, and scans.
Easy To Confuse Pairs
Section titled “Easy To Confuse Pairs”If two Scryer terms feel interchangeable, check here first.
| PAIR | DIFFERENCE |
|---|---|
| Facet vs Library | A facet defines behavior such as movie, series, or anime. A library is a configured collection boundary inside a facet. |
| Catalog vs Library | A catalog is the visible set of titles you can browse. A library owns roots, permissions, and scans. |
| Quality Profile vs Delay Profile | Quality profiles evaluate suitability. Delay profiles evaluate timing. |
| Quality Profile vs Persona | A quality profile decides which qualities are allowed and where the cutoff sits. A persona decides how releases of the same quality are ranked. |
| Plugin vs Provider Instance | A plugin supplies capability. A provider instance stores local configuration for that capability. |
| Media Server Connection vs Notification | A connection lets people sign in with Plex, Jellyfin, or Emby accounts. A notification tells the media server to rescan after Scryer changes files. |
| Activity History vs Wanted History | Activity history is operational. Wanted history is title and decision oriented. |