UK-based developments in online thesauri for

taxonomic information

Copp, C., Grant, M., Hewzulla, D., Hussey, C., Robinson, J., van Breda, J. & White, R.

Why do we need a thesaurus?

Improve indexing Standardise query terms for better retrieval Links to synonyms and overlapping terms Expand or narrow queries Links to other information systems Potential to build knowledge-bases Potential to provide checklists for data entry

UK National Biodiversity NetworkThe Recorder ProjectBioCASE

Recorder 2002 - NBN Taxon & Biotope Dictionaries

Submit search terms

Master Thesaurus

On-lineThesauri

Static Lists

Maintained Lists

Published Standards

Agreements to copy terms & updates

Copy basicTerms

Check for and Add Terms

Copy terms

Check for term

Possible links by indexing or data access and reporting software to check for terms not in master thesaurus or get added value data

User Interface

Thesaurus Interface

Wrapper, API or copy of Master?

Other potential products derived from or using Thesaurus

Derive equivalent and related terms

Users

Sources Management Applications Use

Supply search terms

Partner Databases

Data access and reporting software

Indexing software

Central Metadatabase

The Role of the BioCASE Thesaurus

Term

Term Version Fact

Term Version Term Version Relation

Term inItem

List Item

Term Language

List Version

List List Type

Related ListItem

Hierarchy

Term Type

List Item Fact

Table includes broader term & narrower term relations

Table includes Synonyms, common language forms and preferred status

Related terms in other lists List Item in

List Version

Edit Session

Linked to all tables

Term Word Single word index of terms in Term Table

Associates terms with different versions of lists

Basic logical model

The BioCASE Thesaurus

The BioCASE Thesaurus API

DBMS

DB Manager

Thesaurus Broker

Thesaurus Server

Thesaurus

Client Application

RMI (HTTP tunnel)

JDBC

List Importers

Term

Lists

Thesaurus

Thesaurus Tools

Thesaurus editing tools

Term

Term Version Fact

Term VersionTerm Version Relation

Term Version in Concept

Concept(List Item)

Term Language

Concept Group Version

Concept Group(List)

Concept Domain(List Type)

Related Concept

Hierarchy

Term Type

Concept Fact

Tables include broader term & narrower term relations

Table includes Synonyms, common language forms and preferred status

Related terms in other lists

Concept in Concept Group Version

Concept Code

Word in Term Single word index of terms in Term Table

Associates terms with different versions of lists

Table holds level terms for specific hierarchies

Tables include broader term & narrower term relations

Codes might be used for alphanumeric sorting

A term type maybe linked to one or more hierarchy schemes

Every term has at least one version

Every list has at least one version

Word

A Modified logical model

Principles

Terms fall into various ‘domains’ Within domains there can be many different lists Lists may exist in several versions and some are dynamic (always changing) Lists may be in various languages and may use a wide range of diacritic and other characters There is no single correct list of terms Terms frequently have synonyms, variants and language versions both in and between lists. Terms commonly fall into hierarchies but may also be arranged in more complex ways (networks, ancestor & descendant trees etc.) Terms can be related to terms in other domains

Term

Term_Key

Language_KeyItem_NameAuthority

Concept

Concept_Key

Term_KeyConcept_Group_KeyMeaning_IDVersion_Is_CurrentPreferredInternational_StandardConcept_Rank_Key

Meaning_Relation

Meaning_Relation_KeyRelation_Type_Key

Meaning_ID1Meaning_ID2Comment

Concept_Group

Concept_Group_Key

Domain_Version_KeyItem_NameCommentPriority

Concept_Group_Version

Concept_Group_KeyVersion

Date_FromComment

Domain

Domain_Key

Item_NameSecurity_Group_KeySubject_Area_KeyComment

Domain_Version

Domain_Version_Key

Domain_KeyLanguage_KeyGeographic_Context

Language

Language_Key

Item_NamePriority

Meaning_Fact

Meaning_Fact_Key

DataMeaning_KeyLanguage_KeyConcept_Key

Concept_Status

Concept_Status_Key

Concept_Status_Type_KeyConcept_Key

Concept_Status_Type

Concept_Status_Type_Key

Short_NameLong_NameDescription

Concept_History

Concept_History_Key

Concept_KeyConcept_Group_Version_FromConcept_Group_Version_To

Security_Group

Security_Group_Key

Item_NameSecurity_Bit

Relation_Type

Relation_Type_Key

Item_Name_ForwardItem_Name_ReverseUnidirectionalForward_SynonymyReverse_Synonymy

Concept_Relation

Relation_Type_Key

Concept_Key1Concept_Key2Comment

Concept_Lineage

Concept_KeyParent_Concept_Key

Lineage

Concept_Rank

Concept_Rank_Key

Item_NameInternational_Standard_Italic

Domain Descriptors

Domain_KeyConcept_Key

Subject_Area

Subject_Area_Key

Item_NameComment

The logical model can be expressed in many waysWe may change the physical model as we learn more or for performance reasons. We use an API (Application Programming Interface) to shield users from underlying complexity and change.

‘The BioCASE/Luxembourg Model’

Recorder 6 & Collection Manager

The New Recorder Thesaurus Browser

The Thesaurus Editor