Day-to-day operating brief
What Metadata Assistant (Description) work looks like in practice
A Metadata Assistant creates, maps or cleans descriptive data for library, archive or digital collections. Terms should cover schemas, element definitions, controlled vocabularies, identifiers, authority files, imports, crosswalks, validation, batch changes and public display. The assistant should not populate unknown fields with convenient defaults, run bulk transformations without a tested rollback or expose restricted administrative metadata through public mappings. Transformation logs should capture source field, rule version, affected count and validation sample before public release. Multilingual names, diacritics and non-Latin scripts need appropriate encoding and authority treatment; replacing them with convenient ASCII forms can reduce discoverability and misrepresent creators or communities. Authority work should record why a preferred name, date or subject heading was selected and preserve identifiers for variant forms. Batch changes require a review sample before publication because one mapping error can alter thousands of discovery records.
Individually written and reviewed against the maintained role record.