How mizcausevic-dev/property-schema-publisher works
Property Schema Publisher turns property records into scored listing schema and brokerage entities, then exposes readiness summaries, listing manifests, and repair guidance through an API and dashboard pages. The principal workflow is an HTTP request handled by FastAPI, which calls the schema service; the service reads the JSON property catalog, scores listings, and builds schema payloads. Dashboard and manifest views are rendered separately. The README documents FAQ, entity-linkage, neighborhood, school, and content-quality signals; sampled scoring confirms several of these, but the data and implementation excerpts do not establish a separate content-generation pipeline.
Main entry points: render.py Page renderer · schema_service.py Schema service · main.py HTTP interface · sample_properties.json Property catalog
Components 14
API entry
- HTTP interface
app/main.py - API responses
app/main.py
Schema engine
- Property catalog
app/data/sample_properties.json - Schema service
app/services/schema_service.py - Readiness scoring
app/services/schema_service.py - Listing schema
app/services/schema_service.py - Brokerage schema
app/services/schema_service.py
User surfaces
- Page renderer
app/render.py - Dashboard summary
app/render.py - Listing manifest
app/render.py - Repair queue
app/render.py - API summary
app/render.py - HTML pages
app/render.py
Other components
- Listing team
Connections 16
- Listing team → HTTP interface: requests
- HTTP interface → Page renderer: renders pages
- HTTP interface → Schema service: calls service
- Schema service → Property catalog: reads records
- Schema service → Readiness scoring: scores listings
- Schema service → Listing schema: builds listing schema
- Schema service → Brokerage schema: builds brokerage schema
- Page renderer → Schema service: requests page data
- Page renderer → Dashboard summary: renders
- Page renderer → Listing manifest: renders
- Page renderer → Repair queue: renders
- Page renderer → API summary: renders
- HTTP interface → API responses: returns JSON
- Page renderer → HTML pages: returns HTML
- API responses → Listing team: responds
- HTML pages → Listing team: serves pages