Metadata profile instructions
=============================
Source: https://yenra.com/content-management-metadata/
Prepared October 4, 2026.

Open metadata-dictionary.csv and metadata-samples.csv as UTF-8 comma-delimited files.
The dictionary describes a small local training profile. The sample records
are fictional. Keep identifiers and subject codes as text; use ISO YYYY-MM-DD dates.
Sample rights placeholders must be resolved before any real publication.
review_owner, review_due and content_type are local workflow/profile fields.
DCMI mapping hints do not establish conformance to a complete external profile.
Required fields apply at the publication stage; related_id is optional.

Use the dictionary to agree meaning, allowed values and responsibility.
Required checks: unique IDs; required values; real calendar dates; allowed subject
and type values; appropriate language tags; resolving related IDs; verified rights.
Record the schema version and transformations applied during import/export.
Test a round-trip with two records before using a receiving system at scale.

Samples: HELP-001 is a procedure; HELP-002 is a form related to HELP-001.
Both use VISITS, en, 2026-09-20 modified and 2026-12-20 review due.
Rights: Example only; replace with verified rights.
Reference: https://www.dublincore.org/specifications/dublin-core/dcmi-terms/