Glossary - G

Gender

This refers to the customer's legal gender, male or female.

GeographyLevels

The system uses three geography levels to define locations

• • Geography Level 1 - Country

  • Geography Level 2 - Region

  • Geography Level 3 - Resort

This can be used to pinpoint the location of different places, for example properties are each mapped to a geography level 3 so that the resort that each property is in is known; airports are each mapped to a geography level 1 so that the country they are in is known.

Each Geography Level 3 is associated to a single Geography Level 2. Each Geography Level 2 is associated to a single GeographyLevel 1. For example:

Geography Level 1

The Geography Level 1 is the Country. This is the geography level that covers the widest area. Each GeographyLevel1 has a name and ID.

For example

Geography Level 2

The Geography Level 2 is the Region. In size terms, it is smaller than Geography Level 1, which defined Countries, and larger than Geography Level 3, which defines resorts. Each Geography Level 2 has a name and ID and is mapped to a single geography level 1.

For example, the regions Costa Blanca, Costa Del Sol and Marmaris might all be set up in the system and associated with the country Spain.

Geography Level 3

The Geography Level 3 is the Resort. This covers the smallest area of the the three geography levels and therefore gives the most precise location. Each Geography level 3 has a name and ID. The IDs are allocated in the system when the geography levels are first set up. Each geography level 3 is mapped to a single geography level 2.

For example, the resorts Como, Menagio and Tremezzo might all be mapped to the region Lake Como in Italy:

Guest Details

This is a list of details of guests on a booking given in a prebook or book request. The guest details specify information like title, name, age and so on and assign a GuestID to each guest. In a basket book request, each component booking can specify which guests are on that booking by the guest ID, and the details of the guest can be given at the basket book level.

Guest ID

This is used to uniquely identify a particular guest in a list of guests. For example, the basket prebook request includes a list of guests with their details, so the first guest will have a guest ID 1, the second guest will have a guest ID of 2 etc. and it also includes a list of prebook requests, each of which can identify which guest in the basket prebook request is on that component using the guest ID.