the europeana api strategy
DESCRIPTION
A very brief presentation on the Europeana API Strategy presented at the Open Cultuur Data Masterclass April 23rd 2012. The presentation was not focused on technology but on what to consider when deciding to (or not) to develop an API and how to relate that to your existing strategy, plans and activities.TRANSCRIPT
The Europeana API StrategyAnd what I think you can take away from it
David Haskiya, Product Developer
API Strategy? We don’t have one! Let me tell you why.
Mission and Strategy
“Europeana enables people to explore the digital resources of Europe's museums, libraries, archives and audio-visual collections. It promotes discovery in a multilingual space where users can engage, share in and be inspired by the rich diversity of Europe's cultural and scientific heritage.”
But how? We try to answer that in our strategy: A multi-channel approach combining end-user services, content re-use services and social media.
What is an API?
Application Programming InterfaceWell, that’s not very understandable…
OK, let’s try this: It’s what a developer queries, reads from and writes to when developing servicesFor example: An API is what allows other sites than Google Maps to have interactive (Google) maps on them
The API is one among many tools
Europeana Distribution toolsThe portal
Semantic mark-up
Search Engine Optimization
The API (and programming libraries, re-use widgets)
Linked Open Data, dumps and SPARQL (pilot)
Wikimedia Commons batch upload (planned development)
The Plan 1.0
The first plan in brief
Develop a simple search API5 Beta developers from within the network
Launch with a HackathonSales: Target our high-traffic partners for adoption
To maximize referral traffic
But this was ditched when the commission made a call
KPI: 20 API-implementations by end of 2011We had 19 by the way
As a proportion of total traffic API-referral traffic is small (but it shows deep engagement)
Hack4Europe!
4 hackathons in 4 countries with a focus on non-GLAM developersGoal: To show the potential of Open Data in the European knowledge economyResults:
70 prototypes
Increased acceptance within our network for Europeana as platform
Increased awareness of the necessity for Openness
Problem 1: Our (meta)data isn’t Open so prototypes remain prototypesProblem 2: We lacked resources to do Hack4Europe AND target our major partners
The Plan 2.0
The second plan in brief
Develop an improved APIBased on developer feedback
Automated API-management
Launch when the Data Exchange Agreement takes effectThe DEA makes our metadata Open thus allowing for commercial use of our API
The Europeana Licensing Framework clarifies re-use of partner content
Sales: Target our high-traffic partners for adoption and investigate PPPs with select commercial companiesCreate a Developer Outreach Programme
Of which Hack4Europe 2012 is a component
The Europeana API version 2.0 (Q3 2012)
Is under developmentSimpler for developers (REST,JSON)
More powerful (anything we can do, you can do)
More scalable (logging, throttling, direct sign-up)
Write functionality for user annotations (OAuth)
Better documented (interactive docs, API console)
Direct sign-up for API-keyIs paired with a Development Outreach Programme
Hack4Europe 2012 in May and June
Copenhaguen, Warzaw, Leuven and Berlin
Will be an Open APIMade possible by the new Data Exchange Agreement
What’s your strategy and plan?
Do we need to build an API?
It depends…On your mission and how to best accomplish it
Does it have to be public?No, you could start with an internal API, perhaps between you Collection Management System and Content Management System
Does it have to be Open?No, but usually difficult to get a good Return on Investment if you not
Some API wisdom, Strategy and Planning
Integrate your API in the overall long-term strategyRealizing they’re one means among many, not the only means and not a goal unto itself
Make the business case for the API customerIt’s not about you
Cases and testimonials over statements
Plan your API-activitiesSet goals, define metrics and measure them
Hint: For most GLAMs it won’t be quantity of web traffic
Communicate your APIBuild it and they will not come!
Sales and Developer outreach are 2 different things
Hackathons are probably your best tool to build awareness and generate buzz!
Some API wisdom, low threshold
Clear Terms of UseBy whom and for what purpose
Demystify, undramatize!
Clearly licensed contentCreative Commons
Open Data makes for clarityLow threshold of adoption
Low negotiation cost
Tech choices and guidelines
Consider whether you need to build an API yourselfYour CMS may come with one out of the box
As a Europeana partner you already have one
REST over SOAPJSON over XMLClear versioningClear SLAEnsure you can log and follow up on your metricsBuild you own services based on the API you offer othersInteractive documentation over static documentation
Also libraries, code snippers, how-to’s, case studies
Improve iteratively based on developer feedback
That was it! Questions?
Please contact me if you want to know more or use our API!
Email: [email protected]
Twitter: @david.haskiya