> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/data-map/creating-a-data-map.md).

# Creating a Data Map

Perform the following procedure to create a new Data Map:

**Note:** Before you perform this procedure, ensure the:

* Scanner software (that provides the DLL's required as a prerequisite to setting up Data mapping items) is installed, and
* Personal Data Fields (that will be used by the scanner) are created and added to the appropriate Access Groups (Visitor Types) and the Selected Fields grid on the **Visitor Fields** tab of the Visitor Management Division Configuration.

1. Click the **New Data Map** button on the Viewer Navigation Panel.

   The new Data Map is added to the Viewer Navigation Panel, and the Data Map Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-1efaea034684de202405c6a9cf09002ab2edc6fa%2Fdatamapconfig_popup.png?alt=media)
2. If you want to replace the default name the system has given the Data Map, enter a new name in the **Name** field (limited to 60 characters).
3. If required, enter a logical **Description** (limited to 200 characters).
4. The **Division** button defaults to the name of the last Division in which the Operator created a Command Centre item, regardless of whether it was created in Configuration Client or via Command Centre Client.

   If this is not the appropriate Division for this Data Map, select a Division as follows:

   1. Click the **Division** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7b199073d021ca11902823b748c96d639d5d5f0f%2Fselectdivision_browsetool.png?alt=media)
   2. Select the appropriate Division.
   3. Click the **OK** button.

      The pop-up closes and the button changes to the name of the Division you selected.

   **Note:** If you have not set up Divisions yet, you can add these to your Data Map at a later stage.
5. Click the **Close** button.

   The Data Map Configuration pop-up closes.

   There are four tabs, (i.e. **Source Configuration**, **Destination Configuration**, **Mappings** and **History/Notes** ). The **Source Configuration** tab displays by default.
6. Select the appropriate document type, (e.g. General ID or Passport) from the **Source** drop-down list of available DLL's installed.
7. If you select General ID as the **Source**, you must also click one of the region radio buttons and select the appropriate region from the drop-down list.

   For the ‘Auto detect option’, there are four regions to choose from, (i.e. Asia, Australia, Canada and United States). For the ‘More specific’ option there is a more extensive list of regions available.
8. Click the **Destination Configuration** tab, and select the appropriate **Destination** from the drop-down list.
9. Click the **Mappings** tab.
10. Click the **Add Mapping** button to configure the scanning software to automatically populate the Visitor fields (within Visitor Management) when a form of ID is scanned.

    ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-99036a880573c49a5a24d9b1942df9dcfe8d6ebf%2Fmappingstab_datamap.png?alt=media)
11. Click the drop-down under **Source Field**.

    All available OCR Source fields are listed. The majority of fields are text type PDFs with the exception of the last three that are image type PDFs, (i.e. Image of document, Portrait and Signature).
12. Select the field you want to map to a **Destination Field**.
13. Click the drop-down under **Destination Field** and select the appropriate field to map the source field to.

    **Note:** If the type of Destination Field you select is incompatible with the Source Field, (e.g. an image mapping to a text PDF), an error message will display in the **Transformation** field.

    ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-273f9248b4a5bebfc245f13de84e4b18d0a908f8%2Fmappingstab_datamaptransformation.png?alt=media)

    Although you can carry on performing other functions, the **Save** button will remain disabled until you correct the error by either changing one of the fields so they are compatible, or selecting a transformation type from the **Transformation** drop-down list.
14. Repeat Steps 10 - 13 for each mapping you require.
15. If you want to record any note(s) about the Data Map, click the **History/Notes** tab.

    Refer to [History/Notes tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/history-notes-tab.md) for further detail.
16. Click the **Save** button.

    A new Data Map has been created.

    **Note:** Once a Data Map is saved the **Source** and **Destination** cannot be changed on the Data Map Configuration pop-up.

### Hints

{% hint style="info" %}
**Editing and Deleting Data Maps**

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/deleting-items.md) for procedures on how to edit and delete Data Maps.
{% endhint %}

{% hint style="info" %}
**Duplicating Data Maps**

Operators privileged to create Data Maps can also duplicate Data Maps, which makes the task of setting up multiple Data Maps that are very similar much quicker.

Refer to [Copying items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/copying-items.md) for the procedure.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/data-map/creating-a-data-map.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
