ANLY482 AY2016-17 T2 Group 2 Project Overview Data Source
| Background | Data Source | Methodology |
|---|
Data Source
To facilitate our analysis, Kaiso has provided us with datasets that consists of transaction data, concerts information data and customer demographics data.
- musical15.csv (contains musical transaction data made via phone booking from April 2015 till March 2016)
- musicalAug-Oct.csv (contains musical transaction data made via phone booking from August 2016 till October 2016)
- musicalrb.csv (contains musical transaction data made via phone and internet booking from 25 October 2016 till November 2016)
- concerts15.csv (contains concerts transaction data made via phone booking from April 2015 till March 2016)
- concertsAug-Oct.csv (contains concerts transaction data made via phone booking from August 2016 till October 2016)
- concertsrb.csv (contains concerts transaction data made via phone and internet booking from April 2015 till March 2016)
- Concerts_Master.csv (contains all concerts information for 2016)
- Concerts_Name.xlsx (contains all concerts information for 2015)
- data_cst.xlsx (contains information of registered customers of Kaiso Ticketing)
Musical data (before launch)
Two datasets were provided for this, the first one is a year-long dataset and the second dataset is a two months long dataset. These datasets contains every instance of transaction data for customer purchases for that time period. These purchases were made via phone booking only, part of the remote purchasing services. Musical purchases can be in the form of local musicals or overseas musicals.
For the year-long dataset:
| Data Field | Description |
|---|---|
| Account Number | The account number of the customer. |
| SoldDate | The date and time that the purchase was made |
| Product | Either Local or Overseas. |
| TicketAmount | The amount of the ticket that was purchased. |
| TicketType | The kind of ticket type. For example, "CAT1", "CAT2", "VIP BOX". |
| PerformanceDate | The date and time where the performance is held. |
For the two month long dataset:
| Data Field | Description |
|---|---|
| Dummy | The account number of the customer. |
| Time Attempt | The date and time that the purchase was made |
| Product Type | Either Local or Overseas. |
| Total Amount | The amount of the ticket that was purchased. |
| Type | The kind of ticket type. For example, "CAT1", "CAT2", "VIP BOX". |
| Performance Date | The date and time where the performance is held. |
| Seat Selection | Y means that the seat can be randomly allocated while N means that the customer wishes to choose the seat. |
Musical data (after launch)
This dataset contains every instance of transaction data for customer purchases. These purchases were made via phone and internet purchasing, part of the remote purchasing services. Musical purchases can be in the form of local musicals or overseas musicals.
| Data Field | Description |
|---|---|
| Account Number | The account number of the customer. |
| TicketStatus | Processing status of the purchase. A means that purchase has not been processed while S means that it has been processed. |
| Channel | I is for internet and V is for Phone. |
| SoldTime | The date and time that the purchase was made |
| Product | Either Local or Overseas. |
| TicketAmount | The amount of the ticket that was purchased. |
| TicketType | The kind of ticket type. For example, "CAT1", "CAT2", "VIP BOX". |
| PerformanceDate | The date and time where the performance is held. |
| Seat Selection | Y means that the seat can be randomly allocated while N means that the customer wishes to choose the seat. |
| Customer | ‘old’ means that it is not an old customer while new means that it is a ‘new’ customer. |
Concert data (before launch)
Likewise for concerts, two datasets were provided. The first one is a year-long dataset and the second dataset is a two months long dataset. These datasets contains every instance of transaction data for customer concert purchases for that time period. These purchases were made via phone purchasing only, part of the remote purchasing services.
For the year-long dataset:
| Data Field | Description |
|---|---|
| Account Number | The account number of the customer. |
| TSOpened | The date and time that the purchase was made |
| SelectionName | The exact selection of concert ticket. (e.g. CAT1 Seat 2) |
| TicketAmount | The amount of the ticket that was purchased. |
| Rating | Rating of the concert group |
| PerformanceDate | The date and time where the concert is held. |
| PerformanceName | Concert group name and code |
| ConcertType | The kind of ticket type. For example, "CAT1", "CAT2", "VIP Box" |
For the two month long dataset:
| Data Field | Description |
|---|---|
| Dummy | The account number of the customer. |
| Purchasing Time | The date and time that the purchase was made |
| SelectionName | The exact selection of concert ticket. (e.g. CAT1 Seat 2) |
| Total Amount | The amount of the ticket that was purchased. |
| Event | Concert group name and code |
| Market | The kind of ticket type. For example, "CAT1", "CAT2", "VIP Box" |
Concert data (after launch)
This dataset contains every instance of transaction data for customer concert purchases. These purchases were made via phone and internet purchasing, part of the remote purchasing services.
| Data Field | Description |
|---|---|
| Account Number | The account number of the customer. |
| TicketStatus | Processing status of the purchase. A means that purchase has not been processed while S means that it has been processed. |
| Channel | I is for internet and V is for Phone. |
| OTDSales | Y means that the customer bought the ticket on the spot while N means otherwise. |
| ConcertType | The kind of ticket type. For example, "CAT1", "CAT2", "VIP Box" |
| Rating | Rating of the concert group |
| SelectionName | The exact selection of concert ticket. (e.g. CAT1 Seat 2) |
| ConcertCode | Code of the concert. |
| TicketAmount | The amount of the ticket that was purchased. |
| TicketType | The kind of ticket type. For example, "CAT1", "CAT2", "VIP BOX". |
| PurchaseTime | The date and time where the ticket was purchased. |
| Customer | ‘old’ means that it is not an old customer while new means that it is a ‘new’ customer. |
Concert Group Data (after launch)
Two datasets were provided and both contains concert groups information. The first file is for concerts which were held before the launch of the internet channel while the second file is for concerts which were held after the launch of the internet channel. .
Concert information before launch:
| Data Field | Description |
|---|---|
| No. | Code of the concert. |
| GroupName | Name of the group which performed |
| Year | Year at which group performed |
Concert information after launch:
| Data Field | Description |
|---|---|
| ConcertCode | Code of the concert. |
| GroupCode | Code of the group. |
| ConcertDate | Date of the concert |
| ConcertTime | Time of the concert. |
| GroupName | Name of the group. |
| ConcertName | Name of the concert. |
Customer Demographics Data
This dataset consists of customer details for each registered customer of Kaiso:
| Data Field | Description |
|---|---|
| Dummy | The account number of the customer |
| Gender | The gender of the customer (Male or Female) |
| Nationality | The nationality of the customer. This is represented in country names (e.g. Singapore, Malaysia) |
| Age | The age of the customer. |
| New | 0 means that this is an old customer that registered before the launch of the online site and 1 means that this is a new customer. |
