The Gold Standard of Anthropology | Community Metadata Revision, Takedown Requests and Versioned Provenance

1. Treat metadata as a claim with a history

Back to contents

A title, creator name, cultural group, place or rights statement is an assertion made by someone at a particular time. Record its source and confidence rather than presenting every field as timeless fact. Legacy descriptions may still matter as evidence of institutional practice, but they should not outrank a well-supported community correction in the public view.

2. Define who can request and who can decide

Back to contents

Publish a route for people depicted, creators, descendants, source communities, custodians and authorised representatives to submit a correction, contextual reply or access request. Verification should be proportionate: enough to protect against impersonation without demanding paperwork that marginalised contributors cannot reasonably provide. Separate the person receiving the request from the authority that makes contested decisions.

3. Distinguish correction, annotation, restriction and takedown

Back to contents

A spelling error may be corrected. A disputed interpretation may need multiple attributed statements. A culturally restricted recording may remain preserved but leave public access. A dangerous disclosure may require urgent takedown while review continues. These actions have different effects on discovery, citation, preservation and accountability; one generic “delete” button cannot carry them.

4. Version provenance without republishing harm

Back to contents

Keep an internal change log with the old value, new value, source, decision, date and responsible role. Public version notes can say that a harmful or inaccurate description was replaced without reproducing slurs, sacred knowledge or personal data. The goal is accountable change, not permanent exposure of every superseded phrase. Access to detailed history should follow the same cultural and privacy rules as the object.

5. Design a rapid and a deliberative path

Back to contents

Some requests require immediate temporary restriction: living-person safety, ceremonial material, precise site locations or intimate records. Other disagreements need consultation, research and time. Define an emergency hold with an expiry and reviewer, then a documented deliberative route. A temporary block should not silently become permanent, and slow procedure should not keep preventable harm online.

6. Worked example: a photograph with the wrong family name

Back to contents

A catalogue identifies a woman by the collector’s surname and labels the event as entertainment. Her granddaughter supplies family records and explains that the photograph shows a restricted mourning practice. The archive temporarily removes the image, verifies the relationship with community stewards and replaces the public record with the woman’s name, a community-authored context note and mediated access. The original catalogue card remains in a restricted institutional history file. The change repairs discovery without pretending the earlier error never occurred.

7. Make replies visible beside institutional description

Back to contents

When a community challenges a record, its response should not be buried in a downloadable report. Display attributed community context near the title and access decision, while making clear whether the institution accepts, disputes or is still reviewing a claim. Right of reply is not a comment box; it needs preservation, attribution, moderation and a route into the authoritative record.

8. Changed-context transfer check: a researcher deposits interviews

Back to contents

Move from a historical photograph to recently deposited interviews. The transferable needs are source attribution, correction routes, staged restrictions and version history. The changed context adds active consent agreements and living participants who may have reserved withdrawal rights. The repository must honour the actual agreement; it cannot import a museum policy that grants broader institutional discretion.

9. Know the limits and common misconceptions

Back to contents

Versioning does not mean every public reader should see every version. Takedown is not always erasure: search records, citations and backups may need a managed tombstone or restricted preservation copy. Community opinion may be internally contested, and the loudest requester is not automatically the authorised decision-maker. Legal rights, ethical duties and cultural authority overlap but are not identical.

10. Audit requests, decisions and restoration paths

Back to contents

Retain the request, scope, evidence reviewed, authority consulted, interim action, final rationale, affected systems, notification and review date. Map caches, derivatives, APIs and partner portals so a restriction propagates beyond the main page. Test restoration as well as takedown. A reversible workflow is safer than an undocumented manual deletion that no one can reconstruct.

11. Frequently asked questions

Back to contents

Should inaccurate metadata simply be deleted? Usually replace it visibly and preserve restricted provenance where lawful and ethical. Can anyone demand takedown? Anyone should be able to raise concern; decision authority still needs verification. Must every dispute be resolved to one statement? No. Can backups ignore a restriction? No; restoration procedures must preserve current access rules. What makes revision credible? Attributed evidence, community participation and a versioned decision trail.

12. The gold standard lets the archive learn without hiding its power

Back to contents

A responsible archive is neither frozen nor casually rewritten. It gives communities usable routes to correct, reply, restrict and appeal; records the institution’s decisions; and protects superseded harmful material from needless republication. The gold standard makes change governable. That is how an archive becomes capable of repair rather than merely capable of storage.