Tip:
Highlight text to annotate it
X
Welcome back to Getting Started with Oracle Endeca Information Discovery v3.1.
In this screencast, we’ll go over the various data sources used for discovery applications.
In part 2 of this screencast series, one of the things we covered was that business users can create their own discovery applications to
explore data.
They can do this by loading their own data into Endeca Server from and Excel spreadsheet or JSON file
without any assistance from IT, quickly and easily.
So let’s begin there. Let’s say I am a business user who wants to explore the data in this
spreadsheet. It is warranty claims data from an automotive manufacturer.
I’ll log in as a business user and create a discovery application.
I’ll name it Warranty Claims, and provide a description.
My data source will be my own Excel file, so I’ll select Upload a File. I’ll go over the other options shortly.
Next I’ll browse to the location where my file is stored.
The system provides a preview of the file. If it is the incorrect file, I could browse to another file for upload.
Since this file is correct, I’ll click Next.
Notice I see the application name, data source, and data source type at the top of the page.
The attributes section allows you to control what attributes are included, and make some adjustments to the data,
before the upload is processed.
To keep this demonstration short, I ‘m going to upload the data ‘as is’.
Click Done and the system will create your discovery application based on this data.
When the application is ready, it will appear and you’ll see this pop-up box.
So in just a few minutes, I uploaded my data and created my own discovery application to explore it.
Let’s take a look at the application. We can see we are looking at the Claims data set within the Warranty Claims discovery application.
The default page includes a Search Box, Selected Refinements, Available Refinements, a Chart, and Results Table.
We can begin to investigate data immediately.
If you want, you can change the default values for the charts and table.
For example, I may prefer to see claims by Production Country, and then by model year.
In the Results table, I can quickly see the details of any record.
Or I can select the General view of the table.
Notice that the system automatically added a Record Id column so each record has a unique identifier.
The rest of the columns are in alphabetical order by column heading.
And as you saw in the previous screencast, you can filter the data by a particular term.
and sort the results.
In an upcoming screencast, you’ll see how to add more components and pages to your application for additional analysis.
In addition to spreadsheets and JSON files loaded by business users, administrators can provide available data from Oracle BI Server or
JDBC connections. Business users can then create applications based on this data if they have the proper permissions and access.
The third option is to create a discovery application from a pre-built Endeca Server.
Data can be loaded into Endeca Server using Integrator, as we discussed in Part 2 of this screencast series.
The Integrator Designer is an eclipse-based enterprise ETL tool that can extract data from any number of sources, and join,
transform, and enrich that data before loading it into an Oracle Endeca Server connection.
Oracle provides an Integrator ETL-based sample application that uses sales and product data from a fictitious bicycle manufacturer.
Detailed instructions on how to download the required materials and use Integrator to load and run the sample data pipeline can be found in the
Getting Started guide in our documentation.
As a business user, you can not only create your own discovery applications, you can also delete them.
In this screencast, you learned the various data sources available for discovery applications,
and saw a demonstration of a business user creating a discovery application by uploading data from a spreadsheet.
In Part 6 of this screencast series, you will learn about configuration,
and see demonstrations of how to make various configuration updates using Studio.