3 ms·
That's fine, but someone has to physically go to the records office and scan in thousands of documents to be digitised. That's the problem with Ancestry, they h
by Someone1234 12y ago
That's fine, but someone has to physically go to the records office and scan in thousands of documents to be digitised. That's the problem with Ancestry, they have a massive digital archive and the funds to keep growing it.
Some copies of the census are digitised already, but the further you go back the less likely that is. And a lot of the information people want originates abroad (e.g. UK, Germany, Italy, France, etc).
- toomuchtodo 12y agoSo, I might have some insight into this. I'm working with an organization to collect real estate parcel data for the entire US and open source it. I track every county or district that has parcel data, I built a workflow to get the data from them, manage the ingest of the data, and a separate workflow if they're difficult and I have to FOIA them for it (via muckrock.com). There is a cost, but as always, everything has a cost. Same deal, but closer to what Distributed Proofreaders for Project Gutenberg does with scanning. It can be done. Funds and organization would be necessary, but let's not think its some herculean task.
- Asparagirl 12y agoYou don't actually need to scan all the images, just transcribe the main points of the data (names, dates, places), make that data searchable, and then provide information about how a user could go about ordering a copy of the original data if needed.
- gsnedders 12y agoTranscription errors are very much a problem, though, especially when you're dealing with faded or smudged ink. Scanning the images allows people to verify the transcription and to distribute the work of doing the transcription.