Browse Prior Art Database

System and method to derive business opportunities from NODATA

IP.com Disclosure Number: IPCOM000243760D
Publication Date: 2015-Oct-16
Document File: 4 page(s) / 30K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is the procedure to capture "NODATA" condition at database level by incorporating changes in database product. This is applicable for almost all online service industries like airline ticket, retail etc. It helps in capturing information about the situation for which the system is not capable for providing requested services.The proposal here is to capture such missed opportunities and provide information to BA/BI to make right decision while defining operation strategies

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 41% of the total text.

Page 01 of 4

System and method to derive business opportunities from NODATA

Disclosed is system and method to capture "NODATA" condition at database level by incorporating changes in database product as mentioned below:


1) System and method to flag the fields as NODATA fields, in a table, for columns which influence business decisions

2) Method to use a new clause- "FOR NODATA"- in base tables for columns that influence business decisions, as per point 1

3) Method to create a system defined NODATA TABLE in the background based on point 1

4) Method to capture the information for queries that return 0 results in a JSON (key:value) format using point 1 and 3

Let's consider an airline reservation system, where customers can login to the online portal and book their tickets. Now consider a situation, where, there are several customers trying to book a ticket for a particular route/time/window/fare range, but the airline doesn't have a service matching the request and respond "NODATA". As of now the conditions for "NODATA" are not captured anywhere whereas this can be a potential information for deciding flight operation strategies in future. It may be, increasing number of flights, deciding new routes and different fare offers. Hence, it is utmost important to capture such information.

This situation stands true for any kind of online service industry.

The proposal here is to capture such missed opportunities and provide information to BA/BI to make right decision while defining operation strategies. As the source of NODATA is database itself, it is but natural to implement this at database level to make it generic for all sorts of applications.

The suggestion is to incorporate changes in database product to capture the predicates (values in where clause of queries) of the queries which returns 0 records and hence the term NODATA. However, from business perspective it is recommended to capture only the NODATA information which helps in some business decisions and hence this suggests to flag only those fields in the database tables which will provide meaningful insights for taking appropriate business decisions.

As mentioned above, this is about:
- Fields in the base tables that influence business decisions to be marked using a column directive, "FOR NODATA".

- This will create a NODATA_TAB table in the database to capture NODATA situation
- This NODATA_TAB should capture the NODATA information in JSON (key:value) format

NODATA_TAB to have the following format:

[NODATA_TAB_XXXXXXXXXX] (
query_id serial,

1


Page 02 of 4

sql_query lvarchar,
execution_time datetime year to minute,

Nodata JSON )

Where 'XXXXXXXXXX' in the name above is a system defined unique id. The system catalog information for tables to contain an additional field to show the correlation between a base table and its corresponding NODATA table. This table is only created when a query hits the base table and returns 0 results.

When a query having NODATA FIELDS in predicates hits the databa...