The requirements for a TaxonomicEditor based on the EclipseRichClient platform.

Also see PlatformUseCases for an outline of different projects using this editor.

Non-functional¶

Functional¶

_Add “view / taxon / etc.”, “Login” use cases?

These are currently features, i.e. not actor-centered

NEXT STEP: describe steps in high level use cases, try to incorporate all use cases below

_

High level (too UI-centered?)¶

• Add / edit name

• Add / remove taxon / name relation

• Add / edit / remove taxon / name fact

• Search name

• Add taxon to tree

• Move taxon in tree

• Remove taxon from tree

• Navigate tree

Author¶

• Create author

• Change author

• Delete author (Board only)

• Is distinction between structured and free author team creation too much detail at this point? And will these be the same with autocomplete, as-you-go parsing?

• Create author team (i.e. 1+ authors) by concatenating authors

• Create author team as string

• Change author team by editing list of authors

• Change author team string

• Delete author team (Board only)

• Associate an author team with a name

• Change a name’s author team

• Delete a name’s author team

Reference¶

• Create bibliographic reference (see remarks on author team re: autocomplete, parsing)

• Create nomenclatural reference (see remarks on author team re: autocomplete, parsing)

• Edit a bibliographic reference (Board only)

• Edit a nomenclatural reference (Board only)

• Delete a bibliographic reference (Board only)

• Delete a nomenclatural reference (Board only)

• Associate bibliographic reference with a taxonomic entity

• Associate nomenclatural reference with a name

• Change a taxonomic entity’s bibliographic reference

• Delete a taxonomic entity’s bibliographic reference

• Change a name’s nomenclatural reference

• Delete a name’s nomenclatural reference

Name¶

Taxon¶

Reference¶

Type¶

Distribution¶

Facts¶

Structured Descriptions¶

initially not covered!