A concert flyer shows that a Finnish thrash band was advertised for a particular night. It does not prove the band took the stage. That distinction can disappear when a listing finds its way into a biography and is repeated in a festival history. To keep the record straight, an archive needs to retain the evidence behind a claim—and note what that evidence cannot tell us.
As an archive grows, the same facts turn up in more places. A release date might appear in a discography, a band profile and a local-scene feature. Fixing one page leaves the others at odds. An old review might be good evidence of a record’s reception but a poor source for its catalogue number. A vanished band page can leave several claims without an accessible source. This work needs regular upkeep, not just a proofreading pass before publication.
Give each claim a traceable home
Start with facts likely to be reused: release formats and dates, track listings, lineup credits, venues, festival appearances and tour stops. Keep a private source record for each significant claim. A spreadsheet will do for a small archive; a database helps when bands and releases appear across many entries. Record the claim, where it appears, the evidence, what that evidence establishes, when it was checked and any unresolved qualification.
Take a cassette release. A photograph of the insert may confirm the printed track list and label credit, but not the day the tape went on sale. Treat those as separate claims rather than attaching one citation to every detail. Note whether a date comes from the object itself, a contemporary announcement, a later interview or an editor’s inference. Then one detail can be corrected without casting doubt on the whole entry.
Internal identifiers help when names overlap. An original tape, a later CD and a digital edition may share a release title but have different bonus tracks. Give each edition its own record and connect them under that title. For bands that changed names and venues that moved or closed, retain the name used at the time of the event and record alternatives for searching.
Rank evidence by the question it answers
The best source depends on the claim. A sleeve is strong evidence for its printed personnel credits; its copyright year is not necessarily the year listeners could buy the record. A dated show announcement confirms a booking. A contemporary review, set list or documented live recording may help confirm that the show happened. A musician’s later recollection can supply context, though an exact date recalled years afterward may need corroboration.
Keep disagreements in your working notes. If two contemporary sources give different release months, check whether they refer to different formats or territories before choosing between them. If the conflict remains, publish a less precise date supported by both, or say that the sources differ. Sometimes the year is defensible and the month is not.
Build a review schedule around risk
Pages do not all age at the same rate. A historical album entry based on a verified physical copy may stay accurate for years. A page listing available recordings, active members or upcoming appearances can date quickly. Set review priorities according to how likely the claims are to change and how widely an error might spread.
- Review after an event: Revisit announced concerts after their scheduled dates. Change “scheduled to appear” to “performed” only if the evidence supports it; otherwise, leave the listing as an announcement.
- Review when adding connected material: A newly examined pressing, interview or flyer may change an older band profile or scene history as well as the new entry.
- Review periodically: Check prominent overviews and heavily cross-referenced discographies for contradictions, broken internal references and precise dates without adequate support.
- Review on a credible correction: A reader’s scan, catalogue number or firsthand account is a reason to investigate, not an automatic replacement for the existing record.
Track a “last fact-checked” date for each page in the editorial record, separate from its publication date or the date of a formatting change. Fixing a typo does not reset the source-verification clock. For a large archive, a simple risk score can put pages with many claims, uncertain sources, repeated facts or time-sensitive wording at the front of the queue. Phrases such as “still active,” “recently released” and “currently available” age even when the surrounding history does not.
Separate historical facts from changing availability
A release’s identity is one thing; its availability today is another. The track list for a particular edition may be fixed, but stock can change. If availability belongs in an entry, date the statement: “The label listed remaining copies when this entry was checked in March 2024” says more precisely what was verified than “Copies are available.” An archive page should not make a standing promise about a shop, download or reissue.
Band status needs similar care. A final documented performance does not prove a breakup, nor does a long gap between releases prove inactivity. Without a clear statement, give the latest release or performance in the archive’s records, along with its date and source. A brief return to the stage need not rewrite the earlier history.
Older web material from the late 2000s through the mid-2010s can mislead when its date falls away. A preview of a forthcoming EP documents a plan, not the finished release. Check the release separately. If the title changed, the preview still has historical value—as long as it is identified as an announcement of what was planned.
Keep source copies and rights in order
Online evidence is fragile: band sites vanish, social posts become inaccessible and image hosts lose flyer scans. Keep permitted copies or enough bibliographic detail in your working files to identify what you consulted: creator, title or description, visible publication date, access date and relevant passage. For physical sources, pair notes with edition identifiers and photographs of details you have permission to document. A file called “flyer-final-new.jpg” will tell a future editor little unless the event date, venue and source owner are recorded beside it.
Keeping evidence does not grant permission to republish it. A scan retained privately to check a date is different from posting a full copyrighted flyer or recording. Seek permission when needed, give appropriate credit and describe the facts in your own words when an image is unnecessary. Do not offer unauthorized music copies in place of a vanished official source.
Record provenance too. Did a promoter supply the flyer? Was it photographed from a personal collection, or found without a clear origin? An unattributed image can lead to further research, but it should not carry the same weight as an identifiable contemporary document. Put that distinction in the file so the next editor need not rely on memory.
Make corrections without erasing the record
Once an error is confirmed, find every place it appears. Search the site for the wrong date, spelling or venue name, then check captions, tables, summaries and image alt text as well as body copy. If the entry feeds a timeline or band index, correct those too.
Keep a short private change log with the old claim, the replacement, its evidence and the editor’s date. A substantial public correction—say, a release attributed to the wrong band or a performance that never occurred—also warrants a visible note on the affected page. Readers who saw the earlier version should be able to tell what changed. Punctuation fixes need no public notice.
Give contributors a clear way to submit corrections. Ask for the page and claim, the proposed change, the reason for it and whether any supplied material may be quoted or displayed. For firsthand accounts, establish the contributor’s relationship to the event before deciding how to use them. Respect privacy requests, particularly when a submission includes contact details or unpublished correspondence.
Use uncertainty as an editorial tool
“Advertised for the festival” and “performed at the festival” are different claims, and both can be useful. “Credited on the sleeve” is safer than asserting who played on a recording when session details remain unclear. If an interview conflicts with printed credits, mention the disagreement when it matters to the entry; otherwise, do not invent a resolution.
Match the wording to the evidence’s precision. An approximate recording period should not turn into an exact date on a timeline. A city associated with a band is not automatically every member’s hometown. In European tour histories, distinguish an announced itinerary from confirmed individual shows, especially when cancellations or substitutions were possible. A tidy account is no substitute for a verified one.
Check the publishing system as well as the prose
Presentation can make an accurate draft misleading. A table that sorts dates as text may put entries in the wrong order. An automatic snippet may pull an old “upcoming” sentence onto a current landing page. A caption may name the wrong edition while the release entry gets it right. Check these elements during reviews, particularly after a template change or a move to structured fields.
Where practical, use one canonical internal record for facts repeated across pages. Editors can then see which entries depend on a release date or lineup credit before changing it. There is no need to publish every database field; the point is to avoid isolated copies of a fact that cannot be tracked. This work fits alongside managing editorial and promotion tasks for a Finnish thrash archive, but fact-checking needs its own evidence notes and sign-off.
Preview corrections in context before publishing. A qualified date may read well in prose but appear falsely exact in a discography table. If the table calls for a year, use the supported year and explain a disputed month in a note. Do not squeeze uncertain information into a field that has no way to express doubt. The published page should make sense without access to an editor’s private files.
Run a repeatable check on one entry
- List the entry’s factual claims, separating editions, dates, credits and events.
- Match each significant claim to the strongest available evidence, and note what that evidence does not establish.
- Compare the entry with related profiles, discographies and timelines for conflicting versions.
- Replace time-sensitive wording with dated, verifiable statements, or remove it.
- Check the rendered page, including tables and captions, then record the review date and unresolved questions.
Suppose an entry gives a demo’s release date as “14 June 2010,” but the surviving insert says only “2010” and a contemporary July review calls it new. Those sources support a 2010 release, not necessarily 14 June. Change the public date to “2010,” note that the review shows the demo was circulating by July, and mark the exact day as unverified in the working file. If a dated announcement surfaces later, it can settle the question without leaving anyone to guess where the old date came from.
