Core purpose
The same work may first be serialized on a web platform, then published as a book, released in other languages, and even republished on another platform. These differences cannot be resolved by duplicating work identity, nor can they all be compressed into a text field named “version.”
A Release is an independent Unit that describes one concrete publication that can be identified, cited, and related.
What is available now
- Create Releases with stable IDs and multilingual presentation.
- Relate it to a series and its corresponding work Unit.
- Represent platform, language, region, format, publisher, and time context.
- Show actual edition relationships in work details and series pages.
- Let reviews, collections, and external sources point more precisely to the version they need.
Why it matters
The original serialization, a translated serialization, and a published edition can share work context while retaining their own sources and update rhythms. Readers can therefore identify which version they are viewing instead of assuming that matching titles mean identical content.
In development
Version differences, platform-version ranges, and import validation remain in development. Reliable source and identity governance must come first; string similarity must not automatically declare two releases to be the same.
Relationships and boundaries
A Release is not another work, and it does not manage sales, inventory, file delivery, or DRM. It preserves an understandable release identity and its relations; actual reading still returns to lawful sources or licensed content-hosting services.