Project

General

Profile

Actions
Copy link

feature request #4682

open

[DISCUSS] Do we need an explanation/reason field in RelationBase

Added by Andreas Müller about 8 years ago. Updated about 1 year ago.

Status:
New
Priority:
Highest
Assignee:
Andreas Müller
Category:
cdm
Target version:
CDM UML - Next major release
Start date:
Due date:
% Done:

10%

Estimated time:
3:00 h
Severity:
normal
Tags:
redlist

Description

Some relations such as TaxonRelations are opinion. We may want to have a field to verbally explain why an author thinks that this relation exists/is correct.

Needed e.g. by Moose #4670

Currently we use Annotations for this. But this may not be enough.

It needs to be discussed which RelationBase classes do need such a field.

see also #4681

Actions
Copy link
 #1

Updated by Andreas Müller about 8 years ago

  • Subject changed from [DISCUSS] Do we need an explanation field in RelationBase to [DISCUSS] Do we need an explanation/reason field in RelationBase
Actions
Copy link
 #2

Updated by Andreas Müller almost 8 years ago

  • Target version deleted (CDM UML 3.6)
Actions
Copy link
 #3

Updated by Andreas Müller about 7 years ago

  • Target version changed from CDM UML 4.0 to CDM UML 4.1
Actions
Copy link
 #4

Updated by Andreas Müller almost 7 years ago

  • Priority changed from New to Priority14
Actions
Copy link
 #5

Updated by Andreas Kohlbecker over 6 years ago

  • Description updated (diff)
Actions
Copy link
 #6

Updated by Andreas Kohlbecker over 6 years ago

  • Target version changed from CDM UML 4.1 to CDM UML 4.7
Actions
Copy link
 #7

Updated by Andreas Müller almost 6 years ago

  • Target version changed from CDM UML 4.7 to CDM UML 5.0
Actions
Copy link
 #8

Updated by Andreas Müller about 5 years ago

  • Target version changed from CDM UML 5.0 to CDM UML 5.5
Actions
Copy link
 #9

Updated by Andreas Müller over 4 years ago

  • Priority changed from Priority14 to Priority13
Actions
Copy link
 #10

Updated by Andreas Müller about 4 years ago

  • Target version changed from CDM UML 5.5 to CDM UML 5.15
Actions
Copy link
 #11

Updated by Andreas Müller almost 3 years ago

  • Target version changed from CDM UML 5.15 to CDM UML 5.39
Actions
Copy link
 #13

Updated by Andreas Müller about 1 year ago

  • Due date set to 03/29/2022
  • Priority changed from Priority13 to Highest
  • Target version changed from CDM UML 5.39 to Release 5.31
  • Start date set to 03/24/2022
  • Estimated time set to 3:00 h
  • Parent task set to #2934
  • Severity changed from normal to major

Dicussion/implementation should be done in 5.31 to have it available for RL import in case we implement it.

Actions
Copy link
 #14

Updated by Andreas Müller about 1 year ago

  • Private changed from Yes to No
Actions
Copy link
 #15

Updated by Andreas Müller about 1 year ago

  • Tags set to redlist
Actions
Copy link
 #16

Updated by Andreas Müller about 1 year ago

  • Description updated (diff)
Actions
Copy link
 #18

Updated by Andreas Müller about 1 year ago

  • Target version changed from Release 5.31 to CDM UML - Next major release
  • % Done changed from 0 to 10
  • Parent task deleted (#2934)
  • Severity changed from major to normal

We will not implement this for "Moose" therefore remove it from parent and link it instead. Move to UML milestone

Actions
Copy link
 #19

Updated by Andreas Müller about 1 year ago

  • Due date deleted (03/29/2022)
  • Start date deleted (03/24/2022)
Actions
Copy link

Also available in: Atom PDF