Difference between revisions of "ANLY482 AY2016-17 T2 Group 2 Project Overview Data Source"

From Analytics Practicum
Jump to navigation Jump to search
 
(13 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
<!--Header Start-->
 
<!--Header Start-->
 
{|style="background-color:#6A8D9D; color: #F5F5F5; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |
 
{|style="background-color:#6A8D9D; color: #F5F5F5; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color: #F5F5F5" width="10%" |
+
| style="padding:0.3em; font-size:100%; background-color:#466675; text-align:center; color: #F5F5F5" width="10%" |
[[ANLY482 AY2016-17 T2 Group 2|  
+
[[ANLY482_AY2016-17_T2_Group_2|  
 
<font color="#F5F5F5" size=2><b>HOME</b></font>]]
 
<font color="#F5F5F5" size=2><b>HOME</b></font>]]
 
| style="background:none;" width="1%" | &nbsp;
 
| style="padding:0.3em; font-size:100%; background-color:#466675; text-align:center; color:#F5F5F5" width="10%" |
 
[[ANLY482 AY2016-17 T2 Group 2 Project Overview|
 
<font color="#F5F5F5" size=2><b>PROJECT OVERVIEW</b></font>]]
 
  
 
| style="background:none;" width="1%" | &nbsp;
 
| style="background:none;" width="1%" | &nbsp;
 
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |  
 
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |  
[[ANLY482 AY2016-17 T2 Group 2 Findings|
+
[[ANLY482_AY2016-17_T2_Group_2 Findings|
 
<font color="#F5F5F5" size=2><b>FINDINGS</b></font>]]
 
<font color="#F5F5F5" size=2><b>FINDINGS</b></font>]]
  
 
| style="background:none;" width="1%" | &nbsp;
 
| style="background:none;" width="1%" | &nbsp;
 
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |  
 
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |  
[[ANLY482 AY2016-17 T2 Group 2 Project Documentation|
+
[[ANLY482_AY2016-17_T2_Group_2 Project Documentation|
 
<font color="#F5F5F5" size=2><b>PROJECT DOCUMENTATION</b></font>]]
 
<font color="#F5F5F5" size=2><b>PROJECT DOCUMENTATION</b></font>]]
  
 
| style="background:none;" width="1%" | &nbsp;
 
| style="background:none;" width="1%" | &nbsp;
 
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |  
 
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |  
[[ANLY482 AY2016-17 T2 Group 2 Project Management|
+
[[ANLY482_AY2016-17_T2_Group_2 Project Management|
 
<font color="#F5F5F5" size=2><b>PROJECT MANAGEMENT</b></font>]]
 
<font color="#F5F5F5" size=2><b>PROJECT MANAGEMENT</b></font>]]
 +
 +
| style="background:none;" width="1%" | &nbsp;
 +
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |
 +
[[ANLY482_AY2016-17_T2_Group_2 About Us|
 +
<font color="#F5F5F5" size=2><b>ABOUT US</b></font>]]
 +
 +
| style="background:none;" width="1%" | &nbsp;
 +
| style="padding:0.3em; font-size:100%; background-color:#6A8D9D; text-align:center; color:#F5F5F5" width="10%" |
 +
[[Main_Page|
 +
<font color="#F5F5F5" size=2><b>ANLY482 HOMEPAGE</b></font>]]
 
|}  
 
|}  
 
<!--Header End-->
 
<!--Header End-->
Line 46: Line 51:
 
==<div style="background: #6A8D9D; line-height: 0.3em; font-family:helvetica;  border-left: #466675 solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Data Source</strong></font></div></div>==
 
==<div style="background: #6A8D9D; line-height: 0.3em; font-family:helvetica;  border-left: #466675 solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Data Source</strong></font></div></div>==
 
<div style="margin:20px; padding: 10px; background: #ffffff; text-align:left; font-size: 95%;-webkit-border-radius: 15px;-webkit-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96); -moz-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);">
 
<div style="margin:20px; padding: 10px; background: #ffffff; text-align:left; font-size: 95%;-webkit-border-radius: 15px;-webkit-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96); -moz-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);">
To facilitate our initial analysis, Kaisou has provided us with sample datasets that consists of some transaction data from November 2016. The three datasets given are namely the musical transaction data, concerts transaction data and customer profile data.
+
To facilitate our analysis, Kaiso has provided us with datasets that consists of transaction data, concerts information data and customer demographics data.
<br><br>'''Musical data'''<br>
+
# musical15.csv (contains musical transaction data made via phone booking from April 2015 till March 2016)
This dataset contains of every instance of transaction data for customer musical purchases. Musical purchases can be in the form of local or overseas.
+
# musicalAug-Oct.csv (contains musical transaction data made via phone booking from August 2016 till October 2016)
{|class="wikitable" width="60%"
+
# 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)
 +
</div>
 +
 
 +
==<div style="background: #6A8D9D; line-height: 0.3em; font-family:helvetica;  border-left: #466675 solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Musical data (before launch)</strong></font></div></div>==
 +
<div style="margin:20px; padding: 10px; background: #ffffff; text-align:left; font-size: 95%;-webkit-border-radius: 15px;-webkit-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96); -moz-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);">
 +
<p>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.</p>
 +
<p>
 +
For the year-long dataset:
 +
</p>
 +
{|class="wikitable" width="100%"
 
|-
 
|-
! width="15%" | Data Field
+
! width="30%" | Data Field
 
! Description
 
! Description
 
 
 
         |-  
 
         |-  
         ! Currency
+
         ! Account Number
| The currency the transaction was purchased in. Should be “SGD” for all transactions.
+
| The account number of the customer.
 
          
 
          
 
         |-  
 
         |-  
         ! AccDummy
+
         ! SoldDate
| The account number that purchased this transaction. This is being anonymised.
+
| The date and time that the purchase was made
  
 
         |-  
 
         |-  
         ! TicketStatus
+
         ! Product
| S is for Single and M is for Multiple.
+
| Either Local or Overseas.
 +
 
 +
        |-
 +
        ! TicketAmount
 +
| The amount of the ticket that was purchased.
  
 
         |-  
 
         |-  
 
         ! TicketType
 
         ! TicketType
| The kind of ticket type.  
+
| The kind of ticket type. For example, "CAT1", "CAT2", "VIP BOX".
 +
 
 +
        |-
 +
        ! PerformanceDate
 +
| The date and time where the performance is held.
 +
|}
 +
 
 +
<p>
 +
For the two month long dataset:
 +
</p>
 +
{|class="wikitable" width="100%"
 +
|-
 +
! width="30%" | 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.
 +
|}
 +
</div>
 +
 
 +
==<div style="background: #6A8D9D; line-height: 0.3em; font-family:helvetica;  border-left: #466675 solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Musical data (after launch)</strong></font></div></div>==
 +
<div style="margin:20px; padding: 10px; background: #ffffff; text-align:left; font-size: 95%;-webkit-border-radius: 15px;-webkit-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96); -moz-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);">
 +
<p>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.</p>
 +
{|class="wikitable" width="100%"
 +
|-
 +
! width="30%" | 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
 
         ! Channel
| I is for Internet and P is for Phone. We will use this column to differentiate which channel the transaction is purchased from.
+
| I is for internet and V is for Phone.
  
 
         |-  
 
         |-  
         ! MusicalDate
+
         ! SoldTime
| The date where the musical is held.
+
| The date and time that the purchase was made
  
 
         |-  
 
         |-  
         ! QuickPick
+
         ! Product
| Y means that the machine picked the number while N means that the customer picked the number.
+
| Either Local or Overseas.
  
 
         |-  
 
         |-  
         ! DrawNumber
+
         ! TicketAmount
| Unique number for each musical.
+
| The amount of the ticket that was purchased.
  
 
         |-  
 
         |-  
         ! Product
+
         ! TicketType
| 23 is local production, 9 is overseas production
+
| The kind of ticket type. For example, "CAT1", "CAT2", "VIP BOX".
  
 
         |-  
 
         |-  
         ! SettleDate
+
         ! PerformanceDate
| The settlement date for the purchase.
+
| The date and time where the performance is held.
  
 
         |-  
 
         |-  
         ! Selection
+
         ! Seat Selection
| Seat number that the customer selected.
+
| Y means that the seat can be randomly allocated while N means that the customer wishes to choose the seat.
  
 
         |-  
 
         |-  
         ! TicketDate
+
         ! Customer
| The date of purchase.
+
| ‘old’ means that it is not an old customer while new means that it is a ‘new’ customer.
 +
|}
 +
</div>
  
 +
==<div style="background: #6A8D9D; line-height: 0.3em; font-family:helvetica;  border-left: #466675 solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Concert data (before launch)</strong></font></div></div>==
 +
<div style="margin:20px; padding: 10px; background: #ffffff; text-align:left; font-size: 95%;-webkit-border-radius: 15px;-webkit-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96); -moz-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);">
 +
<p>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. </p>
 +
<p>
 +
For the year-long dataset:
 +
</p>
 +
{|class="wikitable" width="100%"
 +
|-
 +
! width="30%" | Data Field
 +
! Description
 +
 
         |-  
 
         |-  
         ! TicketTime
+
         ! Account Number
| The time of purchase
+
| 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
 
         ! TicketAmount
| The total amount from the purchase
+
| 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"
 
|}
 
|}
<br>
+
 
'''Concert data'''<br>
+
<p>
This dataset contains of every instance of transaction data for customer concert purchases.
+
For the two month long dataset:
{|class="wikitable" width="60%"
+
</p>
 +
{|class="wikitable" width="100%"
 
|-
 
|-
! width="15%" | Data Field
+
! width="30%" | Data Field
 
! Description
 
! Description
 
 
 
         |-  
 
         |-  
         ! Currency
+
         ! Dummy
| The currency the transaction was purchased in. Should be “SGD” for all transactions.
+
| The account number of the customer.
 
          
 
          
 
         |-  
 
         |-  
         ! AccountDummy
+
         ! Purchasing Time
| The account number that purchased this transaction. This is being anonymised.
+
| 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"
 +
|}
 +
</div>
 +
 +
==<div style="background: #6A8D9D; line-height: 0.3em; font-family:helvetica;  border-left: #466675 solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Concert data (after launch)</strong></font></div></div>==
 +
<div style="margin:20px; padding: 10px; background: #ffffff; text-align:left; font-size: 95%;-webkit-border-radius: 15px;-webkit-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96); -moz-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);">
 +
<p>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.</p>
 +
{|class="wikitable" width="100%"
 +
|-
 +
! width="30%" | Data Field
 +
! Description
 +
 +
        |-
 +
        ! Account Number
 +
| The account number of the customer.
 +
       
 
         |-  
 
         |-  
 
         ! TicketStatus
 
         ! TicketStatus
| A is for Active.
+
| Processing status of the purchase. A means that purchase has not been processed while S means that it has been processed.
  
 
         |-  
 
         |-  
         ! TicketType
+
         ! Channel
| The kind of ticket type.  
+
| 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)
  
 
         |-  
 
         |-  
         ! Channel
+
         ! ConcertCode
| I is for Internet and P is for Phone. We will use this column to differentiate which channel the transaction is purchased from.
+
| Code of the concert.
  
 
         |-  
 
         |-  
         ! LiveInd
+
         ! TicketAmount
| Y means that the purchase was on a live concert while N means otherwise
+
| The amount of the ticket that was purchased.
  
 
         |-  
 
         |-  
 
         ! TicketType
 
         ! TicketType
| The type of ticket
+
| The kind of ticket type. For example, "CAT1", "CAT2", "VIP BOX".
  
 
         |-  
 
         |-  
         ! LegStatus
+
         ! PurchaseTime
|  
+
| The date and time where the ticket was purchased.
  
 
         |-  
 
         |-  
         ! MarketName
+
         ! Customer
|  
+
| ‘old’ means that it is not an old customer while new means that it is a ‘new’ customer.
 +
|}
 +
</div>
  
 +
==<div style="background: #6A8D9D; line-height: 0.3em; font-family:helvetica;  border-left: #466675 solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Concert Group Data (after launch)</strong></font></div></div>==
 +
<div style="margin:20px; padding: 10px; background: #ffffff; text-align:left; font-size: 95%;-webkit-border-radius: 15px;-webkit-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96); -moz-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);">
 +
<p>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. .</p>
 +
<p>Concert information before launch:</p>
 +
{|class="wikitable" width="100%"
 +
|-
 +
! width="30%" | Data Field
 +
! Description
 +
 +
        |-
 +
        ! No.
 +
| Code of the concert.
 +
       
 
         |-  
 
         |-  
         ! Odds
+
         ! GroupName
|  
+
| Name of the group which performed
  
 
         |-  
 
         |-  
         ! SettleDate
+
         ! Year
| The settlement date for the tickets.
+
| Year at which group performed
 +
|}
  
 +
<p>Concert information after launch:</p>
 +
{|class="wikitable" width="100%"
 +
|-
 +
! width="30%" | Data Field
 +
! Description
 +
 
         |-  
 
         |-  
         ! SettleInfo
+
         ! ConcertCode
|  
+
| Code of the concert.
 +
       
 +
        |-
 +
        ! GroupCode
 +
| Code of the group.
  
 
         |-  
 
         |-  
         ! TicketDate
+
         ! ConcertDate
| The date of purchase.
+
| Date of the concert
  
 
         |-  
 
         |-  
         ! TicketTime
+
         ! ConcertTime
| The time of purchase.
+
| Time of the concert.
  
 
         |-  
 
         |-  
         ! ArtistCode
+
         ! GroupName
| The concert artist that the ticket belongs to
+
| Name of the group.
  
 
         |-  
 
         |-  
         ! TicketAmount
+
         ! ConcertName
| The total amount from the purchase
+
| Name of the concert.
 
|}
 
|}
<br>
+
</div>
'''Customer Profile data'''<br>
+
 
This dataset consists of each customer’s account number and the associated account details.
+
==<div style="background: #6A8D9D; line-height: 0.3em; font-family:helvetica;  border-left: #466675 solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Customer Demographics Data</strong></font></div></div>==
{|class="wikitable" width="60%"
+
<div style="margin:20px; padding: 10px; background: #ffffff; text-align:left; font-size: 95%;-webkit-border-radius: 15px;-webkit-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96); -moz-box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);box-shadow: 7px 4px 14px rgba(176, 155, 121, 0.96);">
 +
<p>This dataset consists of customer details for each registered customer of Kaiso:</p>
 +
{|class="wikitable" width="100%"
 
|-
 
|-
! width="15%" | Data Field
+
! width="30%" | Data Field
 
! Description
 
! Description
 
 
 
         |-  
 
         |-  
         ! ACCOUNTNUMBER
+
         ! Dummy
| Account number of the customer. Each account number is anonymised in the same way as the transaction datas.
+
| The account number of the customer
 
          
 
          
 
         |-  
 
         |-  
         ! GENDER
+
         ! Gender
| The gender of the customer.
+
| The gender of the customer (Male or Female)
  
 
         |-  
 
         |-  
         ! NATIONALITY
+
         ! Nationality
| The nationality of the customer
+
| The nationality of the customer. This is represented in country names (e.g. Singapore, Malaysia)
  
 
         |-  
 
         |-  
 
         ! Age
 
         ! Age
| The age of the customer
+
| The age of the customer.
  
 
         |-  
 
         |-  
 
         ! New
 
         ! New
| 0 means that it is not an old customer while 1 means that it is a new customer.
+
| 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.
 
|}
 
|}
 +
 
</div>
 
</div>

Latest revision as of 22:04, 19 February 2017


HOME

 

FINDINGS

 

PROJECT DOCUMENTATION

 

PROJECT MANAGEMENT

 

ABOUT US

 

ANLY482 HOMEPAGE

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.

  1. musical15.csv (contains musical transaction data made via phone booking from April 2015 till March 2016)
  2. musicalAug-Oct.csv (contains musical transaction data made via phone booking from August 2016 till October 2016)
  3. musicalrb.csv (contains musical transaction data made via phone and internet booking from 25 October 2016 till November 2016)
  4. concerts15.csv (contains concerts transaction data made via phone booking from April 2015 till March 2016)
  5. concertsAug-Oct.csv (contains concerts transaction data made via phone booking from August 2016 till October 2016)
  6. concertsrb.csv (contains concerts transaction data made via phone and internet booking from April 2015 till March 2016)
  7. Concerts_Master.csv (contains all concerts information for 2016)
  8. Concerts_Name.xlsx (contains all concerts information for 2015)
  9. 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.