1. Europeana roadmap & EuropeanaLocal Olaf Janssen EuropeanaLocal Kick-off 25-27 June 2008, London

2. eContentplus 2008 submissions Proposals from the Europeana Office EuropeanaVersion1.0: project to launch the full Europeana service EuropeanaConnect: project to implement additional functionalities into Europeana

3. EuropeanaVersion1.0 (1/2) Creation of an operational Europeana service 1. Organisational / legal / finacial –Finding a viable organisational solution –Policy development –Creating a sustainable funding model. –Maintaining and extending a powerful alliance of stakeholders –Service agreements with bodies involved in running the service 2. Technical and Standardisation –Technical building of the service –Hardware, storage and bandwidth connected with running the service –Implementing functional specifications –Implementation of new plug ins and technologies –Implementation of new data and object models

4. EuropeanaVersion1.0 (2/2) 3. Content –Ingestion & management of partner content and continuous access to that content –Rights management and IPR –Creation of license and partnership agreements 4. Marketing the service to end users –Regular online & offline marketing –Promotion of standards and data models –Distribution to other channels for mash ups and re use

5. EuropeanaConnect Will deliver components to create fuller Europeana service –Europeana interface and client for mobile devices –Europeana OAI-PMH Infrastructure –Europeana Metadata Registry –Europeana Resolution Service for Persistent Identifiers –Multimedia Annotation Service –e-Books-on-Demand Service –Framework for deep-log-analysis

6. For content providers to Europeana

7. Benefits for content providers Exposes your content to wider user-groups Multilingual discovery of your content Tracks the movement of ideas across Europe Supports an interdisciplinary research approach Builds understanding of interoperability issues Promotes collaboration and knowledge exchange Exposes deeper-level material that search engines are less likely to find

8. The content requirements EDLnet Deliverables D2.2 and D2.5 provide technical requirements for content providers to have their data integrated into Europeana. Available at: http://www.europeana.eu/outcomes.php

9. The content requirements (1/2) Content holders need to provide Europeana with: –metadata files in (at least) unqualified Dublin Core(?)  OAI-repositories for harvesting –vocabularies in SKOS form –licensing and rights information –Persistent identifiers for digital objects,

10. The content requirements (2/2) –URL that points to the original digital object Access to the original digital object is via a link to the content provider site  Europeana will not store original objects! The provided elements will be aggregated into Europeana surrogates which are the basis for Europeana functionality The surrogate will include, for example, –a thumbnail –sample of audio content –Object level descriptive metadata –licensing and rights information at the object level –link to the original digital object

11. The standards OAI-PMH for harvesting SRU, SOAP, JSR and OpenSearch for external search and access XML for syntax SKOS, OWL/RDF(S) for semantics SPARQL for advanced search (but still discussing alternatives such as SQL, SeQL and Lucene) CIDOC/CRM and DCMI Abstract Model Metadata modelling (FRBRoo to be discussed) SAML, LDAP and OpenID for security and authentication Lots of others: WSDL, WAI, UNICODE UTF-8, XSLT, NACO, UNAPI, “See-also”, HTTP/HTTPS...

12. Themes for content providers (1/2) 5 main themes 1. Cities cities of the future/cities of the past migration trade and industry 2. Social life sport leisure clubs, groups and movements 3. Music popular music: from folk roots to downloads music theatre dance

13. Themes for content providers (2/2) 4. Crime and punishment crime on film and tv corruption scandals investigation and the rise of forensic science 5. Travel & tourism historical sites and tourist destinations sustainable tourism mapmaking

14.  Questions ?  Olaf.Janssen@kb.nl