Study guide
9.3 ARMA GARP Principles & Taxonomies
DAMA Certified Data Management Professional CDMP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & DMBoK Framework
1.1 CDMP Exam Details & Strategy 1.2 The DMBoK Framework 1.3 Data Management Organization & Roles
2 Chapter 2: Data Governance (Part A)
2.1 Data Governance Principles & Drivers 2.2 Operating Models & Structures 2.3 Policies, Standards, and Procedures
3 Chapter 2: Data Governance (Part B)
2.4 Data Stewardship 2.5 Governance Metrics & Implementation
4 Chapter 3: Data Modeling and Design (Part A)
Section 3.1: Conceptual, Logical, and Physical Models Section 3.2: ERD Notations & Relational Modeling Section 3.3: Normalization
5 Chapter 3: Data Modeling and Design (Part B)
3.4 Dimensional Modeling 3.5 Naming Standards & Modeling Best Practices
6 Chapter 4: Data Quality (Part A)
Section 4.1: Data Quality Dimensions Section 4.2: Data Quality Policy & Rules Section 4.3: DMAIC & DQ Improvement Lifecycle
7 Chapter 4: Data Quality (Part B)
4.4 Root-Cause Analysis & Remediation 4.5 DQ Metrics, Tools, and Reporting
8 Chapter 5: Metadata Management (Part A)
5.1 Business, Technical, and Operational Metadata 5.2 Metadata Lineage & Impact Analysis 5.3 Repository Architectures
9 Chapter 5: Metadata Management (Part B)
5.4 Standards and Semantics 5.5 Metadata Governance & Integration
10 Chapter 6: Master and Reference Data Management
6.1 Master vs Reference Data 6.2 MDM Repository Architectures 6.3 Match-Merge & Identity Resolution 6.4 Reference Data Governance & Standards
11 Chapter 7: Data Warehousing and Business Intelligence
7.1 DW Architectures: Inmon vs Kimball 7.2 Data Warehousing Storage & Load Patterns 7.3 BI Delivery & OLAP 7.4 Data Marts & Enterprise Data Warehouses
12 Chapter 8: Data Architecture
8.1 Enterprise Data Architecture & Zachman Framework 8.2 Data Flow Diagrams & Value Chains 8.3 Architecture Frameworks & Standards
13 Chapter 9: Document and Content Management
9.1 Records Management & ECM 9.2 Retention, Disposal, and E-Discovery 9.3 ARMA GARP Principles & Taxonomies
14 Chapter 10: Data Integration and Interoperability
Section 10.1: Integration Patterns & Technologies Section 10.2: Replication & Virtualization Section 10.3: Canonical Models & Integration Standards
15 Chapter 11: Data Security
Section 11.1: Security Principles: CIA Triad & Privacy Section 11.2: Access Control & Encryption Section 11.3: Security Regulations & Standards
16 Chapter 12: Data Storage and Operations
Section 12.1: Database Technologies & DBA Roles Section 12.2: Backup, Recovery, and High Availability Section 12.3: Performance Tuning & Operations
17 Chapter 13: Big Data and Data Science
13.1 Big Data V's & Technologies
18 Chapter 14: Data Ethics
14.1 DMBoK Data Ethics Framework
19 Chapter 15: Data Management Process and Maturity
15.1 Maturity Assessment Frameworks
9.3 ARMA GARP Principles & Taxonomies
Key Takeaways Explain This Topic AI
The Generally Accepted Recordkeeping Principles (GARP), developed by ARMA International, establish eight principles for governing corporate records.
A controlled vocabulary prevents search fragmentation by resolving synonyms, while a thesaurus maps equivalence, hierarchical, and associative relationships.
Faceted taxonomies allow multi-dimensional searches by categorizing content across independent attributes rather than a single rigid tree structure.
The Dublin Core Metadata Initiative (DCMI) defines 15 core elements that provide a standardized, domain-agnostic schema for digital resource description.
Last updated: July 2026
ARMA Generally Accepted Recordkeeping Principles (GARP)
To establish effective governance over records, organizations often adopt the Generally Accepted Recordkeeping Principles (GARP) , published by ARMA International (formerly the Association of Records Managers and Administrators). The Principles provide a framework against which an organization's records management maturity can be audited. The eight core principles are:
Accountability : A senior executive must oversee the records management program, delegate program operations to appropriate personnel, and ensure the program is audited regularly.
Transparency : The organization’s recordkeeping policies, procedures, and processes must be clearly documented and available to all stakeholders.
Integrity : The recordkeeping program must guarantee the authenticity, reliability, and security of records, ensuring they are free from unauthorized deletion, alteration, or falsification.
Protection : The program must safeguard private, confidential, proprietary, and classified information from unauthorized access, breach, or disclosure.
Compliance : The recordkeeping system and activities must conform to federal, state, and local laws, regulatory mandates, and internal corporate policies.
Availability : The system must ensure that records can be retrieved efficiently, timely, and accurately to support day-to-day operations and legal requests.
Retention : The organization must maintain records for the mandated duration determined by legal, regulatory, and business requirements, and no longer.
Disposition : The program must provide a secure, consistent, and documented process for the destruction or permanent archival transfer of records at the end of their lifecycle.
Taxonomy Design and Controlled Vocabularies
A taxonomy is a classification system that structures terms to represent relationships, serving as a primary tool for content search and retrieval. When designing a taxonomy for Document and Content Management (D&CM), organizations utilize different structural models based on their search requirements:
Flat Taxonomy : A simple list of terms with no parent-child relationships (e.g., tag clouds). Best for informal or small-scale tagging.
Hierarchical Taxonomy : A tree-like structure where child terms reside under a single parent node (e.g., Finance > Accounts Payable > Invoices). Easy for users to navigate but can force arbitrary placement when a term spans multiple domains.
Poly-hierarchical Taxonomy : A tree-like structure where a term can reside under multiple parent nodes (e.g., "Tax Filings" can reside under both "Finance" and "Legal").
Faceted Taxonomy : Classifies objects using multiple independent dimensions (facets). For example, a contract might be categorized across facets like "Document Type" (NDA), "Department" (HR), "Geography" (North America), and "Creation Year" (2026). This allows users to filter content dynamically.
Controlled Vocabularies and Thesauri
To ensure search consistency, organizations implement a controlled vocabulary , which is a curated list of authorized terms used for indexing and searching. Controlled vocabularies prevent search fragmentation caused by synonyms or spelling variations (e.g., ensuring all content about "automobiles" is tagged with the standard term "Motor Vehicles").
A thesaurus is an advanced controlled vocabulary that maps relationships between terms:
Equivalence : Maps synonyms to the preferred term (e.g., "Cars" USE "Motor Vehicles").
Hierarchical : Maps broader and narrower scopes (e.g., "Trucks" BT "Motor Vehicles"; "Motor Vehicles" NT "Sedans").
Associative : Connects conceptually related terms (e.g., "Motor Vehicles" RT "Traffic Laws").
Metadata for Content and the Dublin Core
Metadata (data about data) is the foundation of digital findability and lifecycle governance. In content systems, metadata is classified into three categories:
Descriptive Metadata : Supports search and discovery (e.g., Title, Creator, Subject, Abstract, Keywords).
Structural Metadata : Describes how digital objects are put together (e.g., page sequences, table of contents, document chapters).
Administrative Metadata : Facilitates system management and compliance (e.g., file size, format, access rights, retention codes, audit history).
The Dublin Core Metadata Initiative (DCMI)
The Dublin Core is a widely adopted, international standard for metadata description (standardized as ISO 15836). It consists of 15 core elements designed to describe resources across domains:
Element Description
Title The name given to the resource.
Creator The entity primarily responsible for making the resource (e.g., author, company).
Subject The topic of the resource, typically expressed as keywords or classification codes.
Description An account of the resource's content (e.g., abstract, summary).
Publisher The entity responsible for making the resource available.
Contributor An entity responsible for making contributions to the resource.
Date A point in time associated with an event in the lifecycle of the resource.
Type The nature or genre of the content (e.g., text, image, dataset).
Format The file format, physical medium, or dimensions of the resource (e.g., application/pdf).
Identifier An unambiguous reference to the resource (e.g., URL, DOI, ISBN).
Source A related resource from which the described resource is derived.
Language The language of the resource's intellectual content.
Relation A reference to a related resource.
Coverage The spatial or temporal topic of the resource (e.g., a specific region or era).
Rights Information about rights held in and over the resource (e.g., copyright, patents).