Upgrading Endeca Server data domains from 3.0 to 3.1

Question

Please explain the instructions mentioned below (link for reference where it is mentioned):
http://docs.oracle.com/cd/E40518_01/studio.310/studio_migration/toc.htm#Application%20data%20structure%20now%20uses%20data%20sets
When you upgrade Endeca Server data domains that were ingested using Integrator ETL, you will need to ingest the records into a single data set (referred to as a collection in Endeca Server and Integrator ETL) that has its key set to "Base". The display name can then be something to represent the actual content of the records.
Setting the data set key to "Base" allows any existing components that were tied to the Base view in 3.0 to be able to display the correct data.
What "key" we are referring here, is it collection key or view key. Also, which Integrator ETL version we are referring, is it 3.0.
I tried exporting the data domain from Endeca 3.0 and importing into Endeca 3.1 with default settings, it did not work.
Thanks in advance!

Answer 1

Correct.
Now, keep in mind that while this will get your data up to 3.1, it is very likely (assuming you have a production app) that you'll want to consider data model changes or other enhancements to take advantage of the new functionality.
Also, there are no more child data sources, so if your application used them, you'll want to consider separate datasets, not just a base dataset.