Data schema

A schema states which fields a record can contain, which are required, what types they accept, and how records relate. A useful project schema also explains meaning: date might mean event date, while reviewDate describes editorial maintenance. Names alone do not supply that distinction. Before importing another catalog, compare its schema with yours and write a field map. Decide how to handle missing values, unsupported fields, conflicting identifiers, and different date precision. Test edge cases rather than only ordinary records. A schema can validate structure without validating historical truth, rights status, or the relevance of a source. Keep a small readable data dictionary beside formal rules so a future editor can understand why fields exist and how to create records that remain consistent with the collection.

Editorial review: 2026-09-23. New evidence may change this account.

Report a problem with this record