Existing membership assoc block the creation of new associations of other types
E.g. the following condition is met:
User1 (Username) <-- Membership Assoc --> DMX (Workspace)
Status: Once such a membership assoc is created between a username and a workspace, no other association (regardless of its specific type or semantics) can currently be created to associate these two players. Currently User1 can by no means associate herself with this workspace using different semantics/any other assoc type.
Subsequently, the creation of any other assoc currently fails due to a
duplicateCheck and the RuntimeException
Duplicate: such an association exists already.
Example: User1 can by no means subscribe to updates from the workspace using the DMX Notifications plugin.
A subscription here is modeled using the "Notification Subscription" edge between Username and Workspace. This is courtesy of the "DMX Notifications" plugin.
Cause: The error is caused due to the re-typing of the workspace module. The workspace module suggests users IF they create an assoc between a Username and a Workspace, this will always be one of type "Membership" while, in fact, it was not even my intent to create a 2nd "Membership" assoc. As a result, users are powerless here. The user can't decide which assoc type is the desired one. The request simply fails with an Exception.