Project

General

Profile

feature request #3363

dagger (Totenkreuz) after extinct and fossil taxa

Added by Gabriele Dröge over 6 years ago. Updated 6 months ago.

Status:
In Progress
Priority:
Priority13
Category:
cdm
Target version:
Start date:
03/24/2013
Due date:
% Done:

0%

Severity:
major
Tags:

Description

Use case: recent, extinct and fossil taxa are listed in same classification. Currently used in Corvidae portal.

To distinguish better between extinct and recent taxa in the taxon tree I propose to use a dagger (Totenkreuz) after the name string.

Currently I use a marker ("extinct") for those taxa. It is not essential to display the dagger in the EDITor, since the user here knows his/her taxa, but highly recommended for display at data portal.

Example: http://dev.e-taxonomy.eu/dataportal/corvidae/cdm_dataportal/taxon/e4171f61-a96e-4823-8248-dbb587d8e659

Corvus anitpodium T

(Unfortunately can not type dagger here for encoding reasons, but I hope you know what I mean)


Related issues

Related to PhycoBank - bug #6069: DataPortal for Registry Closed 12/13/2016

History

#1 Updated by Gabriele Dröge over 6 years ago

  • Subject changed from dagger (Totenkreuz) behind extinct and fossil taxa to dagger (Totenkreuz) after extinct and fossil taxa

#2 Updated by Andreas Müller over 6 years ago

  • Assignee changed from Andreas Kohlbecker to Andreas Müller
  • Category changed from dataportal to cdm
  • Target version deleted (cdm_dataportal - Next Major Release)
  • Priority changed from Priority08 to Priority13
  • Severity changed from normal to major

first discuss if this can be handled via an explicit "status" (what is the best name to distiguish it from the taxonomic state like "accepted" or "synonym" - "fossil status" ??) field in the Taxon class.

Therefore I changed to Milestone CDM UML

#3 Updated by Gabriele Dröge over 6 years ago

You have to distinguish between extant and fossil. Extant are all species living in the Holocene (ca. 10.000 years before present until present, "rezente Arten"). Fossil are all species living (and become extinct) before Holocene age.

Fossil species are always extinct. Extant species are sometimes extinct (e.g. Mammoths).

A dagger should be displayed if a species is extinct.

Extinction in present days can be a conservation status (extinct in the wild, still alive in captivity) or a taxon is completely extinct. In the latter case the dagger also should appear.

I searched the web for a suitable term but couldn't find something.

Therefore I suggest the term: "Extinction status"

Status: Fossil

Status: Extant and Extinct

Status: Extant and Still alive OR Extant and not extinct (would be the default value)

Since our diatom people are the only group currently handling data of fossil (specimens) at BGBM I cc Henning as well, maybe he can help here.

#4 Updated by Andreas Müller over 6 years ago

Henning:

Hallo zusammen,

fürchte, ich kann in dem Fall mit meinem Diatomeenblick nicht wirklich weiterhelfen, weil:

1) wir meist mit Schalen = Mikrofossilien arbeiten. Was in den Sedimenten ist, nennen wir meist rezent oder "subfossil", ich gehe nicht in Details.

2) wir nie wissen, ob mikroskopische Arten wirklich "extinct" sind, d.h. in historischer Zeit ausstarben (was ist die Grundlagen? Deutschland, Europa, Welt?). Bei der Roten Liste ist die Kategorie in Deutschland 0= ausgestorben oder verschollen, zumindest im mikroskopischen Bereich keine belastbaren Daten zum Aussterben (wie beim Mammut o.ä.) möglich.

3) in den mit zugänglichen Diatomeenbüchern auf Kreuze verzichtet wird, auch wenn es sich um Taxa handelt, die vor dem Holozän ausgestorben sind.

Im Prinzip sind die Status, wie von Gabi angegeben, sinnvoll. Für höhere Tiere macht das Sinn, für Algen nicht mit einer Holozän-Grenze. Was sagen denn die Bearbeiter höherer Pflanzen dazu? (deshalb die Mail auch an Norbert).

Viele Grüße,

Henning

#5 Updated by Andreas Müller almost 5 years ago

  • Target version changed from CDM UML 3.5 to CDM UML - Next major release

Move all unassigned modelling tickets to next major release

#6 Updated by Andreas Müller about 3 years ago

  • Description updated (diff)
  • Target version changed from CDM UML - Next major release to CDM UML 4.1
  • Keywords set to corvidae

#7 Updated by Andreas Kohlbecker about 3 years ago

  • Related to bug #6069: DataPortal for Registry added

#9 Updated by Andreas Müller about 3 years ago

  • Status changed from New to In Progress
  • Priority changed from Priority13 to Highest

#10 Updated by Andreas Müller about 3 years ago

  • Priority changed from Highest to Priority14

#11 Updated by Andreas Müller about 3 years ago

  • Target version changed from CDM UML 4.1 to CDM UML 4.7

#12 Updated by Andreas Müller over 2 years ago

  • Private changed from Yes to No

#13 Updated by Andreas Müller over 2 years ago

  • Target version changed from CDM UML 4.7 to CDM UML 5.0

#14 Updated by Andreas Müller over 1 year ago

  • Target version changed from CDM UML 5.0 to CDM UML 5.5

#15 Updated by Andreas Müller 11 months ago

  • Priority changed from Priority14 to Priority13

#16 Updated by Andreas Müller 10 months ago

  • Target version changed from CDM UML 5.5 to CDM UML 5.13

#17 Updated by Andreas Kohlbecker 6 months ago

  • Tags changed from corvidae to corvidae, phycobank

#18 Updated by Andreas Kohlbecker 6 months ago

  • Tags changed from corvidae, phycobank to corvidae

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)