Project

General

Profile

feature request #9619

Model changes for taxon concept strategy

Added by Andreas Müller 6 months ago. Updated 5 months ago.

Status:
Closed
Priority:
New
Category:
cdm
Target version:
Start date:
05/10/2021
Due date:
% Done:

100%

Severity:
normal
Tags:

Description

In the taxonId meeting 2021-03-21 we agreed on the following changes

Class: Taxon
Attribute: conceptId
Type: String
Reason: s. email discussion, there are usecases where nameUsageIds have to stay stable when conceptsIds change and the other way round therefore a separate identifier is needed though we use the same class for handling concepts and nameUsages (instances of class Taxon with all available data attached)

Class: Taxon
Attribute: isConcept
Type: boolean
Reason: workflow control available explicitly for concepts; maybe the existence of the conceptId is enough

Class: Taxon
Attribute: isNameUsage
Type: boolean
Reason: workflow control available explicitly for name usages; the existance of the taxon.id (= nameUsage.id) is not enough as Taxon records used only as condepts will always hava a Taxon.id due to technical reasons

Class: Taxon
Attribute: conceptDefinition
Type: EnumSet
Description: an enumset defining all data that define the concept (e.g. homotypic groups, descrptive data, secundum, ...); this may also include the rules when the concept is changing (e.g. automatically when a homotypic group is added, when HG is added but only after user feedbac, automatically if HG is moved from another concept to this concept or the other way round, ...). In future rules maybe become a separate attribute depending on the degree of detailedness needed

Class: Taxon
Attribute: isPersistent
Type: boolean
Reason: defines if a concept will/should be available for long time; necessary e.g. for temporary concepts (e.g. Kew concepts in E+M usecase)

Class: Taxon
Attribute: supportsProvenance
Type: boolean
Reason: defines if a concept supports provenance (guaranteed links to successor concepts when ever the concept is not the current concept anymore)

Class: Taxon
Attribute: isCurrentConcept
Type: boolean
Reason: defines if the concept is the current concept in it's classification (maybe also computable by list of successors isEmpty or by position in classification)

Class: Taxon
Attribute: currentConceptPeriod
Type: TimePeriod
Reason: time period when this concept was current (only start value if concept is still current)

Associated revisions

Revision 2368acec (diff)
Added by Andreas Müller 6 months ago

ref #9619 add conceptId, conceptDefinitions, conceptStatus, taxonTypes and currentConceptPeriod to Taxon

History

#1 Updated by Andreas Müller 6 months ago

  • Status changed from New to Resolved

#2 Updated by Andreas Müller 6 months ago

  • Tags set to taxonID

#3 Updated by Andreas Müller 6 months ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100

Tested on test server. The new columns appear as expected.

#4 Updated by Andreas Müller 5 months ago

  • Target version changed from Release 5.25 to Release 5.23

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)