• Aucun résultat trouvé

A User-Centred Evaluation Framework for the SeaLife Semantic Web Browsers

N/A
N/A
Protected

Academic year: 2022

Partager "A User-Centred Evaluation Framework for the SeaLife Semantic Web Browsers"

Copied!
1
0
0

Texte intégral

(1)

A User-Centered Evaluation Framework for the SeaLife Semantic Web Browsers

Gayo Diallo1, Gemma Madle1, Gawesh Jawaheer1, Patty Kostkova1, Dimitra Alexopoulou

2

, Robert Stevens

3

,Simon Jupp

3

,Khaled Khelif

4

1

City eHealth Research Centre, City University of London, London, UK

2

Bioinformatics Group, Biotechnological Centre T U Dresden, Dresden, Germany

3

School of Computer Science, University of Manchester, Manchester, UK

4

INRIA Sophia Antipolis Méditerranée, France

Abstract

The SeaLife project1 is investigating semantic browsing and its application to the life science domain. SeaLife’s main objective is to develop the notion of context-based information integration by extending three existing semantic web browsers (SWB) to link the existing Web to the eScience infrastructure. The browsers under development are COHSE2, Corese3 and GoPubMed4, all of which already offer some semantic browsing functionality. This poster presents a user-centered evaluation framework for the SeaLife browsers. There is a need for a common framework and we will focus on evaluating the end-user perception of the SWB and how a SeaLife browser helps them gather desired information. The criteria used in the evaluation is related to the user experience and the impact the semantic browsers have on two case studies involving the NeLI portal5 and PubMed6. They will help to confirm or contradict the following hypotheses: i) having a SWB reduces the length of the pathway taken or time taken to find information or perform a task; ii) having a SWB reduces the number of links to be explored and the ability to explore information the user may not have been aware of; iii) users think that semantic links/ranking is a good help and this facilitate the use of the system; iv) users always prefer using the system with the semantic browser capability. Users range from infectious disease practitioners to molecular biologists, who will perform a set of tasks in both workshop and online-based evaluations. Three sources will provide the necessary data: i) Web server logs collected automatically as users navigate the portals; ii) a task performance questionnaire constituted by a set of tasks to be performed; iii) a user satisfaction and attitude questionnaire about the system with and without the semantic browsers.

1 http://www.biotec.tu-dresden.de/sealife

2 http://cohse.cs.manchester.ac.uk/

3 http://www-sop.inria.fr/edelweiss/software/corese

4 http://www.gopubmed.com/

5 http://www.neli.org.uk

6 http://www.ncbi.nlm.nih.gov/pubmed/

Références

Documents relatifs

Static content (e.g., an SVG world map) will be referenced as Datasource and composed with dynamic content built from RDF Datasources (e.g., the FAO Geopolitical Ontology) using

Concepts and relations in BabelNet are harvested from the largest available semantic lexicon of English, WordNet, and a wide-coverage collaboratively-edited encyclopedia, Wikipedia..

We created this semantic model to conform to the rules and regulations of the Dutch parliament, although the model can be easily adapted to follow different rules (of

We present a study of 17 social applications to define requirements and attributes for a common user model that allows sharing of user data and analyze what is needed to enhance

Such a framework would be useful in various application scenarios, ranging from filtering and processing social networking event streams, over integrating and aggregating events

Finally, when a retrieved answer is to be inserted in the user edited docu- ment ((rich) text area), in order to preserve the semantic markup, since the user produced content is

We propose a two step bootstrapping architecture of integrating relational databases with the Semantic Web by first generating a “database- derived putative ontology” and

Setting up SemWIQ requires: (1) setting up a mediator host, (2) setting up wrappers, (3) specification of mappings from local concepts (i.e. database tables and attributes) to