# Metadata Management Pack

Skill: `managing-metadata`

[Word report](report.en.docx) · [Excel register](register.en.xlsx)

## Record details

| ID | Field | Project value |
| --- | --- | --- |
| `artifact_id` | Artifact ID | |
| `project` | Project | |
| `skill` | Skill | |
| `version` | Version | |
| `date` | Date | |
| `status` | Status | |
| `author` | Author | |
| `owner` | Owner | |
| `approver` | Approver | |
| `purpose` | Purpose | |
| `business_outcome` | Business outcome | |
| `scope` | Scope and exclusions | |
| `source_inputs` | Inputs and sources | |
| `assumptions` | Assumptions and constraints | |
| `decisions` | Decisions | |
| `rationale` | Rationale | |
| `risks` | Risks | |
| `exceptions` | Exceptions | |
| `open_items` | Open items | |
| `due_date` | Due date | |
| `acceptance_criteria` | Acceptance criteria | |
| `evidence_location` | Evidence location | |
| `reviewer_decision` | Reviewer decision | |
| `next_gate` | Next stage gate | |

## Domain analysis and decisions

### Minimum metadata product (`metadata_product`)

Define minimum useful capabilities from discovery, understanding, and impact-analysis tasks.

> Enter project evidence, conclusion, and owner.


### Sources and consumers (`source_inventory`)

List technical, business, and operational metadata sources and users.

> Enter project evidence, conclusion, and owner.


### Metamodel and architecture (`metamodel`)

Choose centralized, distributed, or hybrid design with IDs, relationships, and sync ownership.

> Enter project evidence, conclusion, and owner.


### Business glossary (`glossary`)

Record definition approval, synonyms, disputes, versions, and effective dates.

> Enter project evidence, conclusion, and owner.


### Designed and actual lineage (`lineage`)

Separate designed mappings from observed runs and trace fields to consuming outputs.

> Enter project evidence, conclusion, and owner.


### Quality freshness and coverage (`freshness`)

Define refresh deadlines, coverage denominators, quality rules, and adoption measures.

> Enter project evidence, conclusion, and owner.


### Impact analysis and change gate (`impact_analysis`)

Trace schema or term changes downstream and set review gates.

> Enter project evidence, conclusion, and owner.


### Permissions and acceptance (`acceptance_evidence`)

Verify sensitive-metadata access, discovery tasks, and lineage evidence.

> Enter project evidence, conclusion, and owner.


## Working registers

### Business Glossary (`glossary`)

Maintain term definitions and approval ownership.

| Term (`term`) | Definition (`definition`) | Source (`source`) | Owner (`owner`) | Approver (`approver`) | Version (`version`) | Status (`status`) |
| --- | --- | --- | --- | --- | --- | --- |
|   |   |   |   |   |   |   |

### Field Lineage (`lineage`)

Trace field source, consumers, and implementation evidence.

| Source field (`source_field`) | Target field (`target_field`) | Transformation (`transformation`) | Consumer (`consumer`) | Owner (`owner`) | Evidence (`evidence`) | Review date (`review_date`) |
| --- | --- | --- | --- | --- | --- | --- |
|   |   |   |   |   |   |   |