The document discusses NPR's digital media strategy, specifically focusing on their use of APIs and a crossmedia content management system known as COPE (Create Once Publish Everywhere). It outlines the goals and principles behind the NPR API, emphasizing improved development efficiencies and content distribution flexibility, as well as lessons learned from implementing the API. The text also highlights the architectural improvements and challenges associated with maintaining and adapting the API for mobile and partner applications.

1. NPR Everywhere: Even Better APIs and Content StrategiesZach BrandNPR, Digital Media@zbrand #NPRAPI

2. “From NPR News in Washington..” –Jack Speer et alX 784X 35M / Week

3. NPR Digital Media

4. But First, Some Definitions…CrossMediaCMS: Content Management SystemAPI: Application Programming InterfaceCOPE (Create Once Publish Everywhere)Flexible Content

5. Why Have A Crossmedia Strategy?0 - 50> 1,000,000,000~ 1,000,000

7. Our Technical Principles…Don’t Attempt to Build the ‘One System’

8. COPE (Create Once Publish Everywhere)

9. COPE drives all other architectural decisions

10. Realized at NPR with the NPR News API

11. Content Management Tools & Presentation Layers

12. Understand Your Atom

13. Story is the Atom for NPR

14. Stories contain ‘Assets’ (ie. text, audio, video, images, etc.)

15. Stories belong to ‘Lists’

16. It is better to be incomplete than inaccurate“Everything should be an API”FCC managing director Steve Van Roekel

17. Goals for NPR APIImprove development efficienciesDistribute content to stations and partnersAllow the public to do amazing things with the APIGreater flexibility in what we do with NPR content

18. The Life of a (FLEXIBLE) Story at NPRPresentationLayersCMSAPI1234

20. (1) CMS: The Story is Born

21. (2) API: It Becomes Data..

22. (3) Distribution: Delivery Service

23. (4) Presentation Layers…

24. iPhone Music App

25. iPhone Music App

26. iPad App

27. iPad App

28. HTML5 site

29. Station Website

30. The Life of a (FLEXIBLE) Story at NPRPresentationLayersCMSAPI1234

31. \

32. Lesson: COPE!\

33. The NPR Architecture of COPE

34. The NPR Architecture of COPE

35. The NPR Architecture of COPE

36. The NPR Architecture of COPE

37. The NPR Architecture of COPE

38. The NPR Architecture of COPE

39. Goals for NPR APIImprove development efficienciesDistribute content to stations and partnersAllow the public to do amazing things with the APIGreater flexibility in what we do with NPR content

40. Goals for NPR APICase Studies of the ^Improve development efficiencies?Distribute content to stations and partners?Allow the public to do amazing things with the API?Greater flexibility in what we do with NPR content?

41. Has NPR’s API improvedApp Dev?

42. Lesson: Enabled MobileFacebook IntegrationNPR MusiciPhone appNPRiPad appRelaunched NPRmobile siteNPR News Android appAPILaunch2008Player 2.0NPR MusicRemixNPR BlogsMade API FriendlyHomepage ImprovementsStory PageImprovementsNPR News iPhone app

44. Lesson:Gotta figure out how to use it.Lesson:Be Scalable

45. Lesson: Flexible ArchitectureA P I MySQL InstanceWeb ServerWeb ServerContent Management SystemCacheTierWeb ServerWeb ServerMySQL InstanceSingle Oracle DatabaseServer(Point of Failure)Web ServerWeb ServerMySQL InstanceWeb ServerWeb ServerWeb ServerWeb ServerMySQL InstanceWeb ServerWeb ServerMySQL InstanceWeb ServerWeb Server

46. Lesson: Maintainability

47. Better Architecture

48. Results of New ArchitectureResponse time is 22% faster (0.45 -> 0.35s)Eliminated many (slightly) inaccurate returnsFaster Development on the APICleaner Separation of Output formatsNo more use of Xpath QueriesEasier Ramp up for New Developers

49. Lesson: Its Not Just Tech..FlexibleContentToolsPeople

52. Lesson: A thousand words matter

55. Lesson: Have PeopleWorkonStuffthatMatters

58. Image Data in the API<image id="133849355" type="primary" width="200" src="http://media.npr.org/img/a1.jpg" hasBorder="false"><crop type="square" src="http://media.npr.org/img/as.jpg" height="440" width="440"/><crop type=”wide" src="http://media.npr.org/img/aw.jpg" height="400" width=”225"/></image>

59. Case Studies of NPR APIImprove development efficiencies?Distribute content to stations and partners?Allow the public to do amazing things with the API?Greater flexibility in what we do with NPR content?

60. How has NPR’s API served Partners?

62. Nationally-Broadcast Reports by Martha WoodroofMartha Woodroof

63. Connecticut Public Broadcasting Photos Courtesy Derik Elis, CBTV

65. Lesson: It’sHard to knowhow it will go.

66. Lesson: Changes and Deletes

67. How has NPR’s API served Partners?

68. Lesson: Ingest is TrickyDRMData/MetaData StandardsCategoriesUptime/PerformanceIntegration & QA

69. Lesson: Tools/Support is Big Deal

70. Case Studies of NPR APIImprove development efficiencies?Distribute content to stations and partners?Allow the public to do amazing things with the API?Greater flexibility in what we do with NPR content?

71. Has the API resulted in amazing ‘free’ stuff?

72. NPR Addict iPhone App

73. Lesson: You’ll drink your own champagne

74. Paid DevPublic Dev$$$

75. Lesson: Opportunity to work with the public

76. Case Studies of NPR APIImprove development efficiencies?Distribute content to stations and partners?Allow the public to do amazing things with the API?Greater flexibility in what we do with NPR content?

77. Has the API made our content flexible?

78. More than ‘Story’ Pages

83. Lesson: New Features…New Versions

84. To RecapImprove Development Efficiency?

85. Yes it Does!

86. Flexible Content Helps Solve the Mobile Problem

87. An API Requires Investment x2

88. Content & Technology Are Inextricably Linked

89. Creates New Editorial & Content Challenges

90. Needs to be Built for MaintainabilityTo RecapImprove Development Efficiency?

91. Improve Distribution to Partners?

92. Absolutely!

93. Should Support a Range of User Capabilities

94. Expedites Business Development

95. Ingestion has Unique Challenges

96. Updates, Deletes, & Omissions All Cause Problems.To RecapImprove Development Efficiency?

97. Improve Distribution to Partners?

98. Public Will Do Your Work For you?

99. They Might Do Some Things

100. You Must Engage with them Actively

101. But They Will Work with You.To RecapImprove Development Efficiency?

102. Improve Distribution to Partners?

103. Public Will Do Your Work For You?

104. Greater Flexibility in What You Can do with Your Content

105. Yes … But Not Everything

106. Understanding Your ‘Atom’ helps & also Defines Limits

107. Content Needs Expands = API Expansion

108. You’ll Need Versioning

109. APIs may Beget More APIsQuestions? #NPRAPIPS: We’re Hiring in DC & Boston@NPRJobs | http://www.npr.org/about/careers/Email: zbrand@npr.orgTwitter: @zbrandAPI : www.npr.org/apiBlog http://www.npr.org/blogs/inside