Download DE3.2 Accessibility and Multilingual Support for ECLAP Solution

DE3.2– Accessibility and Multilingual Support for ECLAP Solution
ECLAP Best Practice Network
multilingual metadata indexing and query is reported. Details about the elements that have to be indexed,
metadata indexing, multilingual indexing and search and faceted search are provided. Section 6 refers to
multilingual portal interface and automated translation, while section 7 deals with multilingual portal
interface validation and acceptance process. Multilingual SKOS automated translation is addressed in
section 8, and multilingual taxonomy editor is described in detail in section 9. Section 10 refers to
multilingual metadata and GUI on mobile devises. In section 11 accessibility analysis issues are addressed.
More precisely, there is an overview of available W3C accessibility assessment methodologies and tools,
concluding to strategies for assessing the accessibility of ECLAP portals: metadata ingestion servers, social
service portal and mobile portal. Finally, in section 12 there is reference to automatic translation tools.
3 Multilingual Metadata Automated Ingestion
3.1
Metadata Ingestion Overview
As described in DE3.1 (section 6) and DE4.1 the basic workflow for massive content and metadata ingestion
within ECLAP consists of the following steps:
1. Content partners provide metadata in their native or desired language using the ECLAP Metadata
Ingestion Service (EMIS) portal, metadata should be provided as XML, it is directly uploaded as a
file or harvested them via an OAI-PMH access.
2. Each content partners maps its own metadata XML structure to the ECLAP metadata XML format ,
this will is done using the EMIS portal to define a XSLT that is used in the mapping phase;
3. In case of a OAI-PMH access the EMIS will crawl the content partners archives and it acquires the
original metadata;
4. When the original metadata is acquired it is mapped to the ECLAP metadata format and stored and it
is made available toward the ECLAP Social Service Portal (ESSP) via an OAI-PMH server;
5. The ESSP regularly crawls the EMIS to acquire metadata represented using the ECLAP metadata
format and in the original metadata format
6. For each metadata record acquired the ESSP will download the content files associated with it, ESP
will use the content urls defined in the ECLAP metadata (content may be also acquired using Hard
Disks, DVDs in case content size is too high for a rapid download)
7. Each piece of content acquired will be formatted, adapted and a complete media content will be
produced in the ESSP portal with the associated metadata;
8. Each produced content will be available in the ESSP portal for:
• metadata enrichment
• metadata translation
• IPR definition
these activities are orchestrated by using an internal workflow management tool integrated in the
portal.
9. When the content and the associated metadata are ready they will be made available (on the basis of
the IPR defined) for access to the final users accessing on the ESSP portal.
10. Metadata will be published on Europeana and Europeana users will reach the ESSP portal to see the
content.
In the Cultural Content Metadata Space, the largest technological challenge is to ensure syntactic and
semantic interoperability across the different types of metadata that exist in the Cultural Heritage sector. The
technical standards enabling interoperability form an important dimension of this work. In order to achieve
semantic interoperability within ECLAP we need a common automatic interpretation of the meaning of the
exchanged information, i.e. the ability to automatically process the information in a machine-understandable
manner. The first step of achieving a certain level of common understanding is a representation language that
ECLAP project
8