A festival poster shows that a Finnish thrash band was billed to play. It does not show that the gig happened. If one contributor writes the concert entry and another captions the poster scan, that distinction is easy to lose. Both need access to the evidence and to the decision about what it supports; otherwise, a documented announcement can quietly become an unsupported account of a performance.
Give the project a defined unit of work
“Research the scene” is too broad to assign or review. Give a contributor a specific item to produce: a release listing, concert entry, caption, interview excerpt cleared for publication, or correction to an existing record. The task should say what it covers, what evidence is already available, what remains in doubt, and who can approve the result.
For a discography entry, that might mean checking the title, format, track order, label as printed, and any uncertainty around the date. A history of the band’s sound belongs in a separate, sourced piece. Keeping the jobs apart lets someone finish a verifiable entry without settling every larger question first.
A short task card is enough:
- Record: the band, release, or event being documented.
- Deliverable: the entry or edit expected.
- Evidence: where to find the relevant scan, recording, publication, or correspondence.
- Open point: what still needs confirmation.
- Owner and reviewer: who drafts the entry and who checks it before publication.
That small bit of coordination can stop two volunteers transcribing the same cassette insert while a concert caption waits for review.
Make evidence usable by someone other than its finder
A shared folder full of files is not, by itself, a shared research process. Give each item a stable identifier and enough context to tell it apart from similar material. “flyer-final.jpg” tells a reviewer little. A catalogue record can note the printed title, apparent year, physical item or publication, who supplied the scan, and any limits on its use. Keep a link or file reference to the original alongside the working transcription.
In the notes, separate what a source says from what the team concludes. A sleeve can establish printed credits and track titles, but not necessarily the date of a recording session. A contemporary review documents a response to a release; its description of “classic thrash” is still that reviewer’s characterization. Keeping the distinction visible spares the next editor from having to reverse-engineer a polished paragraph.
When sources disagree, record the different readings and what supports each one rather than quietly picking a date. “The poster prints June 12; a later recollection gives June 13” is a useful internal note, even if the public entry says only “June.” Mark private correspondence clearly, too: permission to consult a message is not permission to quote or publish it.
Use stages that match editorial decisions
A task status should tell the team what happens next. One workable sequence is collected → transcribed → fact-checked → edited → approved → published. Use a separate “blocked” status and name the obstacle—an unreadable date, for example, or permission that has not been settled. “Almost done” gives the next person nothing to act on.
Give each record an owner, even if several people contribute evidence. The owner requests review and incorporates agreed changes; they do not get to overrule a reviewer’s objection. On a small team, one person may collect and transcribe, but someone else should check names, dates, formats, and quotations before publication.
Decide early which questions need specialist review. Wording drawn from Finnish-language material should go to a translator; claims about pressings or packaging need someone familiar with physical releases. An editor can settle a sentence-level disagreement. A disputed historical claim, though, should stay qualified or unpublished until the evidence supports it. That leaves routine copy edits out of long meetings without sidelining substantive objections.
Keep feedback attached to the claim
“Check the dates” is hard to act on. A useful review note names the sentence, the problem, and a next step: “The draft calls this the first issue, but the photographed insert has no issue number; remove ‘first’ unless another copy confirms it.” Reply in the task record so a future contributor can see the decision. If you remove a claim, keep the reason in the internal notes.
Protect contributors’ time and the archive’s boundaries
Underground music archives often rely on people with little spare time and uneven access to material. Set modest review windows and let contributors hand off tasks without apology. A short note covering what has been verified, what remains uncertain, and where the files are makes a handoff workable. Save meetings for decisions that cannot be settled in task comments, and circulate the disputed entries beforehand.
Access should match the job. A person editing a caption does not need the contact details of the musician who supplied the scan. Restrict private messages and unpublished recordings, document permission to reproduce material, and share only the excerpts needed for review. The archive can describe a release without distributing an unauthorized copy of its music.
Before assigning a batch of entries, try the process on one record. Ask someone who did not gather the material to find its evidence, check its claims, and identify the next action. If they cannot tell whether a gig date comes from a poster, a review, or a participant’s account, put that information in the record before the batch goes ahead.
