From Athenawiki

Jump to: navigation, search

Contents

Technical specifications for a terminology management tool

Context

A benchmark on terminology resources and dedicated tools is being performed in the framework of the WP4 of the Athena project. One of the outcomes of this benchmark is that there is a lack for cultural institutions to have a complete software environment for managing terminology. Indeed when an institution intends to ingest into Europeana its digital collection and object descriptions, an effort about the terminology in use for these descriptions has to be done. The purpose of such a tool is to lessen the efforts of the institution for providing its terminology from its internal organisation and management to the final integration into Europeana.

This document intends to define the technical specifications of such a tool.

Needs

In ATHENA WP4, D4.1 study (Identification of terminology resources in European museums) has confirmed that a lot of European museums use an in-house non-standard terminology to describe their collections and objects. The cost implied by a reference terminology or specific needs (language, domain, …) are the main reasons for this choice. This means that these museums have a strong effort to make for expressing their descriptions with a reference terminology fitting with Europeana. Europeana mainly asks for terminologies expressed in SKOS and multilingual if possible.

Another important point is to enable a collaborative approach to lessen these efforts and also make terminology more lively.

A terminology management framework :

One solution consists of the design and the implementation of an integrated software environment for terminology management enabling any institution to find its way to manage its terminology according to Europeana ingestion.

A study of the information process (see the Annexes) concerning terminology management has already led us to consider an integrated software environment able to support a 6-step-chain of tasks:

1. Registration of a terminology in a repository
2. SKOSification of a terminology
3. Search and navigation into a network of vocabularies
4. Mapping of the terminology with a thesaurus
5. Enrichment of a thesaurus
6. Collaborative moderation of updates/modifications of the thesaurus

In our understanding, we consider that an ideal tool for terminology management would have as features: • To be a webservice: For collaborative work online
• To have a user-friendly GUI: Adapted for a non-expert use in European museums
• To combine open-source components: Such a service must stay independent of proprietary codes and formats
• To be logically structured with an intuitive Workflow: The user must find which actions to do according to his/her needs
• To be flexible enough to be adapted to new standards: What if SKOS is updated in a new version or evolving towards an ontology description?

Technical functionalities and features

The main functionalities and features expected for this integrated environment are listed according to the 6 steps introduced above:

1. Registration of a terminology in a repository


- Import functionality
- A terminology expressed in SKOS format
- Terminology in other format (OWL, …)
- Set of metadata for each terminology
- Edition and modification of the terminology metadata

- Export functionality
- Export in SKOS format
- Export in HTML or CSV format
- Use a stylesheet imported by the user for the export

2. SKOSification of a terminology



- Creation of a new terminology in the basic SKOS format or Athena SKOS-based format
- Conversion:
- Integration of a set of tools for helping the conversion into SKOS
- Mapping interface for matching any schema to the Athena schema.
- Edition of a registered terminology in SKOS
- Validation:
- Inclusion of a validation service (such as PoolParty validator?)
- connection to external validation services?

3. Search and navigation into a network of vocabularies



- Search and navigation in the concept tree (labels and relations)
- Browse each terminology within a same window/tab
- Possibility to browse several terminologies within a same window/tab
- Simple search and advanced search :
1. simple search: full text in all text labels and notes
2. advanced search:
1. specify the language
2. specify the type of content (label, note)
3. specify the exact match or related terms

4. Mapping of the terminology with a thesaurus


- graphical interface?
- semi-automatic mapping facilities

5. Enrichment of a thesaurus


- Workflow: Definition of roles and user rights for modification and validation of the terminology

6. Collaborative moderation of updates/modifications of the thesaurus



- Creation of a new terminology in the basic SKOS format or Athena SKOS-based format
- Search and navigation in the concept tree (labels and relations)

This page was last modified on 19 January 2011, at 10:54.This page has been accessed 4,927 times.