PRIVATE RESEARCH / DATA ENGINE
A record of
every change.
Track each site's access status, collector, for-sale listing count, retrieval time and latest run. Ieichiba and a metadata-only Nagano City pilot write to the local database; MLIT contributes an attributed FY2025 open-data snapshot. Firebase sync and twice-daily scheduling remain off. Jimoty is paused pending an approved method.
Loading database status…
SOURCE COVERAGE
What we collect, and when.
Collector status shows what can be run and what has been verified. A shared structured-data collector is available for public sale listings, but each source’s coverage remains unverified until its run succeeds; some sources still need a site-specific connector. Counts include for-sale records only. “Last fetched” is the most recent source-page request recorded, not proof of a full crawl.
| Source | Property types | Collector status | Saved listings | Photo coverage | Last fetched | Latest run | Plan |
|---|---|---|---|---|---|---|---|
| Loading catalog and database status… | |||||||
LATEST ACTIVITY
Collection runs
How collection works
Ieichiba and the Nagano City Akiya Bank use source-specific, paced collectors; their public indexes provide source-hosted image URLs where available. MLIT ProjectLINKS imports a dated FY2025 registration CSV and does not include listing photos. Other catalog sources use a shared public JSON-LD collector when their public index exposes structured, sale-specific records. Each such source remains unverified until a run succeeds. Photos are kept as HTTPS URLs hosted by the source or a configured image host; the collector does not download or rehost image files. Jimoty now uses a bounded public sale-index collector; image URLs are captured only when the card points to a Jimoty HTTPS host.
Source IDs prevent duplicate records. A failed or incomplete run retains earlier data; missing listings are never automatically marked sold. Search results retain first-seen, last-seen and last-changed dates. Coverage is a bounded sample, not a complete national inventory.
The dashboard's published status file contains for-sale aggregate counts and run times only. Property rows stay in the local database until the sign-in gate and publication rules are ready. Firebase sync and the twice-daily schedule are not enabled.