In my previous post on OEID, we saw how to quickly create an Oracle Endeca Information Discovery (OEID) application from a relational table, and use it for data exploration. Now suppose that during this exploration we discovered some questions that the existing data could not answer. The beauty of OEID is that you can add data to the existing application to help answer such questions. For that reason, today I will show you how to add an additional table to the existing application as a new data set, so you don’t have to make changes to the existing application.
Starting with the application we created in my last OEID post, the data showed what kind of leads different recruiting lead sources generated for an organization. A question may have come up, “What did it cost me to get those leads?” If I had the information, I could perhaps better allocate my budget to get the best bang for my recruiting buck.
Assuming the organization keeps data in another relational table that indicates what each of the lead sources charged per lead, the same steps as the previous post will show how to create a new data source that pulls from the table. Let’s see how we can add that to the existing application:
Open the application that was previously created, and click on the settings icon (the little “gear” on the top right corner) and choose “Application Settings.”
Once there, select “Data Sets” from the menu on the left.
Then click on the button on the right to add a “New Data Set.”
Assuming “LeadSources” is the Data Source that was created from the new table, select it to include in the application.
Make changes to the definition of the attributes being pulled from the Data Source and click “Done” to add this to the application. Notice the check box that says “Automatically create refinement rules.” This is OEID volunteering to automatically find the links between this new data set and the data set(s) that you have added to the application previously.
OEID Studio automatically creates a new tab/page that displays the data from the new data set. Here you see a chart that shows the number of leads that each type of source generated, and the average cost per lead for each source:
So how does this link up to the existing data set? Remember those refinement rules that OEID volunteered to create? Well say you wanted to narrow down the set of data to only the ones gotten via “Direct Marketing” efforts, hover the pointer over the value on the chart to tell you what the average cost was:
If you click on the graph at that point, you see on the left that the data set has been narrowed down to only “Direct Marketing” sources. The chart changes to show the different sources or efforts that fall under that category.
If you navigate back to the “Leads” page, you see that that data set was also narrowed down to the same value. How did this happen? This is one of the refinement rules that OEID automatically creates because it was able to find the common attributes between the data sets, based on name and data type.
In a future post, I’ll show you how to create or remove such refinement rules yourself, so you can fine tune the application, especially if the attributes are not named exactly the same. As usual, if you have any questions, comments, or need more information about OEID, feel free to leave a comment or send us a note at firstname.lastname@example.org.
Author: Andy Tauro, Performance Architects