« Previous | Main | Next »

Shapes of things to come

Post categories:

Michael Smethurst Michael Smethurst | 11:57 UK time, Monday, 21 April 2008

Possibly not a post of interest to many but we thought we'd share our /programmes schema with you. It's just going through a major rewrite, the results of which should be live on the site soon-ish. In the meantime we hope you think it's as pretty as we do.

thumbnail

It's probably best to note that whilst /programmes and iPlayer take their data from a common pot (PIPs) this is not the schema of either PIPs or iPlayer but has been reshaped slightly for our publishing platform.

If this is of interest you might also like to compare and contrast with the Programmes Ontology.

Updates

  1. 01-06-2008 uploaded schema 1.38

Comments

  • Comment number 1.

    I still don't get the logic behind having both Episodes and Series/Brands in the same table. Surely they're completely different beasts?

  • Comment number 2.

    Whilst they initially look like three separate things, brands, series and episodes are all editorial grouping constructs that have pretty much the same metadata.

    This is also the approach taken by TV-Anytime, where what we call brands, series and episodes are represented by GroupInformation elements of type show, series and programConcept.

  • Comment number 3.

    It's kind of an editorial / audience vs production distinction. In the editorial world episodes are items and series / brands are groups of items. But PIPs models down to versions - it's versions that are broadcast, versions that appear in iplayer etc. Episodes group versions, series + brands group episodes. So episodes, series and brands are all just groups.

  • Comment number 4.

    I'd argue that the versions in PIPs are also editorial, but you do have to careful how they are exposed in audience facing UIs.

    We have to flatten production versions to create the audience facing ones (signed, shortened, etc).

 

BBC © 2014 The BBC is not responsible for the content of external sites. Read more.

This page is best viewed in an up-to-date web browser with style sheets (CSS) enabled. While you will be able to view the content of this page in your current browser, you will not be able to get the full visual experience. Please consider upgrading your browser software or enabling style sheets (CSS) if you are able to do so.