Menu

Collecting a reference library of genuine document layouts — scrape, partner, or buy?
📰

Collecting a reference library of genuine document layouts — scrape, partner, or buy?

DEV Community: security·Erik Svensson·7 days ago
#103pYhHo
#devtosecurity#devto#dev#reference#document
Reading 0:00
15s threshold

At Landvex we need a reference holding of what genuine document families look like: bank statements, employment certificates, invoices, and some ID/travel documents used in Europe. Not customer files. Layout, issuer markers, typical field structure. Receiving country and issuing country are often not the same, which already makes "just scrape one national portal" pretty useless!?

What's actually worked when the material has to be lawful and auditable?

A few points I'm turning over:

Public official specimens versus anything that looks like a customer document

Is scraping those public pages even the right architecture, or do you start with data partnerships and treat crawlers as a last resort?

How do you store provenance so a later reviewer can see where a reference came from, when it was fetched, and under what licence? Some official libraries are explicitly not for reuse in a product.

Layout fingerprints versus storing full page images.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.