> 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/booking-interface-configuration-examples.md).

# Booking Interface configuration examples

### Importing bookings from a source file

The following is a fictional example, showing how a source file, (e.g. CSV file) containing booking data will be imported into Command Centre.

The source file contains the following fields:

<table><thead><tr><th width="78">Reference</th><th width="66">Location</th><th width="114">Name</th><th width="78">Start Date</th><th width="78">Start Time</th><th width="84">End Date</th><th>End Time</th></tr></thead><tbody><tr><td>B1</td><td>Room 1</td><td>Room 1 Booking</td><td>03/12/2012</td><td>08:30:00</td><td>03/12/2012</td><td>09:30:00</td></tr><tr><td>B2</td><td>Room 2</td><td>Room 2 Booking</td><td>03/12/2012</td><td>08:30:00</td><td>03/12/2012</td><td>09:30:00</td></tr><tr><td>B3</td><td>Room 1</td><td>Room 1 Booking</td><td>04/12/2012</td><td>08:30:00</td><td>04/12/2012</td><td>09:30:00</td></tr><tr><td>B4</td><td>Room 1</td><td>Room 1 Booking</td><td>05/12/2012</td><td>08:30:00</td><td>05/12/2012</td><td>09:30:00</td></tr></tbody></table>

The data format for this Booking Interface is configured as shown:

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

**Notes:**

* The source file format type is "Delimited". The delimiter used is "Comma". A header row of "1" has been entered.
* The date format is "day/month/year". The time format is "24 hour".
* You can import the field names directly from the source file. To do so, click the **Field Import** button, then select the source file.

The mappings for this Booking Interface are configured as shown:

![](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)

**Note:** An ID transformation mapping from "Room 1" to the "Block A: Room 1" bookable resource item has been created. An ID transformation mapping from "Room 2" to the "Block A: Room 2" bookable resource item has also been created.

### Importing bookings from a Microsoft SQL database

The following is a fictional example, showing how booking data provided from the timetabling/booking system Syllabus Plus will be imported into Command Centre. The data provided specifies re-occurring bookings.

The source table contains the following fields:

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

The data format for this Booking Interface is configured as shown:

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

**Note:** You can import the field names directly from the source table. To do so, click the **Field Import** button.

The mappings for this Booking Interface are configured as shown:

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

For the Syllabus Plus data, the Interval Type has been configured as a wildcard transformation mapping to "Weekly". The Booking Name source field has been used as the Booking Name.

**Note:** If the Booking Reference is used, then all updates are applied to that booking, and are not new bookings.


---

# 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/booking-interface-configuration-examples.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.
