Collect data

Specifics of collecting data from cloud maps

You can collect data from your maps using Express-collection and Collection by Template.

Express-collection collects data by collection topic(s) that you have placed in the current map. You create these topics "manually" immediately before collection or add them to the map as collection express templates from the drop-down menu under the Collection Templates button.

Collecting data when you want to find current project issues or quickly determine the next task is convenient. Also, a project leader may find it convenient to gather the activities that an employee is responsible for when you contact them about a project. Or a manager can collect the information immediately relevant to the discussion.

Setting up a template-based collection is the best choice if you regularly collect data using the same criteria. The template has the same collection topics but is well-constructed and stored for permanent use.

Both methods follow the same collection concepts and techniques.

Express-collection

See the previous sections for a detailed discussion on Express Collection.

Here is a summary of how to use it:

Create a topic/branch with data collection criteria on a current map. Or add a data collection express template to the map.
Choose a Collection Configuration (to the left of the Collect Data button).
Select the topic/branch and click the Collect data command.

MultiMaps will collect data according to the collection criteria specified in the collection topic/branch from the sources specified in the Collection Configuration, taking into account the options specified in the Collection Configuration.

Collection by Template

1. Select the Collection Configuration (to the left of the Collect Data button).

2. Click the required collection template in the drop-down menu under the Collect Data button.

Data recollection

Sometimes you may need to update the collected data after the original collection. That is, recollect data for the collection branch or template.

Select the branch you want to update or open the collection map that MultiMaps generated through collecting data by a template.

Check the collection configuration (to the left of the Collect Data button) and ensure that you have selected: From current map.

Click the Collect Data button.

MultiMaps always stores the collection configuration in the collection map. Therefore, MultiMaps uses the sources and options used during the first collection when recollecting data.

You may want to change the collection sources when updating the collection map/branch (for example, to add another map from which you also want to collect data) or tweak the collection options.

Click the Configuration in the current map button:

In the window, change the collection sources or options. MultiMaps will recollect data according to this modified collection configuration.

Collecting data from cloud maps

MultiMaps allows you to collect data from maps located in the cloud storages.

But there are a number of features you must understand and consider when collecting data from cloud maps.

Unfortunately, at the moment, working with maps from cloud storages in MindManager leaves much to be desired.

MindManager API does not allow to download a map from the cloud storage as well as upload a map to the cloud. MultiMaps can only "ask" MindManager to open a cloud map. And only then it can search for the necessary data in the open map. (In case of the local maps, MultiMaps does not open them in MindManager when collecting data, but "infiltrates" the map files, looking for the necessary data. This significantly (ten times) speeds up the process of searching and collecting data.)
Sometimes MindManager takes a long time to open a map from cloud storage. On average, this process takes 5-10 seconds, but it can take up to 60 seconds (and even more!). Even in the case of not a large maps. And until MindManager opens the map, data collection is not possible.
Sometimes MindManager saves the map to the server (the cloud) for a long time as well. On average, this process takes 5-10 seconds, but sometimes up to a minute. And until he saves it, it should not be closed, otherwise the changes will be lost. Unfortunately, the MindManager API does not provide a way to know if the process of saving a map to the server has finished or not yet. For this reason, if the user has made changes to the collected data and sent the changes to the original maps, MultiMaps will save these maps, but leave them open in MindManager (no way to know if MindManager finished pushing changes to the server).

Let's summarize:

To collect data from the cloud maps, MultiMaps has to open them in MindManager in visible mode. This process is time consuming, especially if there are a lot of maps. (You will spend no less time if you want to open them manually).
After collecting data from cloud maps, MultiMaps can automatically close these maps, or can leave them open. You make the decision. There are options in the MultiMaps Settings for this.
- If you only need the data for a viewing or analysis, it is better to indicate that maps are automatically closed after collection.
- If you are going to make changes in the collected data and then send changes to the originals, it is better if MultiMaps keeps the maps open (to not to open them again for pushing the changes).
When sending changes to the originals, MultiMaps should open that maps (if they are not already open). After changes has sent, MultiMaps saves affected maps, but keeps them open. MultiMaps won't close them (although it can) because the MindManager API doesn't provide a way to know if the changes are already saved on the server (the cloud). So you should manually close these maps .