A promoter has found a scanned flyer for a Finnish thrash gig. Does the archive want it? Should they send the scan straight away, or describe it first? An email address answers none of that. A good contact page tells a first-time visitor what the archive can consider and how to make a useful enquiry.
That enquiry could come from a former band member correcting a credit, a collector identifying a cassette variant, a researcher checking a citation, or a festival organiser asking about a historical photograph. Each needs a slightly different route. None should mistake making contact for a promise of publication, research help or permission to reuse material.
Say who should get in touch—and about what
Put the archive’s scope near the top, in ordinary language. For example: “Contact us about documented Finnish thrash releases, shows, flyers and scene material from the late 2000s to the mid-2010s.” That does more work than “We’d love to hear from you,” and lets someone with an unrelated request see the mismatch before writing.
Then give a few concrete reasons to get in touch. The categories should leave room for unexpected evidence while helping senders describe what they have:
- Corrections: a disputed release credit, venue name, date or attribution on an existing page.
- Source material: flyers, ticket scans, release inserts, photographs or firsthand documentation that may help verify a historical entry.
- Rights and reuse: questions about material displayed by the archive, including requests to remove or correct an attribution.
- Research enquiries: questions tied to a particular entry or clearly identified subject.
Describe what the archive can reasonably consider, not services it cannot provide. If volunteers cannot identify recordings from audio clips or handle open-ended genealogy requests about bands, say so. A clear limit saves both sides time.
Distinguish evidence from a request for publication
Someone who owns a flyer may assume that sending it means the image will appear online. Separate submission from editorial review: “We review submitted material for relevance, provenance and permission before deciding whether to use it.” That leaves room to ask where the item came from and whether the sender can authorise its use.
Underground music history often depends on incomplete evidence. A recollection may be valuable without settling a disputed date; a photograph may show a performance without identifying its photographer. Ask contributors to say what they know and what they cannot verify, rather than treating every memory as a settled record.
Give visitors a route that suits the enquiry
A form helps when it asks for information the archive genuinely needs. Email may suit a complicated correction or an initial discussion about a set of documents. If you offer both, explain which to use: perhaps a form for straightforward corrections and general questions, and a dedicated email address for rights concerns. A row of unexplained addresses makes that choice harder.
Make the route easy to find. “Contact” is clearer as a navigation label than an inventive name that could mean several things. A reader should also be able to reach the page from an archive entry while the disputed detail is still in view. Information buried only in the footer is easy to miss on a phone.
Do not make a social media account the only way in. Platforms change, messages get missed, and former scene participants or collectors may not use them. Keep a stable form or email route independent of any particular platform.
Ask for enough detail, not a dossier
A general form needs little more than a name, reply address, enquiry type, subject and message. A correction form can also ask for the URL or title of the entry. Use the message prompt to suggest evidence without making every detail mandatory: “For a date correction, please include the date shown on the page, the proposed correction and the source you used.”
Requiring a phone number, home address, band affiliation and several attachments from everyone adds work and collects details the archive may not need. Mark a name as optional if it is; if an email address is needed only for a reply, say so. A shorter form is easier to use on a phone or with assistive technology.
For submissions, the prompts can reflect the object:
- Flyer or ticket: where it was obtained, whether the date and venue are legible, and whether the sender can provide a clear scan.
- Release scan: the format, visible credits and identifying marks that distinguish versions.
- Photograph: the event or approximate period, the photographer if known, and whether permission to display it has been established.
- Correction: the exact sentence or entry at issue, with a source supporting the proposed change.
These are prompts, not tests. A useful item may have an uncertain history. Its owner should still be able to explain what is known and what remains unclear.
Make the next step visible
After someone submits a form, confirm that the message was sent; do not simply clear the fields. An automatic email can acknowledge receipt, but it should not imply that a person has reviewed the material.
Only give a response-time estimate the archive can meet. “Messages are reviewed by volunteers; replies may take several weeks” is better than an unreliable 24-hour promise. If some submissions will not receive a personal reply, say so before people write. Give rights and privacy concerns a clearly identified route so they do not disappear among routine research suggestions.
Explain what may happen next. Will you ask permission before publishing a photograph? Check a proposed correction against other sources? Let a contributor request credit or remain unnamed in a public note? Put those answers on the contact page or in a clearly labelled policy available from it—not in a surprise follow-up after files arrive.
Handle large files without making uploads the default
A public form need not accept full-resolution scans or audio. Large files can fail on slow connections or fill storage; an open upload field may also encourage people to send copyrighted recordings the archive cannot distribute. Let a contributor describe the item first, then arrange a suitable transfer if it is relevant and permission is clear.
If attachments are allowed, put accepted file types and the size limit beside the upload field, along with instructions for files that exceed it. Do not ask people to shrink a scan until dates, credits or handwritten notes become illegible. Nor should they need to upload an entire release to ask about a sleeve credit; a legible image of the sleeve may be enough.
Make privacy and consent understandable
Even a simple contact form collects personal information. At the point of submission, say why you collect the reply address and message, who handles them, and how long they are kept or what determines retention. A separate privacy notice can hold the fuller detail.
Evidence can contain personal information too. A backstage photo, old email thread or handwritten note may identify people who never agreed to publication. Ask senders not to include private correspondence or third-party details unless they are relevant and permitted to share. Receiving an item does not give the archive the right to publish every part of it.
Avoid hidden, sweeping claims over submitted files. Explain that sending material allows the archive to review it, while publication or reuse will be discussed separately where needed. Owning a physical cassette or print, after all, does not necessarily mean owning copyright in its artwork or photograph.
Write for someone who has not met the archive
Longtime scene participants may recognise a band nickname or venue abbreviation; a new visitor may not. Lead with plain terms and use scene-specific ones when they add precision. If entries use Finnish names or diacritics, the form must accept them unchanged. Someone reporting a misspelling needs to show the spelling they mean.
Use descriptive labels and keep instructions easy to scan. “What is your message about?” says more than “Category.” Show an example beside any field with a required format. Errors should identify the field and problem without relying on colour, and preserve what the visitor has already typed. No one should have to rewrite a detailed account because they missed one field.
Test the page with a keyboard as well as a mouse. Focus should follow a sensible order, every field should have a label, and the submit button should be recognisable. On mobile, instructions and confirmation messages should remain readable without horizontal scrolling. Otherwise, useful corrections can be lost before they are sent.
Check whether the page earns useful replies
Treat the contact page as an editorial tool, not just a working form. Look at the questions that come in. Repeated enquiries about flyer scans suggest the submission guidance is too hard to find. Corrections that omit the entry name call for a title or URL prompt. If files routinely arrive before permissions have been discussed, bring that guidance closer to the form.
A periodic check can catch quieter problems:
- Send a test message from a phone and a desktop browser.
- Confirm that it reaches the address the archive actually monitors.
- Read the acknowledgement as a first-time sender would.
- Check that the privacy wording, response-time estimate and file limits match current practice.
- Review a small sample of enquiries for recurring confusion, without retaining personal details unnecessarily.
More messages are not necessarily better. Fewer, better-described corrections may be more useful to a historical archive than a flood of vague enquiries. What matters is whether people can explain why they are writing and whether the archive has enough information to respond.
Try the page yourself from an entry with an uncertain concert date, without relying on what you already know about the site. Can you identify the entry, propose a date, cite a flyer or other evidence, and get a clear acknowledgement? Wherever you have to guess, revise the instruction or field before the next correction arrives.
