An archive can contain accurate individual files yet still be confusing as a public collection. A final review should check links, labels, versions and the relationship between items. It is also a chance to catch material that has entered the public selection by mistake.

Checking an Art Project Archive Before Publication

Test the archive from the reader's starting point rather than from the organiser's familiar folder view. A clear internal structure does not guarantee a clear published route through it.

Agree who will look after the record after the activity ends. A collection can become difficult to use when staff leave, access accounts change or the meaning of filenames is lost. A brief handover should explain the structure, the permitted uses, the unresolved issues and the person or organisation responsible for future decisions. Check that the recipient can actually open the material.

A simple working sequence

1. Open the public index and follow a sample of complete paths.
2. Check descriptions, credits, dates and relevant access information.
3. Remove drafts or unresolved items from publication until their review is complete.

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.

See how the distinction matters

For example, a link labelled full interview might lead to an edited excerpt with no explanation. Correcting the label can be more important than adding more files to the collection.

Keep the working record close to the activity it describes. A short note made after a session can preserve a change of plan, an unresolved question or a participant's suggested adjustment more accurately than a polished account written much later. Separate observation from interpretation, and mark anything that needs checking before it becomes part of the public story.

A point that deserves care

Do not treat successful file upload as proof of successful publication. A document can open while still being the wrong version or missing essential context.

Use stable identifiers or clear filenames to connect related material. A photograph, recording, caption, permission record and final publication may all refer to the same contribution. The next person should not have to identify that connection from memory. Keep the structure understandable enough for a small team to maintain without turning routine documentation into a separate technical project.

Support a thoughtful process

Credit should reflect the work people actually contributed and the way they wish to be identified. Discuss this early enough for the final display, programme and online record to use a consistent approach. Do not assume everyone wants a full name made public. Equally, a collective label should not quietly erase the specific labour that made the project possible.

Keep the surviving record understandable beyond the original team's memory. A future reader needs the project's purpose, dates, context and relevant restrictions, as well as a selection of the material itself. Explain which parts are complete and which remain uncertain. This is especially important when a short-lived public activity is later encountered only through a website or archive.

Turn a finding into a decision that somebody can act on. If the invitation was difficult to understand, specify which part needs rewriting and test the new version. If a resource was missing, identify who can address it before the next session. A report that records every issue without changing the plan is less useful than a short review that leads to a clear improvement.

A clear point to build on

The final check should leave readers with an understandable collection and the team with a record of what was actually released.

Related reading

Writing Process Notes After an Art Workshop; Building a Timeline for a Participatory Art Case Study; Naming Files for a Small Art Project Archive.

Background and further reference

Library of Congress: identifying, organising and preserving digital material.