While collecting topics, you will often collect duplicate topics.
For example, on Thursday, you collect data using the following criteria:
Overdue - collects all the overdue tasks;
This week - collects all the tasks that are active in this week;
This week - End - collects all the tasks that will end this week;
Using Overdue, results in a search only collecting overdue tasks (normal).
Using This week - End, results in a search only collecting tasks that end this week (normal).
However, This week, will result in a search collecting all tasks from this week, including Overdue tasks and tasks that satisfy This week - End. This situation may result in the data collection engine gathering duplicate tasks.
You will want to exclude Overdue tasks and This week - End tasks from the tasks collected under the This week condition.
To do this, use the operator filterdoubles_map. This keyword will identify and exclude any duplicates that appear in a filtered map. You may also use the operator filterdoubles_branch, to eliminate duplicates that appear inside a branch (not in a whole map).
Using these operators will make the resulting map more readable.
Other collection cases may also produce duplicate tasks/topics, but they are not as overwhelming as using the keywords like This week, which can return twice as many topics.
You need to be aware that you may get duplicates in your collection maps.
When you change something in one of the duplicated topics and then send changes back to original maps, the Data Collection Engine keeps track of all duplicated topics. It synchronizes the differences between them in real-time. All your duplicates will always be identical.
Everything is under control :-)