New Crowd Structure

gistfile1.txt

- crowd
  - data
    - $domainId
      - $deploymentId
        - $crowdId
          - name
          - demographics
          - domainId
          - deploymentId
  - lists
    - domain-utterances
      - $domainId
        - $deploymentId          
          - $crowdId
            - $utteranceId: orderNumber


Utterance on review for crowd01

utterance01
Bot: user utterance
Topic: topic1

        utterance02
        User: user utterance
        TopicPathName: topic path 1

utterance03
Bot: user utterance
Topic: topic2
        
        utterance04
        User: user utterance
        TopicPathName: empty (topic new path 1)

utterance05
Bot: user utterance
Topic: empty (new topic 2)



- crowd
  - data
    - crowd01
      - name
      - demographics
      - domainId
      - deploymentId
  - lists
    - domain-utterances
      - domain01
        - deployment01
          - crowd01
            - utterance01: 0
            - utterance02: 1
            - utterance03: 2
            - utterance04: 3
            - utterance05: 4
- utterances
  - data
    - utterance01
      - topic: topic01
    - utterance02
      - topicPath: topicPath01
    - utterance03
      - topic: topic02
    - utterance04
    - utterance05


If designer adds a topic for utterance05

utterance05 is topic03
Then utterance04 should automatically use topicPath02 which connects topic02 and topic03 on crowdCreatedPaths

if designer adds a topic of utterance05 to newtopic04
Then utterance04 should automatically create a new path newTopicPath03 which conects topic02 and newtopic04 on crowdCreatedPaths

So if designer change the topic from empty to new topic, it creates a new topic in the macro review.