Data dictionary — Public Space LDN

How to read this

Zero is not the same as empty: 0 means a genuine zero. Empty means no value at all and is shown as -. Core never stores a dash.
Days of the week: 0 = Monday, 1 = Tuesday, through to 6 = Sunday, everywhere in Core.
Money: All amounts are held in pence as whole numbers. Applications format them for display.
Worked-out values are read-only: Minimum Spend From, Room Hire From and Lead Commission are worked out by Core. No application can write them.
Commission: The listing commission rate is private commercial data held as a decimal fraction (0.0500 = 5%). Core copies it onto a lead at creation and that copy never changes.
Venue and listing: A venue is the physical place; a listing is how a space is presented. One venue may have several listings. Opening hours belong to the venue; listings inherit them.
Lead stages: Exactly one of: Lost, Final Chaser, Discount Chaser, New, Quoted, Qualified, Delayed Chaser, Viewing, Decision, Awaiting Payment, Booked. Never empty.

Core — This project — the central record everything else reads.CRM — Sales desk: leads, enquiries, viewings, messaging.Venue Portal — Venue teams: their own venue, staff and events.Listing pages — Public website pages for each space.

Changed byCRMRead byCoreVenue PortalListing pages

Field	Kind	Type / allowed values	Who may change it	Notes	Example
Listing referenceid	system	reference	Nobody		…
Belongs to venuevenue_id	relationship	reference	Sales		…
Listing name (CRM)sharedtitle	stored	text	Sales		…
Short web namesharedslug	stored	text	Sales		…
Descriptionshareddescription	stored	text	Sales		…
Lifecyclestatus	stored	controlled textdraft, published, paused, archived	Sales	CRM labels: Live = published. Only published listings are publicly readable or can take enquiries; paused returns a holding page. Transitions: draft to published/archived, published to paused/archived, paused to published/archived, archived to draft/published. Slug is locked once first published.	…
Standing capacitysharedcapacity	stored	whole number	Sales	The one official standing figure.	…
Seated capacitysharedseated_capacity	stored	whole number	Sales		…
Minimum spend (legacy)legacymin_spend_pence	stored	whole number (pence)	Sales	Superseded by Minimum Spend From, derived from weekday guide pricing.	…
Overview blurbsharedoverview_blurb	stored	text	Sales	Short summary paragraph shown above the full description. Empty means not supplied.	…
Main photosharedhero_image_url	stored	text	Sales		…
Floor space (sq ft)floor_space_sqft	stored	whole number	Sales		…
Listing websitewebsite	stored	text	Sales		…
Nearest tubenearest_tube	stored	text	Sales		…
Walk to tube (minutes)walking_time_to_tube_mins	stored	whole number	Sales		…
Old extra details (legacy)legacydata	stored	free-form	CRM	Superseded by the canonical columns and child tables. Not part of the v2 public contract.	…
Published onpublished_at	stored	date and time	CRM		…
Createdcreated_at	stored		CRM		…
Last changedupdated_at	stored		CRM		…

What each project may do

Permission to work with the central records. No project copies records to another.

Project	Records	See	Add	Change	Remove	Notes
CRM	Venues	Yes	Yes	Yes	No	Sales desk manages venue records.
CRM	Listings	Yes	Yes	Yes	No	Including capacities and listing facts.
CRM	Listing commercial terms	Yes	Yes	Yes	No	Private. Sales only.
CRM	Guide pricing	Yes	Yes	Yes	Yes	Weekday figures.
CRM	Minimum Spend From / Room Hire From	Yes	No	No	No	Worked out by Core.
CRM	Opening hours	Yes	Yes	Yes	Yes	Venue level.
CRM	FAQs, features, reviews, media	Yes	Yes	Yes	Yes	FAQs limited to four.
CRM	Viewing rules	Yes	Yes	Yes	Yes	Not public at this stage.
CRM	Contacts	Yes	Yes	Yes	No	Venue contacts are linked by venue.
CRM	Leads	Yes	Yes	Yes	No	Stage, quoted figures and notes.
CRM	Commission snapshot / lead commission	Yes	No	No	No	Set and worked out by Core.
Listing pages	Listings, venues, pricing, hours, FAQs, features, reviews, media	Yes	No	No	No	Published listings only, through the public contract.
Listing pages	Listing commercial terms	No	No	No	No	Private commercial data.
Listing pages	Viewing rules	No	No	No	No	Revisit when listing pages are migrated.
Listing pages	Contacts and leads	No	Yes	No	No	Only by submitting an enquiry through the controlled Core operation.
Venue Portal	Their own venue and listings	Yes	To be decided	To be decided	To be decided	Writes decided during the Venue Portal audit.
Venue Portal	Hours, pricing, FAQs, features, reviews, media, viewing rules	Yes	To be decided	To be decided	To be decided	Read only for now.
Venue Portal	Listing commercial terms and lead commission	No	No	No	No	Public Space commercial data.
Venue Portal	Leads for their venue	Yes	No	To be decided	No	Without commission figures.
Core	Everything canonical	Yes	Yes	Yes	Yes	Core is the source of truth and owns worked-out values.

Old data still kept for now

Nothing here is removed yet. Each line says what has to be true first.

Item	Can go once
listings.min_spend_pence	Listing pages read the worked-out Minimum Spend From instead.
listings.data (old extra details)	Every reader uses the canonical columns and child tables.
enquiries.client_name / client_email / client_phone	The details originally submitted with each enquiry are preserved in an unchangeable record first, then readers use the linked contact.
crm_state copies of listings, contacts, users and events	The CRM reads Core directly.
Guide pricing and gallery held inside the old JSON	CRM and listing pages read the guide pricing and media tables.
Old opening-hours copy	Every application reads the canonical venue hours.
Venue-as-contact duplicate records	Venue contacts are linked by venue instead.
Obsolete lead grouping field	Confirmed unused by every application.