Catalog-Level Data
- Harshula Jhala
- Wilmarié Moreland
This page covers:
What is Catalog-Level Data?
Before you can start tracking your initiatives, goals, and results in Amp Impact, you need to create several catalog-level records. These records are like a library of options that users can select from and add to Amp Impact Projects as they create and manage them. Typically, there will only be a handful of users with the permissions to create and modify these catalog-level records, while the majority of users in the system will have the permissions to assign them to their projects or initiatives.
System Administrators (or a set of Super Users) often upload these catalog-level records into the system in bulk (using a data loading tool). This allows them to align on the options in the catalog (and the hierarchy of records if applicable) before making the options available to other users in the system to assign to their projects.
Catalog-Level Data Setup Structure
There are three main types of catalog-level data in Amp Impact:
Geographic Areas store a list of geographies that can be assigned to projects to indicate where the project is being implemented. Depending on the organization, this may be a list of global geographies (regions, countries) or more granular ones (states, provinces, districts, or even villages). Geographic Areas can also have a parent-child hierarchy (through the self-lookup on the object).
Disaggregation Groups allow users to define common ways that Indicators can be broken down into relevant smaller sets for more granular management and reporting.
For example, it is possible to create a Disaggregation Group called Age Group and then break down Targets and Results for specified indicators into different age brackets.