A reader spots a demo listed as a 2011 release and asks: was it recorded that year, or just issued then? The answer may be in a sleeve scan, a label catalogue, or a note from whoever submitted the entry. If those sources are scattered across inboxes, an editor has to piece the evidence together before replying. Keep the sources and the editorial decision together, and the archive can answer without guessing—or correct the listing if it needs correcting.
For a Finnish thrash-metal archive, “customer experience” has little to do with a sale. It is what listeners, collectors, musicians, and researchers encounter when they consult a listing or get in touch. Behind that experience is a repeatable process for receiving material, checking facts, making decisions, and publishing changes. When it works, credits are dependable, editions are easier to tell apart, replies are useful, and corrections do not quietly erase earlier mistakes.
Make a submission usable before it reaches an editor
Independent releases often come with patchy documentation. Someone may remember a gig where a CD-R was sold but not know whether the recording had circulated earlier. Another contributor may own a copy with a printed year but no recording dates. A submission form needs room for both accounts; a single “release date” box cannot carry that distinction.
A useful intake record separates the claims an editor may need to check:
- What the item is: band, title, format, track list, and any edition or catalogue identifier visible on the copy.
- What each date means: recording, first issue, reissue, and performance dates, where applicable.
- Where the information came from: sleeve, insert, label documentation, contemporary announcement, or a named contributor’s recollection.
- What may be shared: permission to publish a submitted photograph, scan, quotation, or contact credit.
- What remains uncertain: an explicit note rather than an empty field that could later be mistaken for oversight.
Visitors need not fill out a long questionnaire. A short public form can collect the essentials; the internal record can hold follow-up questions and evidence. Contributors then need not repeat details they have already supplied. Later, a reader can see what is actually known about a pressing rather than finding an ambiguous year presented as fact.
Give each claim a path to publication
An enthusiastic correction is not necessarily a supported one. A shared workflow gives each proposed change a few clear states: received, awaiting evidence, under review, ready to publish, and published. One editor should own the next action, even when several volunteers help with research. Otherwise, the same question can linger in multiple inboxes, each person assuming someone else has it.
Distinguish evidence from interpretation
“The insert prints 2012” describes something visible on the copy. “This was the band’s first release” calls for a wider discography check. The distinction matters with late-2000s and early-2010s underground recordings: an early demo, a later self-issued disc, and a digital upload may share tracks or artwork. An editor can confirm what the insert says without accepting the broader claim.
Before publishing, check names and dates against the sources at hand, then make sure the wording does not claim more than they support. If two credible sources disagree, describe the disagreement or qualify the date. Record the decision internally, too: what changed, what supported it, and who reviewed it. The next person asked about the entry should not have to start the investigation over.
Route enquiries by the action they require
A typo report is not the same job as examining a rare insert someone offers to lend. Nor should a request to remove an image sit in the same queue as a question about a band’s European tour history. Sorting messages by the action they require helps an archive reply promptly without pretending every research question can be settled at once.
- Simple correction: verify the reported detail and update the entry, or explain why the existing wording stands.
- Research question: say what the archive can check, and distinguish a documented answer from an unverified lead.
- Rights or privacy concern: restrict access to the disputed material while its permission status is reviewed.
- New material: record its source and what the contributor permits the archive to publish.
A quick acknowledgement can name the item and the next action without promising a completion date the archive cannot meet. Reader reports can also expose a recurring problem. If several edition dates have been confused with recording dates, review related listings instead of fixing each report as an isolated typo. The companion post on turning archive feedback into better listings and records looks at that wider use of feedback.
Protect the experience when work is handed off
In a volunteer archive, intake, research, editing, and publication may pass through different hands. “Fix the date” gives the next person almost nothing to work with. A useful handoff names the entry, quotes the proposed change, identifies its source, notes any permission limits, and states what remains unresolved. The contributor should not have to tell the story again because an internal note was too thin.
Private material needs a firm boundary. An email from a musician may help an editor investigate a credit without becoming a public citation or a searchable contact record. Keep contact details separate from publishable notes, restrict access to those handling the enquiry, and record permission before using images or quotations. A convenient internal file is no reason to expose correspondence.
Measure friction, not just output
A count of new entries says little about whether visitors get useful answers. Once a month, a small archive could check how many enquiries have no owner, how often editors ask for information already supplied, how long permission concerns remain unresolved, and which fields draw repeated corrections. These are signs of friction in the process, not a scorecard for volunteer productivity.
Suppose three readers question dates on separate CD-R listings. An editor might find that older notes supplied only one “year” field, leaving recording and issue dates muddled. The fix is to separate those dates in the internal template, then review affected entries before changing the public wording. At the next editorial check-in, open one unresolved date query: can the team see its source, who owns it, and what happens next?
