You must add a new data source when you have a new source of data
for the entity database.
About this task:
All results are a product of quality data. Getting data of high quality
into the entity database is therefore one of the most fundamental tasks, but
to do so requires significant analysis of the data and configuration .
Procedure:
- Identify the source of the data. It is critical to know where to
go for resolution of the data problems.
- Analyze the metadata. Every configured data source in the entity
database must have a unique identifier on its records, so that the entity
database can fully attribute all data back to its original source. Find the
field that will provide record uniqueness, and ensure that it is indeed unique.
- Use an acquisition program to transform the data from its native
format into UMF.
- Configure the data.
- Define a role for the data source.
- Configure the data source.
- Create any required number types.
- Create any required characteristic types.
- Review the resolution configuration, and customization if necessary.
- Configure new DQM rules.
- Validate the new DQM rules.
- Configure the role alert rules.
- Verify the data.
- Check that the pipeline started.
- Verify that the pipeline was able to use configured transports
and that it received UMF from the acquisition program.
- Verify that the acquisition node produced well-formed XML messages
by examining the .bad file.
- Verify that no UMF exceptions occurred as a result of invalid
mapping or configuration.
- Check for expected results by viewing the data source and load
summary reports.
- Search for one or more of the entities resolved using the visualizer.
- If applicable, examine role alerts.