Project

General

Profile

task #8130

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

Added by Patrick Plitzner 27 days ago. Updated 3 days ago.

Status:
Feedback
Priority:
Highest
Category:
taxeditor
Target version:
Start date:
02/22/2019
Due date:
% Done:

0%

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.

History

#1 Updated by Andreas Müller 27 days ago

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

#2 Updated by Patrick Plitzner 15 days ago

  • Status changed from New to In Progress

#3 Updated by Patrick Plitzner 15 days ago

  • Description updated (diff)

#4 Updated by Patrick Plitzner 15 days 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?

#5 Updated by Andreas Müller 15 days 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

#6 Updated by Andreas Müller 15 days ago

  • Description updated (diff)

#7 Updated by Andreas Müller 15 days 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.

#8 Updated by Katja Luther 10 days 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.

#9 Updated by Katja Luther 3 days ago

  • Assignee changed from Katja Luther to Patrick Plitzner

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)