We added consent language next to ancestral remains in Gallery 3 on Tuesday per the Jan 2024 NAGPRA rule, and it’s forcing tighter integration of provenance notes and community-approved context on case labels. How are your teams balancing precise object histories with protocol-driven descriptors after consultation, especially when accession records conflict with oral histories?
We’ve been handling the Jan 2024 NAGPRA-driven changes by using a two-line label: community-approved context first, then a dated note like “accession record (1932) states X; Nation oral history (2023) says Y,” plus a small “provenance under review” badge so visitors understand the tension. When space is tight (those Tuesday case-label swaps), we move the verbatim accession quote to a QR page and keep only the consultation language on the case.
We added a small “Sources” icon with a QR to a one-page provenance timeline, so the case text stays community-first but still shows where accession and oral histories diverge — Git for labels. Each update gets a plain note like “reconciled per consultation with [Nation], 2025‑11‑02,” and we include the consent wording by permission. Caveat: don’t rely on the QR alone; we mirror a one-sentence divergence note in print for accessibility.
Quick fix that helped us: after the Jan 2024 NAGPRA rule we added a date-stamped ‘consent verified’ line and a tiny ‘consultation outcomes’ card that puts community language first, and we label accession conflicts as ‘contested (1932 ledger)’ so they’re clear without overruling oral histories. For visitors who won’t scan, we stash the full provenance split with citations in a small gallery binder so the case stays clean — @fleming42 your QR timeline is smart, but phones are spotty in that wing, .