This page covers:
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
🔎 What is Catalog-Level Data?
Once Before you can start tracking your initiatives, goals, and results in Amp Impact is installed in your system, you need to create several records as the “backbone” of your system. Catalog-level catalog-level records. These records are almost like a library of options that users can select from and add to Amp Impact Projects as they create and manage Projectsthem. 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 these records them to their projects or initiatives.
| Info |
|---|
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 four three main types of catalog-level data in Amp Impact:
Reporting Periods: Reporting periods represent time periods during a project. The object is commonly used to manage grant reports or progress reports (including narrative, results, financials, and files). It is an important object for Indicator Management and also for Financial Management (every Financial must link to a Reporting Period for that project).
| Panel | ||
|---|---|---|
| ||
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). |
| Panel | ||
|---|---|---|
| ||
Disaggregation Groups allow users to define common ways that Indicators can be broken down into relevant smaller sets for more granular management and reporting. |
| Panel | ||
|---|---|---|
| ||
Thematic Area |
is a flexible term that can be defined according to how an organization categorizes its Projects/Grants/etc and/or their Indicators. This is often according to different sectors that the organization works in (for example, Education, Health, WASH, etc.). Sometimes the Thematic Area object is also used to define cross-cutting themes or strategic initiatives (for example, Gender Equality; Reduce Maternal Mortality). Thematic Areas can be nested in a parent-child hierarchy. It is also possible to define different types of Thematic Areas (for example, Sectors and Strategies) and differentiate them using the 'Type' field on the object. |
🔧 Setup & Design for the Catalog-Level Data
Amp Impact General Set Up & Configuration| Info |
|---|
Geographic Areas records (and Reporting Periodrecords) are required for Indicator Management and Financial Management features to function. Make sure that these records are set up and assigned to projects before continuing to enter targets, results, or financial data. For more details, review the Indicators, Targets & Results in Amp Impact and Financial Management in Amp Impact sections. |
📝 Find Your Way Around the Catalog-Level Data
Reporting Timelines: Defining and Setting Up Reporting Periods
Slice and Dice: Setting Up Disaggregation Groups & Disaggregation Values
Content Categorization: Defining and Setting Up Thematic Areas