EDIT

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

Following is a summary of the functionality of the existing Berlin Model Web Editor.

_Add “view [[name|/ 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

== Concept relation use cases

* Create a concept relation between taxa

* Delete a concept relation

== Distribution use cases

* Distribution …

== Fact use cases

* Create fact 

* Change fact

* Delete fact

Will these two ever take place outside the context of moving a taxon?

* Move fact to another taxon

* Move all of a taxon’s facts

## Status / taxonomic inclusion

_Or should this all be under “taxon”?_

* Create “included in” relation

* Remove “included in” relation 

_The following are the only complex use cases, i.e. multi-step, multi-integrity

Mapping them out in detail will show exactly what the UI needs to do_

* Move a taxon to another taxonomic tree

* De-activate a taxon, moving its taxonomic data to another taxon

* Move synonym to another taxon

* Move all of a taxon’s synonyms to another taxon

* Move fact to another taxon

* Move all of a taxon’s facts to another taxon

* Remove a taxon from its taxonomic tree

* Set synonyms belonging to an inactive taxon to “unresolved” (?)

* Deactivate taxon (confirm w/ Eckhard that this is a relatively frequent occurrence?)

* Reactivate taxon

_How will these two appear in the UI?_

* Turn a synonym into an accepted name

* Turn an accepted name into a synonym

## Name

## Taxon

## Reference

## Type

## Distribution

## Facts

## Structured Descriptions

initially not covered!