Day-to-day operating brief
What Documentation Officer (Database) work looks like in practice
A Documentation Officer maintains the procedural and evidential framework for museum collection records. Terms should cover accession registers, catalogues, locations, loans, audits, numbering, authority files, documentation plans, backlogs, retrospective work and database quality. The officer should not make records appear complete through unsupported defaults, erase historic numbers or close discrepancies before objects and source documents have been reconciled. Documentation plans should assign priority by legal, location, access and preservation risk rather than chase the easiest volume totals. When retrospective research changes an object's identity, the prior attribution and sources should remain traceable so future users can understand why the catalogue conclusion changed. A backlog project should define minimum evidence, uncertainty notation and review status before data entry begins. Records created from old cards must remain distinguishable from facts checked directly against the object or accession documentation.
Individually written and reviewed against the maintained role record.