DIRECT ANSWER
Definition
AUMSearch normalization converts source-specific records into consistent fields without discarding their original meaning. Every published normalized value must retain its source record, native identifier, reporting context, and processing timestamp.
01
Field classes
| Class | Meaning | Example |
|---|---|---|
| Source-reported | Value supplied in the filing | Form ADV regulatory AUM |
| Source metadata | Value assigned by the source system | EDGAR accession number |
| Normalized | Consistent representation of a source value | Canonical date or state code |
| Calculated | Value derived by AUMSearch | Quarter-over-quarter change |
| Inferred | Relationship supported by evidence, not explicitly reported | Potential CRD-to-CIK mapping |
02
Normalization rules
- Retain the raw source value.
- Do not convert ranges into false point estimates.
- Store identifiers as strings where formatting matters.
- Separate report, filed, accepted, retrieved, and processed dates.
- Preserve amendments and supersession links.
- Version calculation logic.
- Display the field class and method when it affects interpretation.
03
Missing and unavailable data
Blank, not applicable, unavailable, and not reported are different states. AUMSearch should not replace them with zero unless the source definition explicitly says zero.
SRC
Primary sources
Definitions and regulatory claims on this page are grounded in the following official public resources.