Content on this website goes through a workflow which has a number of 'states', eg draft, published, check accuracy. When content is first created it has the 'draft' status. The owner (or those with the right permissions) can edit and move the status to the next step which in this case is 'check accuracy'. The resource can not be publically seen until it is 'approved'. Once approved and edited, the approved one will stay publically seen while the edited one goes through the review process. Once the newer version has been approved it will replace the publically seen version.

The public version is the normal URL, eg /node/890

The latest version that is going through revision/workflow has '/latest' added to it, eg /node/890/latest

When editing the content, you will always be editing the latest version, ie /node/890/edit is editing /node/890/latest not /node/890.

CURRENT SITUATION

There is a lot of content that is currently public that needs to be checked. This content ideally should not be public, but then there won't be much on the site so we are in a temporary phase as all content is checked. To make this work there are two public statuses, 'published' (the old version) and 'approved' (the new version). The approved version replaces the old 'published' version. Since all new content cannot go from draft to published, but must go through the review process to be approved there will not need to be any changes to the site.

REVISIONS VIEW

Using the revisions view of the content will give you the list of all revisions and indicate the latest (top of the list) and the public version (current version). You can view any revision, but only edit the latest version. If you 'revert' or 'set as current version', a version which is a publicable status, ie 'published' or 'approved' then it will become the public version. If you 'revert' or 'set as current version' a version which is not publicable, eg 'check accuracy' it will become the latest version which is the non public version that can be edited. Yes, 'revert' or 'set as current version' does not quite do what it says it should do, ie revert should only be version that are publicable (published or approved) and 'set as current version' should be on all other versions.

You can also compare any two versions which can be quite a handy feature.