A release entry lists a date, but what does it date: the recording, the original issue or a later reissue? If the page does not say, a collector may repeat the wrong claim long before a correction reaches them. For an underground music archive, that distinction matters more than a finished-looking page.
Publishing pages before their evidence is ready
Archive material is rarely even. One Finnish thrash release may have a sleeve with full credits; another may be known only through a flyer and a partial track list. They should not appear equally well documented. Before launch, decide which fields each page type needs and which can be marked unconfirmed. A release entry might need a title, artist, format and an explanation of how its date was established. A concert entry must distinguish an advertised appearance from a performance known to have taken place.
Read every factual sentence as something another person might quote. Keep track of the sources for names, dates and credits. If sources disagree, say so rather than choosing the tidier version without explanation. An empty field or an uncertainty note is better than an invented detail.
Confusing a promising draft with a publishable record
Working notes, provisional spellings and questions for contributors belong in an editorial area, not on the public page. Check titles, headings, captions and metadata against the same evidence standard as the body text. A search result may show the title and description while leaving a careful qualification several paragraphs out of sight.
Launching an archive with no clear boundaries
Visitors need to know what the site covers. “Finnish thrash metal” does not say whether demos, related bands, shows outside Finland or later reissues belong in the archive. A short scope statement can set out the period and types of material covered, and distinguish established facts from community-submitted leads. It gives editors a basis for deciding where new submissions fit, too.
Avoid calling a catalogue “complete” when independent recordings and small shows may have left little documentation. Say what has been catalogued so far and how corrections are assessed. Then someone searching for a release can read an absent entry as a gap in coverage, not proof that the release never existed.
Designing navigation around the editor’s filing system
Editorial folders do not necessarily make sense to visitors. Someone may remember a band, a sleeve image or a festival name without knowing whether the relevant page sits under releases, interviews or local history. Before launch, try several routes from the homepage to a specific item. A band page should point to its documented releases and appearances; a release page should identify the artist and any related edition without sending the visitor back to search.
Check the section labels, not just the links. “Archive,” “Catalogue” and “Collection” say little if each leads to different material. Name sections for what they contain, and give pages titles that can be told apart in a list. If a recording has multiple editions, do not flatten them into one entry just to shorten the menu. Show the relationships on the pages rather than cramming every historical distinction into the navigation bar.
Ignoring rights until the site is public
Owning a record or flyer does not automatically give an archive permission to reproduce its cover, photographs, audio or written material online. Ask contributors who made the images they send, what permission they can grant and how they should be credited. Store permission records with the assets, not solely in an email inbox another editor cannot reach.
Set an image and audio policy before uploading a large collection. It can distinguish original archive photography, material used with permission and items documented through text alone. Do not post a full recording simply because it is hard to find elsewhere. A description of a scarce demo’s format and track list can help researchers without making the site an unauthorized source for the recording. For background on the protection of creative works, Britannica’s overview of copyright is useful; permission for a particular item still depends on the work and applicable law.
Skipping a rehearsal of ordinary visitor tasks
A homepage can look fine on an editor’s computer while basic tasks fail for everyone else. Test the public site on a phone and a desktop browser without an editor login. Try finding a band through the menu, opening a release entry, reading its credits and sending a correction. Enlarge the text, check keyboard focus and image alternative text, and make sure forms explain what happens after submission.
Test the less glamorous pages as well. Broken links, missing images and a search box that cannot find a known title quickly erode trust. If a cited flyer page has moved, its old address should lead somewhere useful rather than to a dead end. Redirect changed URLs where possible. Check the site again after deployment: a working staging preview does not prove that production files, settings and forms behave the same way.
Leaving correction channels untested
If the archive invites corrections, send one through the public form yourself. Verify that it reaches the right inbox and that the response reveals no other contributor’s personal information. Ask for the affected page and enough detail about the evidence to assess the correction, but do not require private contact details to appear alongside a public comment.
Making pages visible before choosing stable addresses
Links to band and release entries can end up in collectors’ notes, forum discussions and old messages. Changing those addresses after launch breaks those references. Choose readable URL patterns before announcing the site, particularly when artists share a name or a recording has multiple editions. Decide how aliases and alternate spellings will work, then use titles and cross-references so visitors can find a record by more than one route.
Give search previews a final look, without expecting instant search visibility. Important pages need distinct titles and descriptions that identify the actual band, release or event. Check that launch settings do not accidentally block pages meant to be public. Keep drafts with uncertain claims or material lacking permission unpublished, even if that leaves a category looking thin.
Having no maintenance plan for the first correction
Decide before launch who edits entries, who reviews submissions and how corrections are recorded. A brief dated note can explain a substantial revision; a routine spelling fix need not become an announcement. Keep backups, and test that they can be restored. An untested backup is only a hope of recovery.
Technical ownership needs to be just as clear. Record who controls the domain, hosting account and administrative access. Give editors individual accounts instead of a shared password, remove access when a role ends and use the account protections available. Those details determine whether the archive can still be maintained months after launch.
For the last pre-launch check, pick one real entry and follow it from the homepage to its sources, related pages and correction route. Put each failure in a shared log with an owner and a status. If that route contains a broken link—or a date that could mean either the original issue or a reissue—fix it before sharing the entry.
