My favorites | Sign in
Project Home Downloads Wiki Issues Source
Search
for
CommonNamesCataloger  
Common Names for Higher Taxa project description
Updated Sep 9, 2009 by dprem...@gmail.com
This page is under construction and subject to significant revision.

Common Names for Higher Taxa web application

Introduction

A web application focused on developing vernacular name alternatives for higher taxonomic 'backbones' used in navigating biodiversity datasets. Providing known or descriptive vernacular name alternatives for cryptic higher taxonomic groups (family and above) provides valuable context for navigating large data stores. It provides the basis for displays that substitute or complement a higher taxonomic name with an vernacular alternative. Additionally the application will include interfaces to Flickr to access representative images for the higher taxonomic groups to also provide contextual display when navigating taxonomic data.

The application will serve as both a Checklist Bank client, accessing higher taxonomic hierarchies and indexed vernacular names data, as well as a publishing tool with a local data repository for users to compile and publish vernacular names indices.

In 2006 GBIF initiated a project with uBio that resulted in a preliminary application. Initial Terms of Reference describe that project. This project extends the work.

Requirements

Internationalised – The application should support the use of non-English interfaces. A clean and intuitive user interface will minimize the need for text-rich prompts and instructions. Where these are required, there should be a simple mechanism to configure for different languages (text based configuration files for example such as gettext()).

Authentication – The application will require user authentication to enable different editors to make track-able contributions to the dataset. GBIF Node managers and representatives from participating organizations are likely candidates for such user accounts. We would like to utilize an existing sign-on mechanism if possible (OpenID, or a GBIF-oriented signon system)

GBIF policy on user authentication is not yet in place.

Intutive and flexible interface – The application should provide different and vernacular-oriented interface options for the editor, taking advantage of dynamic and graphical UI where appropriate.

Images

Add the capacity to reference and score images that best exemplify the taxon. More details required from Javier and Markus.

  • Provide human-computational-interface for ‘scoring’ images
  • Cache the image and permissions
  • Build multiple-size thumbnails (requirements required)

Vernacular Names Data

Editors provide vernacular names alternatives in a specified language for higher taxa selected from existing lists imported from Checklist Bank. Additional regional usage (dwc:country or dwc:locality) may be provided. The resultant data file tied to an editor will be an unordered list of higher taxa tied to the source concept that was referenced. Higher taxonomic structure in the export format is redundant and is implied through the link to the source.

Standardised data I/O - DwC Archive/GNA format

Description

The web application will present an authenticated user with a default higher classification, the GBIF NUB taxonomy. Alternative taxonomic hierarchies could also be accessed. Higher taxonomy (Family and above) is the target for the tool although many sources will contain sub-familial taxa. The higher taxon focus means that certain vernacular name properties, such as organismPart, lifeStage, Sex, and locality information will not be supported in the capture of vernacular data elements. Lower taxa may be catalogued with the tool but with a limited profile.

The web application would utilise a local data store and web service calls to Checklist Bank.


Sign in to add a comment
Powered by Google Project Hosting