> 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/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-booking-data.md).

# Mapping booking data to Gallagher Command Centre fields

### Introduction

This section of the manual describes how to map fields from your source data to Gallagher Command Centre fields.

### Replace processing mode

Replace processing mode assumes all bookings have been provided from the third party system. At processing time the booking record for a bookable resource will be:

* removed if the booking no longer exists;
* added if the booking never existed;
* changed if the booking reference is provided and the booking has been changed;
* remain if the booking details are the same

**Notes:**

* As mentioned above, all booking data must be provided from the third party system. If the third party system provides booking data for the latest bookings only, the existing bookings will be removed.
* A booking for a bookable resource may occur at the same time or overlap another booking for the same bookable resource. This behaviour is by design, and allows for more flexibility in the booking system.

### Command Centre fields

The following table describes the Command Centre bookable resource fields.

<table><thead><tr><th width="162">Field</th><th width="246">Data Type</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>String. Maximum 110 alpha-numeric characters.</td><td>The bookable resource name. This field must be mapped. This field requires an ID mapping. The value mapped cannot be blank.</td></tr><tr><td>Booking Reference</td><td>String. Maximum 255 alpha-numeric characters.</td><td>The unique booking ID provided by the third party system. If mapped, the value cannot be blank.</td></tr><tr><td>Booking Name</td><td>String. Maximum 255 alpha-numeric characters.</td><td>The display name given to the booking. Used in status messages, events and alarms in Command Centre. If mapped, the value can be blank.</td></tr><tr><td>Start Date</td><td>Date/Time</td><td>The start date of the booking. This field must be mapped.</td></tr><tr><td>End Date</td><td>Date/Time</td><td>The end date of the booking. If mapped, the value cannot be blank.</td></tr><tr><td>Start Time</td><td>Date/Time</td><td>The start time of the booking. This field must be mapped.</td></tr><tr><td>End Time</td><td>Date/Time</td><td>The end time of the booking. This field must be mapped.</td></tr><tr><td>Interval Type</td><td>Interval Type</td><td><p>Can be used if the source data doesn’t specify a booking end date. Enables you to specify re-occurring bookings, (i.e. One Off, Daily, Weekly or Monthly).</p><p>Use either the Interval Count or the Occurrence Pattern field to specify the repeat instances.</p><p>Defaults to "One Off" if not specified.</p></td></tr><tr><td>Interval Count</td><td>Numeric. Maximum 32767 numeric characters.</td><td>The number of re-occurring instances for the booking. Defaults to "1" if not specified.</td></tr><tr><td>Occurrence Pattern</td><td>String that must only contain the characters "1" or "0". Maximum 64 characters.</td><td>The number of re-occurring instances for the booking. Where "1" is a booking instance. Maximum 64 characters.</td></tr></tbody></table>

**Notes:**

* If the booking end date is specified, and the booking spans more than one day, the booking will run until the end date and time is reached.
* Repeat bookings, (i.e. bookings using an Interval Type of daily, weekly, or monthly and an Interval Count/Occurrence Pattern mapping) cannot be configured to span midnight.
* The dates and times for a booking must be synchronized with the Command Centre server PC time zone.
* If the date for a monthly re-occurring booking falls on a day that does not exist in the calendar, (e.g. 31st of February), then the booking will occur on the last day of that month, (e.g. 28th February).
* If a Booking Reference has been provided, then the last record processed containing the Booking Reference will be imported. All other booking instances containing the Booking Reference will not be imported. However, the same Booking Reference can be used by two bookings on different bookable resources.

### Procedure

To map fields from your source data to Command Centre fields, complete the following procedure:

1. Click the **Mappings and Operator** tab.
2. Click **Configure**. The Edit Mappings window opens.

   This window displays the fields you defined on the Data Format tab (these fields originate from your source file) and all Gallagher Command Centre fields that can have data imported.
3. Select **Add or update** from the Cardholder mode drop-down list.
4. If you want to retain the cardholder's pre-existing Access Groups, select **Merge** from the Access Group mode drop-down list.
5. If you want to set Access Groups to the mapped Access Groups only, select **Replace** from the Access Group mode drop-down list.
6. To continue mapping source fields to Gallagher Command Centre fields, refer to the following topics:
   * [Creating an ID mapping](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/creating-a-cardholder-id-mapping.md)
   * [Creating a direct mapping](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/creating-a-cardholder-direct-mapping.md)
   * [Creating a transformation mapping](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/creating-a-cardholder-transformation-mapping.md)

### Removing cardholders

If the purpose of your interface is to remove cardholders, complete the following procedure:

1. Click the **Mappings and Operator** tab.
2. Click **Configure**. The Edit Mappings window opens.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f687615c4f6447d9a8a880612af1ec9a2c00c8f1%2Fedi_bookingexamplefile_2.png?alt=media)

   This window displays the fields you defined on the **Data Format** tab (these fields originate from your source data) and all Command Centre fields that can have data imported.
3. To continue mapping source fields to the Command Centre fields, refer to the following topics:
   * [Creating a booking ID mapping](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-booking-data/creating-a-booking-id-mapping.md)
   * [Creating a booking ID transformation mapping](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-booking-data/creating-a-booking-id-transformation-mapping.md)
   * [Creating a booking direct mapping](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-booking-data/creating-a-booking-direct-mapping.md)
   * [Creating a booking transformation mapping](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-booking-data/creating-a-booking-transformation-mapping.md)


---

# 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/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-booking-data.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.
