EuropeanaTech PGM12


Published on

A presentation of the EuropeanaTech network,, at the Europeana Project Group Meeting, Sept. 2012:

Published in: Technology
1 Like
  • Be the first to comment

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

No notes for slide

EuropeanaTech PGM12

  1. 1. EuropeanaTech - technical R&D in Europeana Antoine Isaac (with slides from Max Kaiser Maarten Brinkerink, Johan Oomen, Evelien Wolda, Marlies Olensky & Juliane Stiller) Europeana Project Group Meeting September 11 2012
  2. 2. Research and Development in Europeana context Identify Marketing Ingestion Evaluate Analyse External Programme m Pr R&D/expertise Management ea od lT uc ca tT ni ch ea Implement Te Conceptualise m Specify Product Development Network EDM R&D Agenda
  3. 3. TasksFoster a network of specialists from GLAM andresearch institutions, who can advice ontechnological topics when neededDevelop R&D agenda for Europeana: identify trends &gaps, who is working on them, how we can support themFeeding R&D results from the scientific / open sourcecommunity into the development of EuropeanaThe EDM model is improved and incrementally updatedInforming IT-related networks, e.g., the Linked Open Dataor Digital Libraries communities, on Europeana-relatedR&D. disseminate our partners’ technological advances
  4. 4. Supporting project: Europeanav2.0 WP7Tasks Developers Network Development of innovative applications for user interaction and UGC Semantic Web / Linked Data Multilingual Access / Translation
  5. 5. Supporting network: EuropeanaTech
  6. 6. EuropeanaTech CommunityCurrently: Task This period:• Persistent Identifiers • FLOSS inventory Developers Forces• EDM and FRBRoo Next period:• Hierarchies • Software development From MS37 Mission Statement: "The mission of the EuropeanaTECH community is to gather task forces on specific technical points (metadata display issues, extensions to the Europeana Data Model, etc) and foster a Europeana Software Developers Network”
  7. 7. network/europeana-tech/
  8. 8. Output 1: Inventory of FLOSS in the CulturalHeritage Domain Alr ead ent y 85 ries !
  9. 9. Output 2: Market study on semantic feature extraction  Tools for the extraction of concepts and named entities  Basis for decision-making for Europeana  Available on EuropeanaTech Wiki as living document
  10. 10. Two example foci: EDM and multilingualissues
  11. 11. Focus: EDM status
  12. 12. Focus: EDM status First implementation • Provided Objects, Web Resources, Aggregations, Agents, Concepts, Places and TimeSpans Documentation • Definitions, Primer, Mapping Guidelines, Object templates, XML schema, RDF/OWL ontology Prototyping ingestion with partners • CARARE, MIMO, HOPE, CulturaItalia Pilot export ESE->EDM as part of Ingestion chain ready in October
  13. 13. Focus: EDM next steps Assessing input data and processes with partners • Getting mappings from original data to EDM Validate existing choices of properties Propose refinements or extensions Adapt data dissemination channels to interoperability needs • Facilitate re-use of Europeana metadata by partners and third-parties
  14. 14. Focus: EDM next stepsMetadata enrichment Linking objects to contextual resources • GeoNames, VIAF, domain-specific thesauri Linking contextual resources • Thesaurus alignment Linking objects • Clusters, FRBRization
  15. 15. Focus: EuropeanaTech EDM task forces Model refinements on EDM  Task force on Hierarchical Objects  Task force on EDM-FRBRoo Application Profile
  16. 16. Focus: multilingual issues Multilingual display, retrieval and interactions are not commonly implemented in CH websites • State-of-the-art analysis of 50 cultural heritage websites
  17. 17. Dimensions of multilingual access Interface Search (query translation or document translation) Result presentation Browsing
  18. 18. Europeanas efforts Interface translated into 26 languages Query translation: only prototype Query result filtering by country/language Document translation (user enabled) Semantic contextualization of objects • Multilingual enrichment/annotation of metadata
  19. 19. Multilingual foci Focus on educating community • Multilingual dimensions and effects on display and retrieval • Multilingual handling in EDM and ESE • Ingestion of multilingual contextual resources (thesauri etc) R&D: better use of language resources • Natural language processing • NB: some of “our” resources (thesauri etc.) are also language resources!
  20. 20. Multilingual and semantics can go hand-in-hand
  21. 21. Fetching available linked dataE.g., from libraries
  22. 22. Interoperability Encouraging the use of RDF + common and simple elements
  23. 23. Interoperability Encourage the use of common and simple data elements<skos:Concept rdf:about=""> <skos:prefLabel xml:lang="fr">Piano carré</skos:prefLabel> <skos:prefLabel xml:lang="it">Pianoforte a tavolino</skos:prefLabel> <skos:prefLabel xml:lang="en">Square pianoforte</skos:prefLabel> <skos:prefLabel xml:lang="de">Tafelklavier</skos:prefLabel> <skos:prefLabel xml:lang="nl">Tafelpiano</skos:prefLabel> <skos:prefLabel xml:lang="sv">Taffel</skos:prefLabel> <skos:broader> <skos:Concept rdf:about=""> <skos:prefLabel xml:lang="en">Pianofortes</skos:prefLabel> </skos:Concept> </skos:broader></skos:Concept>
  24. 24. Multilingual Access: users back in the loop
  25. 25. EuropeanaTech: lessons being learnt Need for active community support • Highlight the added value to contribute to EuropeanaTech • Actively disseminate outcomes • Reach out to the wider community also outside de EU! Need to actively manage task forces: • Define stort-term, measurable goals • Provide communication support • Tasks are interleaved and should inform each other
  26. 26. How to contribute? Several levels: organization, advice, code, data…  Become a member of the EuropeanaTech community • mailing list, twitter…  Designate a "technical/R&D contact point" in their project?
  27. 27. How to contribute?  React to our deliverables  Contribute prototypes & demos in ThoughtLab  Contribute deliverables & software to mindmaps • semantic technology • should we create other mindmaps?  Contribute documented EDM metadata and mappings for next steps of EDM  Participate our coming meetings • how about a joint technical meeting in 2013?
  28. 28. Thank you!Antoine Isaac, Europeana