Sophora not only keeps track of your latest document state, but also previous versions. It automatically creates Snapshots on a defined list of actions, such as on publish, or manually, if needed. Going back to a previous version is as easy as restoring it. You can access all document versions via the Sophora Version Store, an internal Sophora Server component that uses PostgreSQL as its datastore.
Staging Servers do not contain versions
All the following documentation applies to Sophora Servers running in modes “primary”, “replica” or “cluster”. Staging Servers only contain exactly the latest published version of all documents and therefore neither need a Version Store nor a Live Workspace.
Create a version
In Sophora, you automatically create a version of a document when you perform one of these actions:
- Publish
- Set Offline
- Delete
- Release
You can also explicitly create a version directly from the DeskClient or the Sophora Client API.
Distinction between working and live workspace and the Sophora Version Store
On a technical note, Sophora stores documents and their versions in three stores:
| Name | Technology | Description |
|---|---|---|
| Working Workspace | various supported Databases (MySQL), JCR Layer | Stores the latest document version or draft. |
| Live Workspace | various supported Databases (MySQL), JCR Layer | Stores the latest published document version. |
| Version Store | PostgreSQL, SQL | Stores all document versions. |
Once you create a version, the Version Store saves the current state of the document as its own version. At this point the working workspace and the latest version of the Version Store store the same document, but in separate databases. When publishing a version, all three databases basically point to the same document version.
Saving a document does not automatically create a version and therefore only updates the working workspace.
