Documentation is not automatically publication
A research note, community archive, institutional catalogue, and searchable public website are different kinds of record. Agreeing to one does not automatically authorize the others. WIPO's resources on traditional knowledge and traditional cultural expressions discuss documentation as a process that can create benefits and risks, including unintended disclosure or use. UNESCO's inventory guidance likewise centers community involvement. Together, these sources suggest a basic working rule: decide purpose, audience, and access before collecting detail. A practice may be described in general terms for public understanding while its steps, names, places, or images remain restricted. A project should also allow the option of not recording information at all.
Ask what a record could make possible
A record can help a teacher pass on a technique, support community recognition, or preserve a memory. It can also make a location easier to exploit, expose a person who expected privacy, or separate knowledge from the obligations that govern its use. Ask who may benefit, who could be burdened, and how the information might be found outside its original setting. Consider search indexing, downloads, translations, screenshots, and copied metadata. These questions should be discussed with knowledge holders and relevant community decision-makers, not answered only by the archivist or editor. Risk assessment is not a prediction that harm will occur; it is a way to make choices visible before a record travels.
Use specific, revisitable consent
Explain what will be recorded, how it will be stored, who can access it, and which future uses are possible. Ask separately about audio, video, photographs, names, quotations, translation, and public release. A person may agree to an interview but decline an image, or approve a local archive while refusing open web publication. Keep the agreement linked to the resulting files and note its date, scope, and any conditions. Do not promise control that a platform cannot provide, such as guaranteed removal of every downloaded copy. Provide an accessible way to ask questions and change a decision. Consent should be a conversation that can be revisited, rather than a signature collected after a recording has already been made.
Design layers of access
An archive can separate a public summary from a detailed record, or share different views with different groups. A public page might describe a craft's community significance while omitting restricted steps or precise locations. An internal record may retain the full documentation under agreed controls, while a community-controlled copy remains outside the institution. Set access at the level of each file and metadata field, not just the folder. A photograph may reveal more than its caption; a filename may expose a location; a transcript may contain names absent from the public summary. Make review of derivatives part of the access plan. Technical controls should support the agreed relationship, though they cannot guarantee that every recipient will behave as intended.
Keep knowledge attached to its source and limits
When information is shared, preserve who supplied it, how they want to be credited, and what the record does not claim. A technique described by one maker should not be presented as universal for a whole community. A translation should identify who made it and whether key terms were left in the original language. If knowledge is collectively held, ask how collective attribution should work. Mark gaps and boundaries honestly. WIPO's documentation toolkit encourages careful consideration of objectives, stakeholders, and possible consequences before recording traditional knowledge. Traceable source information lets future users understand that a record is situated and governed, rather than free-floating material without a relationship.
Plan for reuse before a new use appears
An archive created for education may later be requested for a publication, exhibition, commercial product, training set, or machine-readable database. Do not assume the original agreement covers those uses. Keep a clear contact and review process, and consult the people or community authorities named in the agreement before adapting or redistributing material. A new context can change an image's meaning even when the file itself is unchanged. If contributors are no longer reachable, follow the project's ethical policy and the access limits already recorded rather than treating silence as approval. The more portable a digital file is, the more important it becomes to preserve its terms of use alongside the file.
Respond carefully to removal or correction requests
A person may ask to correct a name, reduce access, withdraw a quotation, or remove a file. Record the request, acknowledge it, and follow the agreed process promptly. Explain which copies the project controls and where limitations exist. A repository may retain an internal audit record while removing a public version, if that approach fits the agreement and policy. Do not expose the requester or repeat the sensitive information in a public explanation. If community decision-makers disagree about a request, pause the affected use and consult the governance process that was established for the project. Respectful response is easier when the project has planned for change instead of treating publication as irreversible.
Make the access decision findable
A restriction that exists only in an email or one staff member's memory will be lost. Attach access terms to the catalogue record, file metadata, derivative workflow, and handover documentation. Use clear labels such as public, community access, restricted, or not for reproduction only when those terms have been defined for the project. Identify who can approve a change and when the decision should be reviewed. Avoid vague labels that could be interpreted differently by a future vendor, researcher, or editor. If a file is copied into a new system, include the access information in the transfer package. The record should tell future caretakers what they may do without requiring them to guess.
Treat restraint as responsible documentation
A project does not fail when it decides not to publish a detail. A brief public entry can point to the existence of knowledge while respecting a boundary around its practice or circulation. UNESCO's community guidance and WIPO's documentation resources offer frameworks for participation and risk awareness, but the appropriate decision depends on the people and communities concerned. Preserve the decision, its rationale, and its review path. If circumstances change, return to the relevant knowledge holders before opening access. Responsible documentation is measured not by how much it reveals but by whether it serves an agreed purpose without severing knowledge from the relationships that sustain it.