Sharepoint conference - AP


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Sharepoint conference - AP

  1. 1. Real Change in the News IndustryAssociated Press and the Office 2010 Platform<br />Chad Schorr, Director Newsroom Technology<br />Doug Denner, Newsroom Technology Architect<br />Associated Press<br />
  2. 2. Agenda<br />Introduction to the Associated Press (demo)<br />Industry and Technology Challenges<br />Office 2010: An Editorial System?<br />SharePoint Deep Dive (demo)<br />Tweet questions and feedback to: @APatSPC<br />
  3. 3. But First… Why Do You Care?<br />What is intriguing about AP’s implementation of SharePoint 2010?<br />Real time editing across a global footprint<br />The mission critical core of our newsroom<br />Large content turnover. 60k docs a day<br />We’re integrating Microsoft FAST ESP, not FAST for SharePoint<br />SharePoint will not be the UI<br />
  4. 4. Largest and oldest news gathering organization in the world<br />4,100 employees. 243 bureaus in 97 countries.<br />49 Pulitzer Prizes<br />1,700 U.S. members<br />5,000 International subscribers<br />On any given day, more than half the world&apos;s population sees news from AP<br />
  5. 5. What is AP News?<br />
  6. 6. Publishing a Story<br />End to end news filing scenario<br />demo<br />
  7. 7. Newsroom Challenges<br />Demand shifted from content verticals to packages of related multimedia content<br />Linking and association become more important to newsroom workflow<br />Communication/Collaboration<br />Virtualization of the news desk<br />News product landscape can change faster than the news<br />Metadata becomes increasingly vital<br />There used to be a person at the other end<br />
  8. 8. Legacy Technology Challenges<br />Our current system is completely distributed with no central storage<br />Collaboration is based on file sharing<br />Many copies of the same story eventually need to be aggregated<br />Technology creates artificial walls between workgroups<br />Expensive to extend and maintain<br />The user interface is 100% custom<br />No version management<br />
  9. 9. Why Office 2010?<br />We considered several solution options<br />Rebuild everything from scratch<br />Purchase a turnkey solution<br />Hybrid - select a framework technology and customize as appropriate<br />Two thirds of our requirements were met out of the box with Office, Communicator and Exchange<br />Office allows us to focus on the business rules that make AP unique<br />
  10. 10. Key SharePoint Features for AP<br />Managing concurrent work and document versions<br />Co-Authoring versus Check-In Merging Model<br />Search driven replication<br />Close to real time discovery of remote work<br />Communicator and Exchange integration<br />Hot deployment model<br />Site failover with geographic distribution<br />SharePoint as a server and not as a front end application<br />
  11. 11. The Journalist UI<br />Word 2010 Add-In<br />demo<br />
  12. 12. Why Word 2010?<br />Remote Differential Compression sends less data over the wire<br />Quite useful for remote users with limited bandwidth<br />Office Document Cache<br />Asynchronous file I/O unblocks our users<br />Performance<br />Running Word is faster<br />Aggressive document open targets<br />
  13. 13. Publish and Transform<br />Using the OpenXML SDK to Integrate<br />demo<br />
  14. 14. Integration and Extensibility<br />Makes it easy to transform from the Office format to your own format<br />Eliminates any need to have Office client installed server side<br />Enables bi-directional transforms so we can pull back material from our content archive and display in Word<br />Keeps us at a safe distance from docx internals<br />
  15. 15. FAST ESB Integration<br />demo<br />
  16. 16. Architecting for Performance<br />New content needs to be available for our user’s searches within seconds of publishing<br />SharePoint crawling and traditional replication methods do not meet our performance requirements<br />FAST ESP provides us a more customizable platform for ingesting content as it’s produced<br />Using event receivers and service broker to replicate content between multiple FAST instances<br />
  17. 17. Search Abstraction<br />Created an internal, T-SQL based query language<br />Shielding users from the multiple sources of content<br />SharePoint lists<br />FAST full text for newsroom content<br />Autonomy indices for archived content<br />Autonomy indices for multimedia content to link<br />
  18. 18. Search Abstraction<br />request.SearchQuery = newSearchQuery();<br />request.SearchQuery.Query = <br />&quot;select top(1,50) * from FAST where filters(&apos;Obama AND mediatype=text&apos;) order by ARRIVALDATETIME DESC option( spellcheck=false, highlight=false )&quot;;<br /> <br /> <br />
  19. 19. Concurrent Workflow and Versioning<br />Breaking news collaboration doesn’t fit cleanly within the co-authoring model<br />Partial updates are evil – new versions replace, they do not merge<br />Any amount of latency interferes with very quick deadlines<br />Race conditions: Users need assurance that their story will move as-is<br />Users work on their own private snapshot and overwrite the latest revision<br />Last commit wins<br />
  20. 20. Concurrent Workflow<br />Using document sets to manage snapshots<br />demo<br />
  21. 21. Remember to fill out your evaluations onMySPCfor your chance to win two HD web cams and a designer mouse (3 prizes awarded daily)<br />
  22. 22. Learn More about SharePoint 2010<br />Information forIT Prosat TechNet<br /><br />Information forDevelopersat MSDN<br /><br />Information forEveryone<br /><br />
  23. 23. Are we at the start of Office as a development platform?<br />Why now?<br />A fundamental shift in thinking from the Office team that had for some time considered platform/file format to be a guarded secret. <br />We all use Office, why not build more client applications on a platform with 20 years of end user experience.<br />SharePoint as a BackOffice server.<br />Thou shalt build Web Apps! With virtualization, Office installations can be as easy as the web.<br />Great example is Gemini.<br />Today is good. Tomorrow will only be better.<br />
  24. 24. Appendix<br />Sample Demonstration Screen Grabs<br />
  25. 25. Publishing a Story, 1<br />
  26. 26. Publishing a Story, 2<br />
  27. 27. Publishing a Story, 3<br />
  28. 28. The Journalist UI<br />
  29. 29. © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.<br />The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.<br />