Skip to main content

6.2. Address ingestion

address ingestion.png

The background colors of the above image are to be interpreted as:

  • purple: the core application a.k.a. backend that will be built in the context of this project
  • green: supporting systems that will be used in the context of this project
  • blue: trusted parties
  • red: external users of the system

In this chapter we will have a look on how addresses are populated in the register. We will discuss about two scenarios:

  • Addresses ingested via an ETL process
  • Addresses ingested via the vertical cabling data producers

We will also discuss how the process will be monitored and the cases for which an alert will be sent to the application administrators.

Address ingestion via data producers

It is important that Data Producers, which are in most cases Technicians performing vertical cabling interventions, are not blocked in any way when trying to contribute to the NRVC. Therefore we need to consider the cases on which a data producer needs to insert a dataset for an address that does not yet exist on the system.

It is important to make a distinction between addresses ingested via the data producers and addresses inserted / validated by the ETL process.

An address ingested via the data producers is not considered as being a validated address until it has been validated by ETL process against the addresses of the Address Data Producers

The data producers can initiate two different address ingestion processes, The first consists in creating an address for a site that does not yet exist on the system and the second one consists in creating an address to be linked to an existing site or block. Both processes are described below.

Processes

7.2. Create missing address process

7.3. Create missing address for existing site or block process

Address ingestion via the ETL process

7.4. Address ingestion via the ETL process

Monitoring and alerting

The monitoring system will have two tasks:

  • Monitor the health of the ETL process, making sure that the process runs with the right periodicity
  • Monitor the data quality of the NRVC address database

If the system detects that an address in the NRVC address database has a flag “validated = false” and is older than a defined threshold (e.g. 1 month), the system will trigger an alert to the Application Administrators and / or Data Approvers.

The Application Administrators and / or Data Approvers are then responsible for validating the data and take corrective actions (delete or correct the data)

No comments to display

Back to top