See also the closed previous issue #172.

In the second step of our performance analysis we can use the seeding tool to generate dummy data and analyse our bottlenecks.

Secondly, create a topics collection which avoids the nested structure of the meeting series document. Compare the performance of both scenarios.

ACs

• Create a new Collection topics
• Add parentId-Property to reference a topic with its related meeting series
• When finalizing a minutes copy and update its topics and store them in the new collection
• When un-finalizing a minutes perform the necessary topic operations on the new topics collection
• When creating a new minutes query the open topics from the new collection
• When creating a new minutes make sure closed action items and non-sticky info items will not be carried to the new minutes
• On the meeting series items / topics tab query the topics from the new collection
• Feature "re-open topics" should work on the new topics collection
• Collect requirements and make a concept for the order of the topics/items displayed on the meeting series topics/items tab. We will implement this in a separate story: Sort entries of Tab "Items" #154
• Add a db migration which moves all existing topics which are currently stored as subdocuments of the meeting series into the new collection and attach the correct parentId
• Move the subscription of the new topics collection into the template
• Deleting a meeting series should remove its related topics, too
• Purge Topics Collection in end2end helper: e2e.resetMyApp
• Adapt minutes seeding tool