Contextualise is an effective tool particularly suited for organising information-heavy projects and activities consisting of unstructured and widely diverse data and information resources
In the vast majority of the forms the user is expected to provide references to other topics. For example, when creating an association, the user needs to provide up to 5 references to other topics if overriding the defaults and providing "advanced" values (see attached screen shot):
destination topic
destination role
source role
association type
context (i.e., scope)
All of the referenced topics have to exist in advance to creating an association. This is very cumbersome. A suggested workflow (for each reference) would be to determine the existence of the topic after the user has provided the reference/identifier (obviously, the topic exists if the user has selected the reference/identifier from the auto-complete drop-down) and if the reference/identifier does not exist to provide the user with the possibility to create the necessary topic "in place" (i.e., as part of the association creation workflow) in a separate, intermediate workflow.
brettkromkamp
commented
4 years ago
In the vast majority of the forms the user is expected to provide references to other topics. For example, when creating an association, the user needs to provide up to 5 references to other topics if overriding the defaults and providing "advanced" values (see attached screen shot):
All of the referenced topics have to exist in advance to creating an association. This is very cumbersome. A suggested workflow (for each reference) would be to determine the existence of the topic after the user has provided the reference/identifier (obviously, the topic exists if the user has selected the reference/identifier from the auto-complete drop-down) and if the reference/identifier does not exist to provide the user with the possibility to create the necessary topic "in place" (i.e., as part of the association creation workflow) in a separate, intermediate workflow.