Science Environment for Ecological Knowledge
Ecoinformatics site parent site of Partnership for Biodiversity Informatics site parent site of SEEK - Home
Science Environment for Ecological Knowledge









 

 

 



Use Cases

This is version 1. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]


Primary Use Cases

FringedFileFish
User can search for data on the Fringed File Fish. System will resolve the name given by the user and return datasets containing applicable data.

DataIntegration
Integrate data that references taxonomic names and concepts (ecologists, gov. agencies, etc). This is a client application that uses ResolveConcept on each taxonomic object of two or more lists of taxa.

Creators of Taxonomic Information (Systematists or application to PopulateConceptDB)

CreateConcept
Systematist can create concepts in the Concept DB. Irregular or incomplete concepts can also be created.

RelateConcept
Systematist can create/specify relationships in the Concept DB

Secondary use cases

    • TaxonDatabaseWizard : Autonomous database mapping and concept creation tools for micro aggregators.

    • DisplayVisualisationofConcepts : Visualization tools for mapping taxa/taxon concepts

Data Providers (DP)

DataLocationRegistration
DP registers its location with a SEEK registry. This is a precondition, not a Taxonomy WG responsibility.

SEEK Taxon internal functions

PopulateConceptDB
SEEK system consumes information and populates a SEEK reference database from NPs via a common interface. This function populates Tax Concepts and Tax Relationships.

Users

ResolveConcept
User queries with a Tax Object (could be just a name), and receives a ranked, scored list of matching concepts. This could be a way of allowing the user to narrow down his/her request. Various choices are available for the request and return. Particular DPs can be specified. The search algorithm can be specified (narrow or broad search, simple string matching, complex IR algorithms, homonyms returned, etc). Return values can be restricted to concepts from a particular NP Taxonomy tree, to particular fields, to a particular name type (i.e. common names only), etc.

CompareConcepts
This returns a score as a measurement of the equivalance of two concepts. The score is identical to the score returned from ResolveConcept for the same concepts.

GetConceptRelationships
User can query the SEEK system to retrieve the relationships between concepts. Tax Relationships can be parent, child, sibling within a tree, or custom relationships defined by "authorities" or calculated by the system. This could be available after a specific concept is chosen from the results of ResoveConcept.

ResolveEMLToConcept
A user can query the system for datasets related to a given taxonomic object (as simple as a name). With the method ResolveConcept, the system will resolve the user query to a ranked list of concepts. At the same time, the system will query the KNB Metacat server for datasets and resolve the EML from those datasets to taxonomic objects. ResolveConcept will then be called with each taxonomic object returned from the EML to get another ranked list of concepts. The 2 lists of scored concepts will then be compared to determine what datasets best fulfill the user query.

ExtractConcepts
User specifies data sources or datasets. Concepts are extracted from the metadata and returned in XML taxonomic schema format

CompareNames
Service to provide a measure of relative equivalence of two (or more) taxonomic names (RelativeEquivalenceNotes Notes?)


Still unclear

DataProviderSlurpsConceptIDs
a data provider acquires unique global concept IDs from SEEK database, unique ID is used to resolve a specific concept instance, not a unique concept ID,could be a URN (contains 5 elements)



Go to top   More info...   Attach file...
This particular version was published on 06-Jul-2004 14:34:45 PDT by LTER.stekell.