Project

General

Profile

Actions

task #8130

open

Check if related feature data is cleared when supported facts type is changed

Added by Patrick Plitzner about 5 years ago. Updated almost 3 years ago.

Status:
In Progress
Priority:
Highest
Assignee:
Category:
taxeditor
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Severity:
normal

Description

For example:

  1. Set a feature to support quantitative data and assign recommended measurement units, statistical measures and recommended modifiers.
  2. Change the feature to not support quantitative data
  3. Check if the recommended measurement units, statistical measures and recommended modifiers are removed from the term.

Update:

It is not removed when doing this.

Actions #1

Updated by Andreas Müller about 5 years ago

We may want to implement hard or soft validation for this. Maybe also an update script to remove existing data (if it exists).

Actions #2

Updated by Patrick Plitzner about 5 years ago

  • Status changed from New to In Progress
Actions #3

Updated by Patrick Plitzner about 5 years ago

  • Description updated (diff)
Actions #4

Updated by Patrick Plitzner about 5 years ago

  • Status changed from In Progress to Feedback
  • Assignee changed from Patrick Plitzner to Andreas Müller

Andreas Müller wrote:

We may want to implement hard or soft validation for this. Maybe also an update script to remove existing data (if it exists).

@Andreas: Should we convert this into a cdm ticket? This would best be done on model level, wouldn't it?

Actions #5

Updated by Andreas Müller about 5 years ago

  • Subject changed from Check if related term data is cleared when changing term type to Check if related feature data is cleared when supported facts type is changed
Actions #6

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #7

Updated by Andreas Müller about 5 years ago

  • Assignee changed from Andreas Müller to Katja Luther

Katja, could you please check how we do these "model validations" in terms of e.g. nomenclatural code changes in TaxonName. I think there is also at least 1 more place where we do this. We should define a common strategy how to handle these in UIs.
Additionally we should define (soft?) validations to avoid persisting such unwanted states.

Actions #8

Updated by Katja Luther about 5 years ago

For nomenclatural code there is a method checkForDeletableParts() where the deletable parts set to null.

But for ranks the parts are kept but not shown any more. We should discuss if this is wanted behaviour.

Actions #9

Updated by Katja Luther about 5 years ago

  • Assignee changed from Katja Luther to Patrick Plitzner
Actions #10

Updated by Patrick Plitzner about 5 years ago

  • Target version changed from Release 5.6 to Release 5.7

moved to 5.7

Actions #11

Updated by Patrick Plitzner almost 5 years ago

  • Target version changed from Release 5.7 to Release 5.8
Actions #12

Updated by Patrick Plitzner over 4 years ago

  • Target version changed from Release 5.8 to Release 5.10

Move to next milestone for remaining discussion

Actions #13

Updated by Patrick Plitzner over 4 years ago

  • Target version changed from Release 5.10 to Release 5.11

Move to next milestone for remaining discussion

Actions #14

Updated by Patrick Plitzner over 4 years ago

  • Target version changed from Release 5.11 to Release 5.12

Move to next milestone for remaining discussion

Actions #15

Updated by Andreas Müller over 4 years ago

  • Assignee changed from Patrick Plitzner to Katja Luther
Actions #16

Updated by Andreas Müller about 4 years ago

  • Target version changed from Release 5.12 to Release 5.13

I guess this is not yet fixed.

Actions #17

Updated by Andreas Müller about 4 years ago

can you please check and set the correct status for the ticket?

Actions #18

Updated by Katja Luther about 4 years ago

  • Status changed from Feedback to In Progress

I think the status should be In process and we should discuss how it should be handled in general because it should be handled the same way everywhere.

Actions #19

Updated by Katja Luther about 4 years ago

  • Target version changed from Release 5.13 to Release 5.14
Actions #20

Updated by Katja Luther about 4 years ago

  • Target version changed from Release 5.14 to Release 5.15
Actions #21

Updated by Katja Luther almost 4 years ago

  • Target version changed from Release 5.15 to Release 5.18

we need to decide how to handle this.

Actions #22

Updated by Katja Luther over 3 years ago

  • Target version changed from Release 5.18 to Release 5.19
Actions #23

Updated by Andreas Müller about 3 years ago

  • Target version changed from Release 5.19 to Release 5.21
Actions #24

Updated by Katja Luther about 3 years ago

  • Target version changed from Release 5.21 to Release 5.22
Actions #25

Updated by Katja Luther almost 3 years ago

  • Target version changed from Release 5.22 to Release 5.46
Actions

Also available in: Atom PDF