1. WHY API
at the National Heritage Board, Sweden
Leuven June 14 2012: Europeana Plenary
[www.slideshare.net/surikat]
[www.slideshare.net/surikat]
2. Hi, I´m Lars
The National Amréus, new
DG of the
Board. I´m on
twitter:
Heritage Board @larsamreus
Government agency
Heritage environment
Ancient monuments and historic buildings
Promote heritage as a valuable asset
Insight rather than authoritarian
(not a museum)
wikimedia
3. Online
• 800 000 ancient monuments sites (Europeana via Carare)
• 80 000 protected buildings (soon in Europeana)
• 100 000 images (In Europeana)
5. New media team
at the Board
Johan Matilda Sophie Marcus Maria Henrik
6. What are we up to?
SOCH
Platsr.se – digital storyteling
WIR & WdevIR
Carare (Europeana)
Europeana Awareness
Strategy for Digitization
Linked Open Data
IPR and licensing issues
7. Questions:
Why did we decide to implement API?
What are the benefits?
Do you have any suggestions from your
experience using the API implementation?
10. We need to adapt in
order to stay relevant
in a digital society!
11. Users in SE
- 50 % of 3-year old kids use the Internet
- 96 % of young ppl uses social media
- +65 year fastest growing user group
- Mobile surfing is growing dramtically
[”Swedes and the Internet 2011”. .SE (The Internet Infrastructure Foundation) 2011]
12. Users
- Want to contribute - not only consume!
- Want information now – not in 10 days.
- Want to reuse information!
14. Insights:
We cannot provide services for all
users!
We are not the most innovative app
developers!
There´s no point in controlling use!
15. New agenda
Make things as easy as possible
for as many as possible
to use and reuse information.
16. New agenda
Facilitate open access to
information via API
(Facilitate mash-ups)
Focus on improving quality!
17. Today
Until recently…
GLAM create apps for experts
Agencies PR
12-06-14 17
18. Today and future
Today
learning
internal use
Museums
research
Agencies
PR
Universities
create apps for experiences
Associations
creativity
Enterprises
Schools
…or just for fun
Individuals
12-06-14 18
21. SOCH
(Swedish Open Cultural Heritage)
• ”National Europeana”
• Museum collections + monuments + buildings
• 40 institutions
• National – Regional - Local
• 4,2 million objects
• API - 10 apps
• Aggregator for Europeana
22. “Linking Open Data cloud diagram, by
Richard Cyganiak and Anja Jentzsch.
http://lod-cloud.net/” CC-BY-SA
“Linking Open Data cloud
diagram, by Richard Cyganiak
and Anja Jentzsch. http://lod-
cloud.net/”
23. API
Europeana
Google Yellow Pages
Site
WEBSITE/APP
Regional Historic
Local Tourism My Heritage Kringla.nu
Portal Society
Mobile
History
API
OTHER APIs
(Europeana, Google, SOCH Service
Wikipedia, LIBRIS etc)
XML
Läns-
Läns-
Läns-
museum
Info manager
National Sw Läns-
museum
Regional History UGC
museum Local
Musem NHB museum Museums
museum Socities hub
24. KRINGLA.NU
MASHUP
semantic links
tags
georeference
etc
API API API API
SOCH Google Maps Wikipedia
Europeana (Panoramio
WebService Streetview) LIBRIS
XML
Läns-
Läns-
Läns-
museum
Info manager
National Sw Läns-
museum
Regional History UGC
museum Local
Musem NHB museum Museums
museum Socities hub
25. Google
API
Tidsresan/
Museisök Kringla.nu
Time Mash
Fornfynd IOS
API
K-SAMSÖK
Wikipedia
WebService
Libris
XML
?
Läns-
Läns-
Läns-
museum
RAÄ Läns-
museum Hembygds-
Läns- Kommun-
MUSEUM museum
Fornsök museum
museum museum museum UGC
26. Questions & Answers:
Q: Why did we decide to implement API?
A: Facilitate a standardized access to data.
Q: What are the benefits?
A: More use of data, varied applications
Q: Suggestions based on experience from API implementation?
A: Be pragmatic, don´t forget licensing
27. "If your content is not
interoperable, it's not
findable. If it's not findable,
who cares about it?"