Content Management Systems and Metadata

1. Content Management SystemsandMetadata Ontwerp van Multimediatoepassingen Rik Van de Walle academiejaar 2008-2009

2. What is Content Management? entering content and metadata using an authoring template Logo content is published into the right spot in the publishing template

3. Major Components (example: web access) Publishing User Interface Templates HTML Pages Application Server Authoring Templates Database

4. Basic CMS Features • Access control: who is allowed to do what? • Version control: return to previously saved versions • Library • page templates • images • other assets • Content repository • databases • XML repository • Publishing functionality: creates web pages (or more generally: a portal) using • content • templates

5. Prime Benefit: Efficiency

6. Benefits (aka "promised benefits") • "Single source" of content • Reusability of content • Versioning • Easier maintenance • Consistency • Easier authoring and publishing

7. Designing/Implementing CMS: Problems

8. Apart from HW/SW: Other Problems

9. Most Popular Responses • "No easy way to integrate controlled vocabularies" • "It should be more clear what kind of content the system is designed to manage: documents, web content, etc." • "Make it allow for more flexible designs" • "Workflow didn't fit my needs" • Diversity of responses reflects broad CMS scope

10. Conclusions:Prepare Organization for CMS Complexity • Requires coordination across diverse departments and roles, for example • management • IT department • content creators • end-users • Requires rigorous project management • "A CMS is probably the most complex rollout you and your IT colleagues are likely to have to manage." (Martin White, CMS Consultant and Writer)

11. Conclusions:Tightly Integrate Design and Technology • CMS configuration • technical work • often performed by information technologists • gap between technologists and (end-)users • Yet many tasks, like creating authoring templates, require a well-designed user interface for content authors • Hence, importance of HCI / GUIs

12. Conclusions:Don't Neglect the Content • With all the focus on design and implementation, not enough attention is given to • content creation • content migration • Ultimately, you are designing a system to deliver content – prioritize it appropriately!!! • Migrating old content will always take longer than you expect

13. Reusable Content Requires Standardization • Standardize on many levels: • data formats • metadata • authoring templates / GUIs • publishing templates • May require coordination across an organization

14. Start with the User Interface • This keeps the information centered on user needs, instead of having to retrofit a user interface onto a mismatched information model • Helps determine scope: model only the information you need in the system, and avoid an unnecessary large intellectual exercise

15. Feedback Loop • In practice, there is a feedback loop between the user interface and the information model, but focusing on the user interface helps ensure the right design for the user • You may have to consider several different UIs that share content to make sure the content is reusable

16. PublishingTemplates • Fewer is better • easier maintenance • more consistent layout • increased usability • Example: Cisco.com has nearly one million pages with about three HTML templates

17. Create Semantic Relationships • Use metadata to describe the relationship among information types, for (a/o) • content analysis • searching • browsing • indexing

18. Metadata Standards • Some major activities identified: • SMEF (Standard Media Exchange Framework) • P/Meta (EBU Project group) • AAF: Advanced Authoring Format • SMPTE-UMID (Society of Motion Pictures and Television Engineers - Unique Material Identifier) • MPEG-7 (Moving Picture Experts Group) • MPEG-21 • This list is far from complete!!!

19. Why Standardized Metadata? • Standardized metadata allows • authoring once for many destinations • metadata authoring tools that can be supplied to many different customers • editing of metadata that has come from many sources • economy of scale for • content providers • manufacturers

20. Existing Metadata Technologies • Musea • AMICO (Art Museums Image Consortium) • CIDOC (International Committee for Documentation) • ICOM (International Council of Museums) • Archiving • OAIS (Open Archival Information System) • ISAD (International Standard Archival Description) from ICA (International Council of Archives) • EAD (Encoded Archival Description) • IASA (International Association of Sound and Audiovisual Archives)

21. Existing Metadata Technologies • Industry in a broad sense • extremely diverse • a lot of proprietary solutions, like • UDDI (Universal Description, Discovery and Integration) • OASIS - XML.org • BizTalk • Importance of XML • separation between content and layout • generic markup language • content-independent • a lot of “XML tools” are already available

22. Existing Metadata Technologies • Cross-domain technologies • Resource Description Framework • a standard way for using XML • to represent metadata • in the form of statements • about properties and relationships of items • heavily used in digital libraries • Dublin Core (Dublin Core Metadata Element Set) • 15 element set • associated qualifiers • to facilitate discovery of resources • heavily used in digital libraries

23. EBU P/Meta • Developed by • European Broadcasting Union • project group P/Meta • aims at developing common media exchange formats • for broadcasters, publishers and archives • liaison with (a/o) SMPTE and MPEG • Problem: too many organizations developing • too many standards • methods and procedures

24. EBU P/Meta • Importance to guarantee compatibility and interoperability • AAF moves in this direction • with an overall metadata infrastructure • No detailed, official standards for interoperable audio-visual metadata that includes and integrates • all digital production • distribution • archiving • Standardization work is needed • Cooperation is needed as well...

25. TV-Anytime Forum • "Watch what you want, when you want" • Simpler ways for the consumer to acquireTV content on local storage • click on EPG • trailer • website • Personalization and automatic recording

26. TVA Metadata • Assists the consumer in selecting content • Supports creation and use of user profiles • TVA metadata includes • programme information • segmentation information • related material information • purchase information • user profiles • usage history • TVA metadata uses a CRID to refer to content

27. Content Referencing • The CRID (Content Reference IDentifier) • allows for location independent referencing of content • is assigned by an authority which also has the ability to resolve the CRID to a location • A CRID points to • a single piece of content • or a series of other CRIDs

28. Why is Content Referencing Needed? • The same metadata can be used for content regardless of where and when it is broadcast • To reference groups of programmes such as an entire series • References can be given before time & channel has been decided • References work even if there is a change to the scheduled transmission time

29. CRID – Grouping example Group information Program information <GroupInformation GroupId="crid://hbc.com/foxes/all" GroupType="show" Ordered="true" NumberOfItems="2"> <BasicDescription> <Title type="main">All episodes of Foxes ever</Title> <Synopsis Length="short">More Foxes than you can handle</Synopsis> </BasicDescription> <MemberOf>crid://hbc.com/comedy/all</MemberOf> </GroupInformation> <ProgramInformation ProgramId="crid://hbc.com/foxes/episode1"> <BasicDescription> <Title type="main"> The one where Fox jumps in the Potomac </Title> <Synopsis Length="short"> Fox goes to Washington and jumps in the Potomac </Synopsis> </BasicDescription> <MemberOf>crid://hbc.com/foxes/all</MemberOf> </ProgramInformation> <ProgramInformation ProgramId="crid://hbc.com/foxes/episode2"> <BasicDescription> <Title type="main"> The one where Fox drowns in the Lake of Geneva </Title> <Synopsis Length="short"> Fox goes to Geneva and tries to climb the fountain </Synopsis> </BasicDescription> <MemberOf>crid://hbc.com/foxes/all</MemberOf> </ProgramInformation> CRID CRID CRID

30. CRID – Resolution CRIDTOP CRIDs resolve to lists (of CRIDs or locators) A CRID can resolve to other CRIDs CRIDA CRIDB CRIDC CRIDB1 CRIDB2 locator locator locator locator locator At some point, CRIDs must resolve to locations

31. CRID – Hierarchy Example Star Trek Original Series 1966-1969 The Next Generation 1987-1994 Deep Space Nine 1993-1999 Voyager 1995-present … … … Season 1: 1966-1967 Season 2: 1967-1968 Season 3: 1968-1969 … … … … Episode 1: "The Man Trap" Episode 29: "Operation: Annihilate!" Location 1 Location 2 Location

32. Recording from a trailer

33. Recording from a Web page

34. Electronic Programme Guide Creating EPGs with data from many sources

35. Detailed programme information

36. Grouping

37. Searching for interesting programs Search for interesting content without knowing where or when it will be broadcast

38. TVA – Industry Adoption • Transport mechanisms for TVAF data have been incorporated into DVB specifications • ARIB has adopted TVAF (Japan – Association of Radio Industries and Businesses) • ATSC has selected TVAF metadata (US – Advanced TV Systems Committee) • IPTC has (International Press Telecommunications Council) • produced ProgramGuideML • adopted TVAF metadata • EBU P/Meta is TVA compatible, using many common elements (Europe) • Companies in US, Europe, and Asia are developing TVA-compatible products

39. Sources • The (Unfulfilled) Promise of Content Management Systems Victor Lombardi • Introducing TV Anytime Phase 1 Ronald Tol • The MPEG consortium (and its members)