Overview Import

AgrEGG includes an administrative area for managing import expectations and descriptive information per Business Unit or data view. In the codebase this feature is exposed through the overview_import module.

Purpose

This area is useful when administrators need to define or review:

  • which periods a Business Unit is expected to cover;

  • when import-related rules start to apply;

  • which filter items are considered relevant for import monitoring;

  • reminder-related settings for missing imports or data coverage;

  • descriptive information associated with the reporting perimeter.

Main sections

The routes and models show two main functional areas:

  • Data View Import This stores operational import settings for a Business Unit.

  • Data View Information This stores structured descriptive information associated with that Business Unit.

These are related but distinct: one is operational import configuration, the other is business or reporting context.

Data View Import settings

The import configuration section can include information such as:

  • start and end periods;

  • data coverage start period;

  • initial periods tied to composer or validation rules;

  • selected KPI filter level and selected filter items;

  • rationale text for certain start dates;

  • special period sets used for specific workflows;

  • reminder timing related to missing imports or data coverage.

This makes the feature suitable for tracking the expected reporting perimeter over time rather than only storing a file upload rule.

Data View Information records

The information section appears to be intended for structured notes about how a Business Unit reports data.

From the model structure, this can include:

  • connectivity or operational context;

  • reported data characteristics;

  • claim or KPI definition details;

  • data coverage explanations;

  • business-specific notes used to interpret the imported data correctly.

In practice, this behaves like a maintained reference sheet for each reporting perimeter.

Administrative workflow

A typical workflow is:

  • open the list of configured Business Unit import settings;

  • create or update the import profile for a specific data view;

  • review selected filter items and period coverage;

  • maintain the corresponding descriptive information record;

  • revisit the settings when the reporting scope changes.

Operational effects

The code suggests that changes in this area can trigger operational consequences, including:

  • refresh activities for reported-data related structures;

  • period-based checks;

  • reminder logic for missing imports or incomplete coverage;

  • deconfirmation logic in some specialized workflows when controlled period sets change.

For that reason, this section should be treated as administrative configuration, not only documentation.