Organising Audio Files from a Participatory Project
Audio files become difficult to use when names, versions and permissions are scattered across personal folders. A simple system should connect each file to its context without placing sensitive information in public filenames.
Organising Audio Files from a Participatory Project
Separate internal identifiers from the information shared with an audience. A useful file name does not need to contain a participant's full name or a private address.
Preserve an original copy of recordings and make edits on a separate working version. Keep a simple record of dates, locations at an appropriate level of detail, recording circumstances and permitted uses. This is not a substitute for a formal archive policy, but it helps prevent confusion between raw material, edited work and files prepared for public distribution.
Work through the essentials
- Choose a consistent naming system.
- Keep a separate record of context and permitted uses.
- Distinguish originals, edits and public versions.
Test sound in the actual listening situation. A recording that seems clear in a quiet room may be difficult to understand in a busy venue, while a speaker arrangement may affect people who are not choosing to listen. Consider placement, control and alternatives with the host. The listening experience includes the surrounding space, not only the audio file.
A worked scenario
A project can label recordings by session and file number, with access-controlled notes explaining the source. Public exports use only the information agreed for release.
Begin by distinguishing listening from recording. A project may invite attention to sound without needing to capture or publish it. When recording is proposed, explain the purpose and consider the people, conversations and places that may become identifiable. Use an appropriate permissions and review process rather than assuming that an audible sound is automatically available for every use.
Keep this limitation in view
Do not assume that a tidy folder is a complete preservation or privacy policy. Follow the host's arrangements for storage, access and retention.
Offer context without telling listeners what they must feel. A title, location description or short note about the method can help someone understand the work. Keep personal interpretations distinct from factual information about the recording. Different listeners may notice different details, and the project can make room for that variation without declaring one response the correct one.
Keep the project responsibilities clear
Review access arrangements through specific experiences rather than assuming that a well-intended plan worked for everyone. Ask what made joining or continuing easier and what remained difficult. Keep personal information appropriately protected, and distinguish an individual request from a general conclusion about a whole group. Use the feedback to improve the next version of the activity.
Plan the journey from conversation to public use before gathering a large collection. Decide where recordings, notes and agreed restrictions will be stored, who can access them and how a future request will be handled. A permissions note that cannot be connected to the correct recording is difficult to use, even when the original conversation was carefully organised.
Documentation has several possible audiences. The artist may need process notes, a partner may need a practical handover, and a visitor may need a concise explanation of the work. These are not automatically the same document. Prepare an appropriate public version rather than exposing every internal comment, contact detail and unresolved discussion in the name of transparency.
The practical result
Keep an organised collection where the right version and its handling conditions can be found together.
Related reading
Sound Maps as Situated Artworks; Field Recording for a Community Sound Project; Editing Field Recordings Without Losing Context.