Page History

...

The other proposed use case is a pair (or more) of labs which share a repository, but they must not be allowed to see each other's unpublished resources.  In this picture, Lab A's resources are stored in separate workspaces - including a separate published graph and separate withdrawn graph - from Lab B's. 

The labs also have separate resource-navigator and curator roles, RNav-A, etc.  When a user in the RNav-A role creates a new instance, she must choose (or take by default if it is the only one available) the transition out of New into the Draft state in Workspace A.   Note that the states are labelled A and B but they are really the same states, it is the workspace or other graph which separates A from B. 

...