Case study · System
StationRecord: where the schedule starts
StationRecord is a broadcast recording and scheduling platform, built by Darren Gibbons, one of LDC’s directors. Its sign-in page at stationrecord.co.uk calls it a radio recording platform and asks you to “Sign in to your station”.
It doesn’t run on our server, so the picture here is its public sign-in screen. This page explains the part it plays for LDC Radio, in more detail than its card on our web and digital page.
- What it is
- Private system (staff sign-in)
- Sector
- Radio recording and scheduling platform
- Built with
- Web platform with a schedule API
- Sign-in page
- stationrecord.co.uk
The job the system does
A station on air around the clock has two needs that are easy to underestimate. Every show should be recorded as it goes out, without someone remembering to press a button. And there should be one schedule that says what is on and when, which everything else reads from.
If the schedule lives in three places, the three copies drift apart, and the website ends up saying one thing while the studio says another. StationRecord is designed to be that single source.
What it does
StationRecord holds the station’s show schedule and records the shows as they air.
It also serves the schedule through an API. The API is organised by client ID, one per station, so the platform is built to serve more than one station.
How it connects
LDC One reads LDC Radio’s schedule from the StationRecord API every hour. From there it reaches the schedule and the show pages on this website, so a change made in StationRecord appears here without anyone retyping it.
Recordings of LDC Radio’s shows are uploaded to the station’s SoundCloud, each titled with the show’s name and the date it aired. Those uploads are where the listen-again mixes on ldcradio.co.uk come from.
One entry, many places
Follow a single show through the chain. It is scheduled in StationRecord, read into LDC One within the hour, and published on the schedule and show pages of this website. It is recorded as it airs, uploaded to SoundCloud under its name and date, and then turns up here as a listen-again mix. One entry, made once, ends up in every one of those places.
Why one source matters
The same idea applies well beyond radio. Any business that publishes a timetable, a price list, a set of opening hours or a list of staff in more than one place has the same problem: the copies drift. Keeping the master in one system, and having the website and everything else read from it through an API, removes the retyping and the mismatches together.
That is the pattern this website is built on, and it is one we use when we plan bespoke software for other businesses.
What it runs today
Today it holds LDC Radio’s schedule and records its shows. You can see its work in two places: the schedule on this website, which starts life in StationRecord, and the station’s SoundCloud, where the recorded shows are published.
Call us or get a quote
Talk it through with LDC on the phone, or send a few lines and we’ll come back to you with a quote.
Get a quote
Tell us what you’re trying to achieve.
A few lines is plenty. Tick what you think you need — or “Not sure” — and we’ll reply by email to talk it through and quote.