Same Simple Process Approach for all Apps
Each MapDeck app is designed to perform a discrete task.
Apps use internal tables and/or require user actions as an input, then they allow saving the end result of the process for further reuse – that is, either to update previously saved resource or save as a new version.
Any new user generated content is always “saved to” that user’s My Vault folder.
When creating new content (i.e. data tables) MapDeck will always create a product description record (metadata). This may seem unnecessary overhead but, in the long run, the benefit of maintaining proper information about your content outweighs the pain and effort of creating it. It will not only make it easier to find that particular piece of data amongst all your content but metadata will also record its lineage and will make it easier to distinguish between different versions you create and work with over time. Just trust us on this!
To navigate to a specific content on MapDeck use Finder app or click through Vault folders.
As a general rule, on start, all resources open in a new browser window. Close the window after finishing your task without logging out of MapDeck to continue with the current session. The exceptions are resources initiated from a Deck but this is for a good reason – read more about it on Help pages of Deck Manager app.
To preview content of MapDeck tables (i.e. system data) or map layers click the “Start” button on the selected resource (triangle icon). It will activate the Data Viewer app, a default tool for previewing such content.
To interact with a Table resource in MapDeck (e.g. to edit tables, create derived information, etc.) the convention is that you first select and start a relevant MapDeck app (i.e. suitable for what you are trying to do) and then you load the table and/or map layers of interest.
Sharing on MapDeck
MapDeck is designed for easy sharing of content. The basic convention is that sharing privileges have to be set for each resource individually. For example, sharing a folder which contains private resources will not allow third parties to access those resources unless the user specifically set access permissions to those resources.