presentation museumnext

Post on 07-Jul-2015

1.583 Views

Category:

Self Improvement

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

Presentation Workshop Rijksmuseum API at MuseumNext Conference, Barcelona 2012. Inge Giesbers & Lizzy Jongma, Rijksmuseum Amsterdam

TRANSCRIPT

Open Data Workshop: The Rijksmuseum

Hacking Experience

Lizzy Jongma & Inge Giesbers

Our data is open!

Yes, you can

harvest it with

their API !

Did you know the

Rijksmuseum

opened their

data ?

Why open data?

• E-strategy

• Institutional values: authentic, quality, personal, innovative, simplicity

• Mission: ‘The Rijksmuseum connects people, Art and History’

• Interaction with the public

And what about the images?

• Open Cultuur Data

• Apps voor Nederland

• Europeana

Why now?

What did it take?

• An API (Application Programming Interface)• Registration of copyright data• Selection of copyrightfree objects

…. And a room full of nerds

Copyright project

• Unknown territory

• No fields for registration

• Comparative research

• Create awareness

How much data is open?

• 500.000 records in Adlib

• 250.000 records on our website

• 111.000 records in the API (criteria)

• ‘CC-by’ and ‘fair use’

Further steps in copyright

• Clear copyright• Explanation on the

website• Separate copyright

agreement

API, OAI-PMH…

• From Adlib to Open

• Users and sets, sets and users

• Harvest, query, set

• LOD, RDF, DC andprogrammers…

• Back end and user support

Rijksmuseum API

What is special?

• High quality images

• CC-by license metadataand images

• Largest open data art collection

What has been archieved so far?

• 16 apps• 207 harvests• Kennisnet,

ARTstor, Bioportaal, Les2.0

• Europeana

A few Examples:Faces of the Rijksmuseum

Iconclass browser

http://www.rijksmuseum.nl/api?lang=nl

Rijks Add notes

Rijksify

Further steps API

• Expansion of the Open Collection• User specific sets (Golden age, portraits,

tulips)• Search options• Various data formats• Connecting to other sites and portals• LOD, RDF

Lessons learned

• More apps and harvests than expected• Much more requests and questions

than expected• Positive publicity and feedback• No loss of income• No more angry colleagues (after a while)• Apps are difficult to integrate• Supprised by interest from portals and abroad• App contents are fun.

Enjoy! (but don’t expect them to solve allyour problems)

… Don’t show explicit art to American programmers

Any questions?

Inge Giesbers (Information Specialist)i.giesbers@rijksmuseum.nl

Lizzy Jongma (Datamanager)l.jongma@rijksmuseum.nl

top related