|
|||
|
Use Case: Select Naming System
Actors
DescriptionWhen querying SEEK the user may prefer to have results returned acording to a particular naming scheme offered by the provider, e.g. common names rather than full scientific name. The SEEK system must allow the user to be able to specify this and ensure providers can respond to the request accordingly.
Flow of Events
Pre-conditions
Basic Flow
Post-conditionsNone
Alternative Flows
Further Details
Non-functional RequirementsNone
IssuesDoes SEEK have a default naming scheme for returning all results? - I suggest it does. What different naming schemes will we allow? Do these have to be pre-defined or can each data provider supply their own naming schemes? - suggest pre-defined (but extensible) not at discretion of provider. What happens if the result list does not have a name for a particular concept under the scheme chosen by the user?- suggest default naming scheme is used - implication that each data provider must have a name for each concept in the default naming scheme. or user must be notified that it is a partial result.
History
|
This material is based upon work supported by the National Science Foundation under award 0225676. Any opinions, findings and conclusions or recomendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation (NSF). Copyright 2004 Partnership for Biodiversity Informatics, University of New Mexico, The Regents of the University of California, and University of Kansas |