What You Need to Know About Collecting and Preserving New England Folklore
New England Tales Of Hauntings Strange Happenings And Other Local Lore isn't really a single database or one tool. It's a category of fieldwork — gathering oral histories, written accounts, and paranormal reports from the New England region and keeping them somewhere that won't rot away in five years. The people who do this well treat it like a mix of journalism, archival science, and basic data management. That's it. Nothing mystical about the process. The actual work breaks into three parts: sourcing, verification, and storage. Most beginners skip straight to collecting stories without a verification step, then wonder why their archive turns into a pile of unsubstantiated Reddit posts. It happens constantly. I started doing this around 2012 when I found a folder of typed transcripts from a researcher who'd been collecting Salem-area haunting accounts since the 1980s. They were stored on floppy disks. Not kidding. That was my first lesson in why format matters more than content. If your source material can't be opened, it doesn't exist anymore. Everything after that just got slightly less catastrophic.
The sourcing process
You pull stories from five main channels, and each one comes with its own set of problems. Public records and town archives — Many New England towns have historical societies that collected paranormal accounts as part of local folklore surveys. These are gold mines but are almost never digitized. I spent three weeks at a county clerk's office in Worcester looking through a box labeled "weird occurrences" from 1978. Found six solid eyewitness accounts with dates, names, and addresses. None of them were online. Going in person is still the best way to find this stuff. Oral history interviews — Record conversations with older residents. Ask specifically about strange events they experienced or heard about from someone they trusted. Standard interview protocol applies: get consent, record in WAV not MP3, and transcribe everything. I once interviewed a woman in rural Vermont who described a farmhouse incident in detail. Her recollection was sharp and consistent. Six months later, a fact-checker debunked most of it by showing the house had never been occupied during the dates she gave. The story was wrong, but the interview itself was still valuable as primary source material because it showed how the tale had survived and changed in her family. That's the nuance beginners miss — you're often collecting the transmission of a story, not just the event.
Online forums and subreddits — r/NewEngland and regional ghost hunting boards have decent material if you filter for specific details. Vague posts like "my house feels creepy" are useless. Posts with addresses, dates, newspaper clippings, and photos that can be reverse-image searched are worth archiving. I've saved maybe 40 stories from forums over the years that held up under scrutiny. Out of several hundred I looked at. Newspaper archives — Chronicling America, Newspapers.com, and regional archive sites like the Boston Globe archive contain decades of what used to be dismissed as "fluff" crime and oddity sections. Those oddity sections had a lot of strangeness reports. The Boston Evening Transcript ran regular columns on local hauntings in the early 1900s. Digitized and free through some library subscriptions. Academic papers and theses — Folklore programs at UMass, Boston College, and University of Connecticut have published collections. Search ProQuest and Google Scholar with terms like "New England ghost narrative" or "paranormal oral history Massachusetts." These tend to be the most rigorously sourced material you'll find.
Get the Full Details
Verification that actually works
Don't just take a story at face value. Cross-reference it. Here's what I check: Date consistency — Does the timeline match local history? A story about a haunted mill that's dated to 1890 when the mill wasn't built until 1903 is suspect. Quick check against Wikipedia or local history books catches this. Multiple witnesses — A single account is anecdote. Two independent accounts from different families describing the same location and similar events carry more weight. I don't require this, but I flag single-source stories differently.
Physical evidence or documentation — Photos, property records, wills, diaries. These shift the category from hearsay to documented claim. A handwritten letter from 1842 describing an apparition in a specific room is qualitatively different from a forum post made in 2023. I ran into a problem once where a well-known Gloucester sea haunting story had been retold in at least twelve different books, each citing the previous one as its source. Nobody had gone back to any primary document. When I finally found the original 1912 newspaper mention, it was completely different from what all the books said. The books had invented details — a specific ghost name, a particular year of death, a detailed description of the apparition — that didn't appear anywhere in the original. This is extremely common in New England folklore. Stories mutate across retellings and then get cited as independent sources. Always trace back to the earliest available reference.
Storage and format decisions
This is where most people fail. I use a simple three-layer system: Raw files in their original format — Transcripts as .docx, audio as .wav, photos as TIFF or uncompressed PNG. No conversion loss. Migration copies — One set of files on an external drive, one set on a separate physical drive stored somewhere else. The 3-2-1 backup rule applies here. I know it sounds obvious but I've seen people lose entire collections to a single failed hard drive.
Indexed metadata — A spreadsheet or simple database with fields for: story ID, title, location (town and specific address if available), date of alleged event, date of collection, source type, verification status, and file path. This is the part that makes the collection usable. Without metadata, you have a folder of files and no way to find anything. I switched from a plain folder structure to a proper database with relational tables after losing a collection of about 200 entries to a corrupted Excel file. SQLite fixed that. It's free, it doesn't bloat, and it doesn't randomly corrupt your data. I store everything there now with file paths linking back to the raw materials.
Sharing and publishing
If you want to publish these stories, pick one format and stick to it. A website, a printed zine, a YouTube series, a podcast — they all require different workflows. I've done websites and podcasts. Websites need SEO and constant maintenance. Podcasts need audio engineering skills you probably don't have yet. A simple blog with well-researched posts is the lowest-friction option and the one I'd recommend starting with. Always credit your sources. If you got a story from an interview, name the person and get their permission to publish their words. If you pulled it from a newspaper archive, cite the publication and date. I've seen too many collections that present folkloric material as though the collector discovered it. That's not how this works. You're a steward, not an owner.
Practical constraints and where this approach falls apart
Sourcing from public records requires travel. If you're not in New England, many of the best materials are inaccessible without a trip. Digital versions exist for some collections but not most. Verification has limits. Some stories are genuinely unverifiable because the original witnesses are dead and no records exist. You can still include those but you should label them clearly as unverified oral tradition. Don't pretend otherwise. The biggest bottleneck is time. A single well-documented story with proper verification takes me about four to six hours from discovery to archived entry. That includes research, transcription, cross-referencing, and metadata entry. If you're collecting hundreds of stories, budget accordingly or your quality will drop fast.
If you don't have the time for verification, consider contributing to an existing project like the New England Folklore Archive or the Digital Commonwealth instead of building your own collection from scratch. They already have the infrastructure and the methodologies. You'd be adding value rather than reinventing the wheel.
