CMS And APIs At The Science Museum
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

CMS And APIs At The Science Museum

on

  • 2,833 views

Ben Morgan and Stephen Pope discuss how Eduserv built a content management system which worked with APIs and the Science Museum's complex content needs.

Ben Morgan and Stephen Pope discuss how Eduserv built a content management system which worked with APIs and the Science Museum's complex content needs.

Statistics

Views

Total Views
2,833
Views on SlideShare
2,827
Embed Views
6

Actions

Likes
0
Downloads
11
Comments
0

2 Embeds 6

http://www.slideshare.net 5
http://www.eduserv.org.uk 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

CMS And APIs At The Science Museum Presentation Transcript

  • 1. CMS & APIs at the Science Museum Ben Morgan & Stephen Pope Eduserv 2009
  • 2. Eduserv Eduserv is a not-for-profit IT services group delivering technology services to the public sector & the information industry. Using contributions generated from these activities the Eduserv Research Programme funds initiatives supporting the effective application of IT in education.
  • 3. What we do • Managed hosting • Complex websites • CMS & bespoke development • Integration & web services
  • 4. Sitecore CMS • Sitecore is a .Net development platform in its own right • At its most fundamental level it is very open & flexible • Sitecore can integrate with APIs of whatever specification required • Eduserv have more Sitecore developers than any other UK partner
  • 5. CMS vendor landscape Low Priced Mid Market Upper Tier Enterprise Hosted Open Source
  • 6. An application programming interface (API) is a set of functions, procedures, methods or classes that an operating system, library or service provides to support requests made by computer programs. David Orstein – Computer World (Wikipedia).
  • 7. “API = The nubby bit on a Lego brick” Aaron Straup-Cope from Flickr
  • 8. The Science Museum • Founded in 1857 with objects taken from the Great Exhibition in Crystal Palace • Focused on stimulating children's interest & curiosity in science • It is a very hands on place with many interactive exhibitions – it feels a bit like an amusement park • The special exhibitions are perhaps more dynamic than those of other museums…
  • 9. Alcock and Brown's Vickers Vimy biplane, first to cross the Atlantic 1919
  • 10. Babbage's Analytical Engine, 1834-1871 – the first automated calculating model
  • 11. The Science Museum & CMS • The Science Museum is a dynamic organisation with a clear web strategy • The focus of the strategy is around Sitecore • The CMS is to be the corner stone of all projects • Going to look at two projects & how the CMS has been used to deliver benefits for either information or education
  • 12. HANG ON TO YOUR SEATS! HERE COMES SOME TECH…
  • 13. “Launchball” • http://www.sciencemuseum.org.uk/launchpa d/launchball/ • “An interactive game for children to help promote learning and interest in Physics & the Sciences”
  • 14. `
  • 15. Created by Preloaded – a multi award winning creative team of people •Euro best - Gold Winner, Games •SXSW - Winner, Games & Best of Show •Flash in the Can - Winner, Technical Excellence •Museums & the Web - Winner, Innovation •D&AD - In-book Status •Creative Review Annual - In-book Status •Webbys - Finalist, Games •FWA - Site of the Day
  • 16. Launchball CMS Integration
  • 17. Restful API “Simple interface which transmits domain-specific data over HTTP without an additional messaging layer such as SOAP or session tracking via HTTP cookiesquot;
  • 18. “Brought to Life” • http://www.sciencemuseum.org.uk/broughtto life.aspx • “A solution to retrieve content from multiple collections databases into the CMS for web projects”
  • 19. •
  • 20. GOD Integration Layer
  • 21. “An application without APIs is like a house without doors.” Josh Walker, Forrester Research Inc.
  • 22. So add a line to every spec you release; “MUST include a strong API, SOAP or REST” It could make vast difference to the way your CMS works for you.
  • 23. Thanks for listening And thanks to these people, too; Luxtonnerre - http://www.flickr.com/photos/luxtonnerre/30122473 07/sizes/l/ Windell H. Oskay, www.evilmadscientist.com Stephen Pope – Eduserv Mike Ellis – Eduserv Tim Hobday – Eduserv The Science Museum Ben Morgan & Stephen Pope Eduserv