Template:Data Source Maintenance General Discussion

Discussion

When you use the dZ-Dot to put data into your dataZoa account, you are actually capturing a pathway to the data, so we can go back and look for changes. Capturing straight from the website is convenient, but websites can change and the pathways can disappear. When the pathway changes, you can use a dataZoa data migration tool to update the path to that data.

Importantly, you will be migrating from a path on a website to a (hopefully) more permanent path in a database behind the website, using the site's data access API.

Select Series to Migrate section

The first section of the migration tool helps you identify series that need updating in your dataZoa account. You can set various search criteria and get a list of possible candidates, or put in a specific series key, (like MyAccount/0003417).

Whenever you use the ListSeries button, dataZoa will generate rows of Series that match your current criteria. You can then use the PickSeries button on any of these rows to begin the actual conversion.

Set Parameters section

Once you have picked a series, you will set parameters that re-identify the data series at the source database. The details of this section vary widely based on the particulars of the data Series being converted.

You can often hover your mouse over action buttons and drop-down list items for handy further information.

dataZoa will examine the stored legacy path to suggest new path specifications. Often this will happen automatically, but there in some cases there will be a button to Auto-Suggest the parameters based on clues in the dataZoa series.

Data Comparison Columns section

When all of parameters are selected, you do a trial data fetch and examine the results. You can tweak parameters if needed and re-fetch. When you are satisfied that the trial fetch is right for the data series, you can Accept the Parameters and Commit to dataZoa.

The three data comparison columns show:

• The legacy Current data for this Series as stored at dataZoa.
• The proposed Trial data for this Series as it will be fetched with the current parameters.
• An optional <Raw Fetch/b> from direct from the data source, bypassing dataZoa, to help resolve any subtleties about the data as stored at the source.</li> </ul> </p> </div>