1
Describe the asset
Capture identity, purpose, domain, location, owners, consumers, and operational context.
Practical governance tool
Build a useful starter data catalog without unnecessary complexity
Document datasets, tables, reports, APIs, models, and data products with ownership, classifications, lineage notes, quality status, access conditions, and review details.
No external data services.Results use deterministic rules and depend on user-supplied information. They do not replace governance, legal review, security validation, or data-quality testing.
How it works
Start with one important asset, assess completeness, then expand and export the local catalog.
2
Review governance metadata
Record sensitivity, personal-data status, access, lineage, quality, retention, and assurance.
3
Prioritise and export
Use completeness and duplicate checks, then export CSV or JSON locally.
Catalog entry builder
Required fields are marked with an asterisk.
Local multi-entry catalog
Add the current record, import local CSV, check duplicates, filter, and export. Records remain in this browser tab unless downloaded.
Use the exported headers. Maximum 100 records and 2 MB.
No local catalog records added.
| Asset | Type | Domain | Owner | Sensitivity | Quality | Completeness | Duplicate | Action |
|---|---|---|---|---|---|---|---|---|
| No entries yet. | ||||||||
Methodology, limitations, and use
Treat the result as a structured metadata review, not proof that an asset is accurate, compliant, secure, or fit for every purpose.
Method
Fixed weights total 100 points. A valid, non-empty field receives its full weight. No hidden adjustment is used.
Limitations
The tool does not inspect systems, validate lineage, test data quality, assess legal obligations, or confirm access enforcement.
Practical use
Prioritise low-scoring and high-risk assets, assign owners, standardise descriptions, confirm classifications, document access, and schedule reviews.
Related tools
Frequently asked questions
What is a data catalog starter?
A lightweight structure for documenting important assets before adopting or expanding a formal catalog.
Which asset types can I document?
Datasets, tables, reports, APIs, analytical models, and data products.
How is completeness calculated?
Fixed weights are applied to twenty metadata fields and totalled as a percentage.
Does the score measure data quality?
No. It measures metadata completeness.
Is entered information sent externally?
No external service or API is used.
Can I import existing records?
Yes. Download the CSV template and preserve its headers.
How are duplicate records identified?
Matching normalized asset name, type, and domain combinations are flagged.
What should I enter for location?
Use a safe schema, report path, API route, repository reference, or governed URL. Never include secrets.
What does certification status mean?
An internal assurance or lifecycle label governed by your process.
How often should entries be reviewed?
According to criticality, sensitivity, change rate, and policy.
Can this support implementation?
Yes. Exports can support metadata requirements, ownership remediation, migration, and onboarding.
Should every field be completed?
Not necessarily, but inapplicable fields should follow a documented convention.