Europeana Connect All-Staff Meeting


Published on

Max Kaiser, Austrian National Library
Berlin, May 10–12, 2010

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Commission is our father, Europeana is our mother…
  • Europeana Connect All-Staff Meeting

    1. 1. Introduction EuropeanaConnect All-Staff Meeting Berlin, May 10–12, 2010 Max Kaiser, Austrian National Library
    2. 2. Welcome to the All-Staff Meeting!
    3. 4. Introduction <ul><li>This is a quite big meeting…. </li></ul><ul><li>This is the end of successful project year… </li></ul><ul><li>Project established as largest single Europeana technology provider </li></ul><ul><li>Goals of the All-Staff Meeting: </li></ul><ul><ul><li>Get up-to-date about the different strands of work </li></ul></ul><ul><ul><li>Open the “work silos” and profit from synergies </li></ul></ul>
    4. 5. Meeting structure <ul><li>Plenary sessions </li></ul><ul><ul><li>Update on achievements in all work packages </li></ul></ul><ul><ul><li>Demonstrations of project results </li></ul></ul><ul><ul><li>Updates on Europeana and sync with Europeana developments </li></ul></ul><ul><ul><li>Administrative issues </li></ul></ul><ul><ul><li>Dissemination and project marketing </li></ul></ul><ul><li>Parallel sessions </li></ul><ul><ul><li>All-Developers meetings </li></ul></ul><ul><ul><li>Work packages meetings </li></ul></ul><ul><ul><li>Inter-WP meetings for synchronisation </li></ul></ul>
    5. 6. Looking foward to three productive and pleasant days!
    6. 7. Status of EuropeanaConnect EuropeanaConnect All-Staff Meeting Berlin, May 10–12, 2010 Max Kaiser, Austrian National Library
    7. 8. A unusual project … <ul><li>EuropeanaConnect is a unusual European project: </li></ul><ul><ul><li>We don't only have to deliver according to our Description of Work </li></ul></ul><ul><ul><li>But also according to the release planning and requirements of Europeana </li></ul></ul><ul><li>In the end: we will be measured for our success in delivering sustainable products for Europeana </li></ul><ul><ul><li>This is what will remain from the project (hopefully…) </li></ul></ul><ul><li>In contrast to many other projects, most EuropeanaConnect deliverables are not prototypes but should be production-ready components </li></ul><ul><li>Requires a very different project culture and a different approach to planning! </li></ul>
    8. 9. Rhine and Danube…
    9. 10. Complexity and synchronisation <ul><li>Main challenge in year 1 : </li></ul><ul><ul><li>Synchronise the project with the requirements and planning of Europeana </li></ul></ul><ul><li>Europeana Techical Requirements: </li></ul><ul><ul><li>Use cases </li></ul></ul><ul><ul><li>Coding requirements </li></ul></ul><ul><ul><li>Development environment </li></ul></ul><ul><ul><li>Release schedule </li></ul></ul><ul><li>Europeana Business and Policy Requirements: </li></ul><ul><ul><li>Branding and marketing </li></ul></ul><ul><ul><li>Data Provider Agreements (Licensing Framework) </li></ul></ul><ul><ul><li>User Generated Content Policy (Annotations) </li></ul></ul><ul><ul><li>User Testing </li></ul></ul>
    10. 11.
    11. 12. Key Objectives of Europeana Connect <ul><li>Provide a critical mass of audio content to Europeana and implement an audio-enabling infrastructure </li></ul><ul><li>Build the Semantic Layer for Europeana </li></ul><ul><li>Facilitate multilingual access to Europeana </li></ul><ul><li>Develop novel access channels to Europeana (like mobile access) </li></ul><ul><li>Provide tools and methodologies for user-driven development and for testing and evaluation </li></ul><ul><li>Build value-added services (like e-Books-on-Demand) </li></ul><ul><li>Implement key infrastructure components (like OAI-PMH infrastructure) </li></ul><ul><li>Build the Europeana Licensing Framework </li></ul><ul><li>Enable stronger and wider collaborative networking </li></ul>
    12. 13. Achievements in Year 1
    13. 14. Add the music dimension to Europeana
    14. 15. New audio content for Europeana <ul><li>EuropeanaConnect will add the music dimension to Europeana </li></ul><ul><ul><li>WP6, lead by RBB </li></ul></ul><ul><ul><li>Five audio archives are consortium members </li></ul></ul><ul><ul><li>Continuous approach to involvement of new audio archives for the entire duration of the project </li></ul></ul>
    15. 16. Main strands of work / Highlights | 1 <ul><li>Europeana Audio Aggregation Platform (AAP) </li></ul><ul><ul><li>Based on already existing DISMARC portal and infrastructure </li></ul></ul><ul><ul><li>Used for harvesting, analysing and storing audio metadata </li></ul></ul><ul><ul><li>Mapping adjusted, improved connectivity and more storage space on server (used by audio content providers) </li></ul></ul><ul><ul><li>New audio integrated by upload and by links into the AAP </li></ul></ul><ul><ul><li>Data provision for Europeana using OAI-PMH </li></ul></ul><ul><li>How to start? </li></ul><ul><ul><li>Audio Starter Kit on EuropeanaConnect Website </li></ul></ul><ul><ul><li>Describes process of providing audio content to Europeana via the AAP </li></ul></ul>
    16. 17. Main strands of work / Highlights | 2 <ul><li>Already 41.000 items aggregated from 100 collections in 16 countries </li></ul><ul><ul><li>Most items already available via Europeana </li></ul></ul><ul><li>Estimated 150.000 – 200.000 music tracks by project end </li></ul><ul><li>Continuous dissemination, Newsletters, personal contacts etc. </li></ul><ul><li>Targeting at and in contact with more than 300 potential partners </li></ul>
    17. 18. Challenges / Next Steps <ul><li>Challenges: </li></ul><ul><li>Uncertainty about IPR issues underlying most communications </li></ul><ul><ul><li>Approached by delivering necessary information </li></ul></ul><ul><li>Audio archives extremely hesitant towards joint operations </li></ul><ul><ul><li>Answered by various activities </li></ul></ul><ul><li>Only now Europeana Data Provider Agreement available </li></ul><ul><li>Next steps: </li></ul><ul><li>Workshop in September </li></ul><ul><li>Active newsletter publishing </li></ul><ul><li>Handbook for content owners under preparation </li></ul><ul><li>Work with the provider agreement </li></ul>
    18. 19. Building the Semantic Layer
    19. 20. Build the Europeana Semantic Layer <ul><li>WP1, lead by HUB </li></ul><ul><li>Organise Europeana data space as network of interlinked resources for object discovery and further use </li></ul><ul><ul><li>Prerequisite for integration of and with other semantically aware WWW services </li></ul></ul><ul><li>Build a repository of harvested semantic resources </li></ul><ul><ul><li>Vocabularies, classification schemes … </li></ul></ul><ul><li>Convert data into semantic representations </li></ul><ul><ul><li>Semantic processing will mostly use SKOS </li></ul></ul><ul><li>Semantically enrich Europeana content by mapping it to these semantic representations </li></ul>
    20. 21. Main strands of work / Highlights <ul><li>Survey of controlled and structured vocabularies among Europeana data providers </li></ul><ul><li>Successful migration of selected vocabularies to SKOS </li></ul><ul><li>Specification of semantics functionality </li></ul><ul><ul><li>Checking with selected expert users </li></ul></ul><ul><li>Substantial contribution to the Europeana Data Model (EDM) </li></ul><ul><ul><li>Specification and stabilisation of the EDM </li></ul></ul>
    21. 22. Challenges and next steps <ul><li>Challenges: </li></ul><ul><li>Triggering the EDM development </li></ul><ul><li>Getting commitment for an EDM-based planning </li></ul><ul><li>Next steps: </li></ul><ul><li>Contribute to Europeana v1.0, making the EDM and related functionality part of the 'Danube' specifications </li></ul><ul><li>Continue work on data migration and (semi-)automated object contextualisation </li></ul>
    22. 23. Multilingual Access
    23. 24. Multilingual Access to Europeana <ul><li>WP2, lead by HUB </li></ul><ul><li>Provide multilingual access capabilities for Europeana </li></ul><ul><ul><li>Users should be able to find relevant content even if its not described in their native / preferred language </li></ul></ul><ul><li>Build Europeana Repository of Language Resources </li></ul><ul><li>Tools for multilingual mapping of controlled vocabularies </li></ul><ul><li>Suite of translation services for querying and browsing </li></ul><ul><li>Supported set of languages: </li></ul><ul><ul><li>Start with English, French, German, Italian, Spanish, Polish </li></ul></ul><ul><ul><li>Expand with Dutch, Hungarian, Portuguese, Swedish </li></ul></ul>
    24. 25. Main strands of work / Highlights <ul><li>Report on User Preferences and Information Retrieval Scenarios for Multilingual Access in Europeana </li></ul><ul><li>Specification and development of the Europeana Language Resources Repository </li></ul><ul><ul><li>Currently in review </li></ul></ul><ul><li>Multilingual mapping of controlled vocabularies </li></ul><ul><ul><li>Languages and vocabularies for selection </li></ul></ul>
    25. 26. Challenges / Next steps <ul><li>Challenges: </li></ul><ul><li>Data gathering </li></ul><ul><li>Licensing issues </li></ul><ul><li>Criteria for construction of repository </li></ul><ul><li>Evaluation of language resources </li></ul><ul><li>Next steps: </li></ul><ul><li>Populating the Europeana Language Resource Repository </li></ul><ul><li>Selection of vocabularies in different languages for mapping </li></ul><ul><li>Query Translation Module </li></ul>
    26. 27. What do users really want?
    27. 28. User Orientation – Why, How? <ul><li>Why: </li></ul><ul><ul><li>We want Europeana to be used widely by people </li></ul></ul><ul><ul><li>We are not necessarily identical with these ”people” </li></ul></ul><ul><li>How: </li></ul><ul><ul><li>Log file analysis </li></ul></ul><ul><ul><li>Personas </li></ul></ul><ul><ul><li>Surveys </li></ul></ul><ul><ul><li>User Tests </li></ul></ul><ul><li>Part of WP3, lead by KB-DK </li></ul>
    28. 29. Log File Analysis <ul><li>Task 3.1, UCLC </li></ul><ul><li>Log File Analysis for Europeana to evaluate the use of the services </li></ul><ul><ul><li>How do users really navigate and search in Europeana? </li></ul></ul><ul><ul><li>Method: Deep log analysis </li></ul></ul><ul><ul><li>First log file analysis report fed into version 1 </li></ul></ul>
    29. 30. Personas / User Testing <ul><li>Task 3.2, KB-DK </li></ul><ul><li>Development of Europeana Personas </li></ul><ul><ul><li>Archetypical representations of our users </li></ul></ul><ul><ul><li>Workshop on Personas </li></ul></ul><ul><ul><li>Personas Catalogue completed </li></ul></ul><ul><ul><li>7 personas and relating scenarios defined </li></ul></ul><ul><ul><li>Should guide development process </li></ul></ul><ul><li>User Testing of Europeana services with different user communities </li></ul><ul><ul><li>Registry of Test Users </li></ul></ul><ul><ul><li>First draft of Usability Guidelines </li></ul></ul>
    30. 31. New Access Channels to Europeana
    31. 32. Spatio-temporal User Interface <ul><li>Task 3.3, UGOE </li></ul><ul><li>Make use of time-related and geographical metadata of the Europeana Semantic Layer </li></ul><ul><li>Provide a new visual access channel for Europeana </li></ul><ul><ul><li>Combination of spatial and temporal metadata for visualisation </li></ul></ul><ul><ul><li>Interactive and generic map of geo-related tagged events, places and characters in Europe – combined with timeline </li></ul></ul><ul><li>Prototype of spatio-temporal interface and search available </li></ul><ul><ul><li>Pure JavaScript based approach on the client side </li></ul></ul><ul><ul><li>Different possible back-ends for maps </li></ul></ul>
    32. 33. Prototype of the Spatio-temporal User Interface
    33. 34. Mobile Access Channel to Europeana <ul><li>Task 3.4, OFFIS </li></ul><ul><li>Generic Mobile Client, adapting to the user‘s mobile device </li></ul><ul><li>2 main requirements: </li></ul><ul><ul><li>Adaptation of the mobile Europeana portal to the capabilities of the user's mobile device </li></ul></ul><ul><ul><li>Location-based searching </li></ul></ul><ul><ul><ul><li>Allow users to search for works inside Europeana around their current position </li></ul></ul></ul><ul><li>Integration with Europeana </li></ul><ul><li>Basic mobile interface for Rhine Release </li></ul>
    34. 35. User Generated Content
    35. 36. Annotation Service <ul><li>Task 5.6, ARC-AIT </li></ul><ul><li>Allows users to make their own contribution to Europeana content </li></ul><ul><li>Annotation of multimedia resources </li></ul><ul><li>Comments, discussion, linking </li></ul><ul><li>Add value to existing content </li></ul><ul><li>Enhance Europeana searchability through user-provided metadata </li></ul><ul><li>Annotation Tool Suite fully integrated with the Europeana Portal </li></ul><ul><ul><li>Acceptance tests have been executed, currently under review </li></ul></ul>
    36. 37. Image Annotations
    37. 38. Video Annotations
    38. 39. eBooks-on-Demand
    39. 40. eBooks-on-Demand <ul><li>Task 5.7, UIBK </li></ul><ul><li>Integration of eBooks on Demand (EOD) Service into Europeana </li></ul><ul><ul><li>Existing digitisation-on-demand service </li></ul></ul><ul><ul><li> </li></ul></ul><ul><li>Allow for an automatic and generic transfer of Books from EOD to Europeana </li></ul><ul><li>Status: </li></ul><ul><li>EOD harvesting and metadata aggregation infrastructure implemented </li></ul><ul><li>EOD workflow software adapted to include workflow for metadata submission and Print-on-Demand </li></ul><ul><li>1st prototype of the EOD connector will be implemented by July </li></ul>
    40. 41. Back-office Components
    41. 42. Europeana OAI-PMH Management Infrastructure (REPOX) <ul><li>Part of WP5, managed by ARC-AIT </li></ul><ul><li>Task 5.3, IST </li></ul><ul><li>REPOX: Service for metadata harvesting from a large number of OAI data providers </li></ul><ul><li>Management of OAI data providers of administration of harvested metadata records </li></ul><ul><li>First REPOX prototype available </li></ul><ul><li>Functionally complete version in June </li></ul><ul><li>Aligned with Europeana technology specifications in October </li></ul>
    42. 43. Metadata and Service Registries <ul><li>Europeana Metadata Registry </li></ul><ul><ul><li>Task 5.1, IST </li></ul></ul><ul><ul><li>Registration and management of metadata terms and schemas created by various communities in multiple contexts </li></ul></ul><ul><ul><li>Specification and Design document in review </li></ul></ul><ul><li>Europeana Service Registry </li></ul><ul><ul><li>Task 5.2, KB </li></ul></ul><ul><ul><li>Will manage service descriptions of Web Services and support integration of external services into Europeana </li></ul></ul><ul><ul><li>Final prototype and documentation delivered </li></ul></ul><ul><ul><li>Server integration for both Europeana and The European Library will be implemented by end of May </li></ul></ul>
    43. 44. Europeana Persistent Identifier Resolution Service (ERDS) <ul><li>Task 5.4, DNB </li></ul><ul><li>Meta-Service: forward Persistent Identifier resolution requests to resolution services of national libraries and other identifier networks </li></ul><ul><li>Two-day workshop on PIs on 17/18 February 2010 at DNB in Frankfurt </li></ul><ul><ul><li>Report available on EuropeanaConnect Website </li></ul></ul><ul><li>Alpha version of ERDS available </li></ul><ul><li>Final version will be implemented by July </li></ul>
    44. 45. Integration of Geographical Information Services <ul><li>Task 5.5, BNP </li></ul><ul><li>Geoparser and Gazetteer: will enrich Europeana metadata and content with explicit geographical metadata and references </li></ul><ul><li>Protoypes and showcases of both tools available </li></ul><ul><li>2nd Protoypes will be implemented by July </li></ul>
    45. 46. And now for the legal stuff…
    46. 47. Europeana Licensing Framework <ul><li>WP4, BNL </li></ul><ul><li>EuropeanaConnect is building the Europeana Licensing Framework </li></ul><ul><li>Goals: </li></ul><ul><ul><li>Create and validate the Data Provider and Aggregator Agreements which govern the Europeana Rhine release </li></ul></ul><ul><ul><li>Create the draft Europeana Licensing Framework and validate it </li></ul></ul><ul><ul><li>Build, test and validate tools for implementation of the Framework </li></ul></ul>
    47. 48. Main strands of work / Highlights <ul><li>Data Provider and Data Aggregator Agreements </li></ul><ul><ul><li>Collecting requirements, several consultation rounds and final validation for Rhine Release </li></ul></ul><ul><ul><li>Final versions released in late April </li></ul></ul><ul><li>Europeana Public Domain Charter </li></ul><ul><ul><li>Controversial topic, as tightly linked to funding of digitisation programs </li></ul></ul><ul><ul><li>Endorsed by Europeana Foundation and European Commission </li></ul></ul><ul><ul><li>Positive reactions </li></ul></ul><ul><li>Public Domain Helper tools </li></ul><ul><ul><li>Defining decision trees to translate the law into a tool to decide if a work is in the public domain </li></ul></ul><ul><ul><li>Available in Beta Version </li></ul></ul>
    48. 49. Challenges / Next steps <ul><li>Multi stakeholder nature of rights issues made progress in legal questions slow and complex </li></ul><ul><li>Next steps: </li></ul><ul><ul><li>Collecting feedback on agreements from commercial partners and those beyond the immediate cultural heritage sector </li></ul></ul><ul><ul><li>Planning the Danube legal framework </li></ul></ul>
    49. 50. Image Credits <ul><li>http:// </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li>,_Berlin,_Hochhaus_Sender_Freies_Berlin.jpg </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li>http:// =Datei:Donaueschingen_Donauzusammenfluss_20080714.jpg&filetimestamp=20090102094801 </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li>Max Kaiser </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li>Max Kaiser </li></ul><ul><li> </li></ul><ul><li>http:// </li></ul><ul><li>http:// </li></ul><ul><li>http:// </li></ul><ul><li> </li></ul><ul><li>,_Berlin,_Hochhaus_Sender_Freies_Berlin.jpg </li></ul>
    50. 51. [email_address] http:// http:// http:// http:// http://
    51. 52. Looking forward to a successful and productive meeting!