About this edition and its historical sources
A new practical article based on the recovery of the early Tarp pages. It describes record-keeping choices, not an official policy of the historical organisers.
Small concerts and informal showcases often leave a scattered record. An invitation survives in an old message, a programme remains on a changed website and photographs sit in a folder whose event name everyone once understood. Years later, those pieces become hard to connect. The recovery of the Big Orange Tarp pages illustrates both the value and the limits of such material: one address held several different programmes, an announcement changed tense after the event and a linked photo album could not be recovered. A useful archive begins by keeping those distinctions clear. It does not require turning every evening into a major historical project, only saving a few accurate facts alongside the material worth retaining.
Save the invitation and the eventual record separately
An invitation tells us what was planned. A checked programme or a brief note after the event may tell us what actually happened. Both can be valuable, but they answer different questions. Keep the original announcement even if the venue, lineup or time changes, and add a clearly dated correction rather than silently replacing it. A future reader should be able to follow the sequence without assuming that every version describes the same final arrangement. This is especially important when a programme becomes a source for an artist's performance history.
A short follow-up need not be a review. It can state the event's date, confirmed participants and any significant departure from the advertised plan. If no one checked the running order, leave it labelled as scheduled. The Tarp's change from a coming concert to a completed one provides a modest example of a useful update. It establishes something about the sequence without recovering every musical detail. An archive becomes more dependable when it makes the boundary of each document's knowledge easy to recognise.
Record enough context to identify the occasion
For each saved item, note the event name, place, date, creator and source. Add the version or capture date if it differs from the event itself. A photograph taken at a concert, a programme prepared beforehand and a web capture made months later may all carry different dates for good reasons. Do not force them into one field. A simple text note beside the files can explain these relationships without requiring a specialist catalogue or a complex system that nobody will keep using.
Names deserve careful attention. Retain the spelling used in the source and note a verified correction separately. When several people share a name, add the context necessary to identify the right performer. Distinguish the act name from the individual musicians where the programme supplies both. Avoid filling gaps from memory unless that contribution is labelled as a recollection. A future reader can evaluate a remembered detail, but only if it has not been quietly merged into the apparently contemporary document that the archive is meant to preserve.
Keep original files beside readable versions
A readable transcript helps people search and understand an old document, while the original file preserves layout and details that the transcript may overlook. Retain both when possible. If text is extracted from a scan or an old web page, check important names, times and numbers against the source. Mark uncertain readings rather than inventing a smooth sentence. Older encodings can also damage punctuation, so distinguish a deliberate correction from a character that was already unclear in the copy available for recovery.
Do not assume that a web address alone preserves the content found there. Pages change and domains can acquire unrelated material. Save an appropriate local copy where you have permission, record the original address and retain a capture reference if one exists. If a linked album or recording is missing, keep the reference as evidence of what was intended to be available. The missing item can remain a documented gap instead of disappearing from the record or being replaced by an unrelated image that merely fits the mood.
Treat recordings and photographs as somebody's work
Before publishing an image or recording, establish who created it and what permission accompanies its use. A performer agreeing to appear at an event has not necessarily agreed to distribute every recording made in the room. A photographer's name can also be lost when an image moves through several people. Record attribution and permission with the file rather than relying on the organiser to remember the conversation later. Clear records make appropriate sharing easier because the relevant conditions do not need to be reconstructed each time.
Consider what identifying information is necessary for the archive's purpose. A historical home address or an old booking phone number may belong in a protected original document without becoming a prominent present-day contact button. Explain the historical status of such details if a source is made public. This is not a reason to erase the document's context. It is a reason to design the presentation so readers can understand what the material records without mistaking it for a current invitation, service or route to the people mentioned.
Choose a structure that another person can maintain
Use clear filenames and an uncomplicated organisation by event or date. Keep a small index describing what each folder contains and which items are missing. A structure that makes sense only to its creator will become fragile when someone else needs to use it. Test the arrangement by asking whether another person could identify the correct programme without opening every file. The goal is not to impose a perfect taxonomy on a living music scene, but to make the records findable and their relationships understandable.
Keep more than one copy and periodically check that the files still open. A collection is not secure merely because it exists on an old drive, an email account or a web service that has been reliable so far. Record who is responsible for maintaining the collection and where the current index is held. If the archive changes hands, include the explanations that give the files meaning. A modest set of well-described documents can be easier to preserve than a much larger collection whose significance has never been written down.
Let uncertainty remain visible
A good archive does not need to answer every question. It should help a reader see which answers come from contemporary documents, which come from later recollections and which remain unknown. The early Tarp pages give us event invitations and detailed programmes, but not a complete record of how every set unfolded. Their value increases when that distinction is preserved. A confident but unsupported narrative can make an archive feel finished while reducing its usefulness to someone who later discovers another piece of evidence.
Start with the next event rather than waiting to organise an entire lifetime of material. Save the invitation, keep the final programme if one exists, label a few approved images and write a brief factual note. Those small actions create a dependable foundation. The recovered pages presented here survived because ordinary documents happened to be captured and retained. A more deliberate record can preserve the same everyday musical culture with fewer gaps, while still leaving room for the songs and experiences that no programme can completely contain.
Read the original documents
- GrooveLily in Baltimore: the original announcement · captured 18 April 2002
- After Baltimore: the concert follow-up and summer links · captured 27 May 2002
- Big Orange Tarp / Folkmusic.org at NERFA · captured 22 January 2003
- Big Orange Tarp / Folkmusic.org showcases at NAFA · captured 13 February 2003