Project

General

Profile

feature request #3746

Implement time period scope for description elements in TaxEditor

Added by Andreas Müller over 5 years ago. Updated 4 months ago.

Status:
Closed
Priority:
Highest
Assignee:
Category:
taxeditor
Target version:
Start date:
10/30/2013
Due date:
% Done:

100%

Severity:
normal

Description

also modifiers and modifyingText is still missing there. The later should be available only for NON-TextData. => handled in #3836

see #3312, #3747

duplicated by #3615

picture672-1.png View (2.2 KB) Andreas Müller, 04/30/2018 04:50 PM


Related issues

Related to Edit - feature request #3747: Check if time period is handled correctly for description elements in data portals Closed 12/18/2015
Related to Edit - feature request #3312: Add time period scope to DescriptionElementBase Closed 02/19/2013 09/27/2013
Related to Edit - feature request #3836: Implement modifiers and modifying text for Description Elements in TaxEditor Resolved
Related to Edit - feature request #3616: Show DescriptionElementBase.timeperiod in Dataportals Closed 06/18/2015
Copied to Edit - feature request #7394: parsing behaviour and layout of the period part issues New 05/02/2018

Associated revisions

Revision e8a69e3a (diff)
Added by Katja Luther about 1 year ago

fix #3746: move time period down in details view

Revision 8f3ebbd4 (diff)
Added by Katja Luther about 1 year ago

ref #3746: fix not saving period data in details view

History

#1 Updated by Cherian Mathew over 5 years ago

  • Target version deleted (TaxEditor CDM 3.3)

#2 Updated by Andreas Kohlbecker about 5 years ago

  • Target version deleted ()

no release 3.3.1 of the taxeditor so I am moving all tickets to the next milestone 3.3.2

#3 Updated by Cherian Mathew over 4 years ago

  • Target version deleted (TaxEditor RELEASE 3.4.0)

Moving tickets to 3.4.1 milestone

#4 Updated by Cherian Mathew over 4 years ago

  • Target version deleted ()

Moving tickets that were auto assigned to me to the unassigned milestone

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

  • Description updated (diff)
  • Assignee changed from Cherian Mathew to Katja Luther
  • Target version changed from Unassigned CDM tickets to Release 4.13

We may now need DescriptionElementBase timeperiods for flowering time features.

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

  • Related to feature request #3747: Check if time period is handled correctly for description elements in data portals added

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

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

RH:

nach jahrelanger Pause wollen wir für Zypern mal wieder ein Datenset erfassen und es im Portal darstellen, die Blühzeiten der Arten.

Im Prinzip gibt es zwei Herangehensweisen. Entweder wir machen es „primitiv“ und füllen irgendwelche Freitextfelder aus, etwa mit „January-May(June)“ oder ähnlich. Oder wir erfassen die Monate strukturiert in Tabellenform und zeigen das wie auch immer geartet graphisch an (habe mal eine primitive Farbleiste angehängt mit Haupt- und Nebenzeiten dunkel/hell). Da gibt es sicherlich noch elegantere Lösungen.

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

  • Private changed from Yes to No

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

  • Target version changed from Release 4.13 to Release 4.14

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

  • Target version changed from Release 4.14 to Release 5.0

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

  • Priority changed from New to Highest

This is needed for cyprus therefore I put it to highest

#14 Updated by Katja Luther over 1 year ago

The time period should be displayed for all kind of features?
I think for some it is not necessary, for example common names... or categorical data.
maybe we also should add this to the Feature class.

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

Every information may have a time scope. A common name e.g. may have been used only in a certain century. And categorical data is only a way to handle data in a more structured way then pure TextData, the data itself may be true anyway only for a certain time.

Of course we could think about something like supportsTimeScope in Feature class but I don't think this is necessary. Maybe better we add a CdmPreference "timeScopeSupporting features" or so, so each project can decide for which features it wants to allow adding time scopes.

#16 Updated by Katja Luther about 1 year ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 50

#17 Updated by Katja Luther about 1 year ago

  • Assignee changed from Katja Luther to Andreas Müller
  • % Done changed from 50 to 0

this should be fixed now. the time period element is now at the end of the description element details view

#18 Updated by Andreas Müller about 1 year ago

Some minor issues:

  1. Relabel to "Time scope"
  2. Leave a bit more space to the element above
  3. Keep the element collapsed at start time. Only if someone really wants to edit the time scope it should be expanded.

#19 Updated by Andreas Müller about 1 year ago

  • Status changed from Resolved to Feedback
  • Assignee changed from Andreas Müller to Katja Luther

Some general issue about the time period selection.

The parsing behavior is somewhat unclear. E.g.

  • Enter date 1.1.2006 into "Parse" Textbox => according date shows up in label and in atomized Start textboxes
  • Remove text from "Parse" => label disappears, however Start textboxes are still filled
  • Change value in Start-Year to 2005 => 2005 appears in label

Looks like the the Start textboxes are not emptied correctly while the values are internally deleted already.

Please decide if this is related to the ticket or an issue for a new ticket.

#20 Updated by Andreas Müller about 1 year ago

Another minor and general issue:

The labels "Start" and "End" are not on the same hight as the according labels for "Year", "Month" and "Day". See attachment.

#21 Updated by Andreas Müller about 1 year ago

A critical issue: the value is NOT being saved or not being reloaded when reopening the fact !!

#22 Updated by Andreas Müller about 1 year ago

  • % Done changed from 0 to 30

#23 Updated by Katja Luther about 1 year ago

  • Status changed from Feedback to Resolved
  • Assignee changed from Katja Luther to Andreas Müller

The saving is fixed now.

The other issues are related to the general period part so I create a new ticket for this. (#7394)

#24 Updated by Andreas Müller about 1 year ago

#25 Updated by Andreas Müller about 1 year ago

  • Status changed from Resolved to Feedback
  • Assignee changed from Andreas Müller to Katja Luther
  • % Done changed from 30 to 40

Andreas Müller wrote:

Some minor issues:

  1. Relabel to "Time scope"
  2. Leave a bit more space to the element above
  3. Keep the element collapsed at start time. Only if someone really wants to edit the time scope it should be expanded.

The first 2 issues still seem to be open.

If possible please also reduce the empty space below label "Time period"("Time scope") by moving the atomized data part more to the left. Otherwise it easily happens that the data textboxes are wrapped.

The save seems to work now.

#26 Updated by Andreas Müller about 1 year ago

  • Related to feature request #3836: Implement modifiers and modifying text for Description Elements in TaxEditor added

#27 Updated by Katja Luther about 1 year ago

  • Status changed from Feedback to Closed
  • % Done changed from 40 to 100

only the space between the time period element and the element above is still open, so I close this ticket.

#28 Updated by Andreas Kohlbecker 4 months ago

The output in the taxeditor can very ugly depending on the partial fields being used:

  • Timescope: start month: 05 - end month 06
  • representation: 5.xxxx-6.xxxx

Is this wanted?

#29 Updated by Andreas Kohlbecker 4 months ago

#30 Updated by Andreas Müller 4 months ago

Andreas Kohlbecker wrote:

The output in the taxeditor can very ugly depending on the partial fields being used:

  • Timescope: start month: 05 - end month 06
  • representation: 5.xxxx-6.xxxx

Is this wanted?

Not wanted but we havn't discussed yet best formatting for Partial with missing non-beginning parts. There are multiple possibilities.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)