Day-to-day operating brief
What Collections Information Officer (EMu/Modes) work looks like in practice
A Collections Information Officer administers museum databases such as EMu or Modes and supports documentation standards, reporting and data quality. Terms should cover user roles, object and party records, vocabularies, locations, imports, media, audit logs, bulk edits, migrations and public exports. The officer should not overwrite source data, grant broad access for convenience or release internal valuations and security fields through a public API. User support should distinguish a training issue from corrupted data, permission failure or system defect and route it accordingly. Before an upgrade, reports, labels, integrations and public collections pages need representative tests; successful login alone does not demonstrate that the museum's documentation workflows remain intact. Configuration changes should be tested against accessioning, loans, locations and public export before release. Where two legacy terms are merged, the migration note should preserve provenance and enable affected records to be identified afterwards.
Individually written and reviewed against the maintained role record.