Core purpose
A title is only one way to find a work. Readers also arrive through authors, translators, publishers, illustrators, characters, and worldbuilding concepts. REZICS makes those objects reusable Entities rather than leaving them as text fields on every page.
Entities can be real people and organizations or fictional characters and concepts. They share stable identity and multilingual presentation, while their relationships retain distinct meanings.
Two relationships that must not be confused
Credit attribution
This says who did what for content or a work: author, translator, publisher, developer, or distributor. The relationship can preserve role, order, and sources so attribution does not depend on free text.
Subject association
This says whom or what content discusses, includes, or derives from: a protagonist, appearing character, theme, adaptation, or fan work. It never mistakes the character discussed for a creator.
What is available now
- Create multilingual identities for people, organizations, characters, and concepts.
- Connect author, translator, publisher, and other credits to books, Posts, and other works.
- Connect characters, subjects, and derivative relationships to the correct objects.
- Preserve traceable links to sources and external pages.
- Reuse the same entity data in search and work detail pages.
In development
External authority IDs, source evidence, and relationships for entity-specific knowledge pages will be strengthened. A character’s wiki explanation belongs in a Post and is connected to the character and work through subject association; long text does not belong in a relationship row.
Relationships and boundaries
Entities do not replace user accounts: accounts identify who signs in and acts, while Entities describe objects in the work network. A source link is not credit attribution; official sites, platform pages, and author relationships must be expressed separately.