Project

General

Profile

Actions

feature request #9287

closed

Show term details in details view of term tree editor

Added by Katja Luther about 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
New
Assignee:
Category:
taxeditor
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Severity:
normal

Description

From ticket #8774:

Can we show the details of a term anyway even if it is not editable in the term tree editor. This is because the pure label is often not enough to decide if one took the right term.
If not all information is easily available at least the most important should be shown.

But ofcourse it should be disabled for editing. (but Maybe in future when vocabularies will also use term trees for hierarchy editing might be a requested feature, just in case this is important to know for implementation).


Related issues

Related to EDIT - bug #8774: Reimplement term tree editors to implement the general save strategyClosedKatja Luther

Actions
Related to EDIT - feature request #9337: Open issues for reimplementation of termtree editorsClosedKatja Luther

Actions
Copied to EDIT - bug #9688: Make disabled fields copyableClosedKatja Luther

Actions
Actions #1

Updated by Katja Luther about 2 years ago

  • Related to bug #8774: Reimplement term tree editors to implement the general save strategy added
Actions #2

Updated by Andreas Müller about 2 years ago

  • Target version changed from Unassigned CDM tickets to Release 5.18

As this is related to #8774 I move it to current milestone as we should implement it soon (might also be an interesting feature for the "integrated taxonomy" course.

Actions #3

Updated by Andreas Müller about 2 years ago

Maybe we do not need to load the data with the initial DTO but asynchronously when ever it is needed. Just in case loading takes to long for term types with a large number of term nodes.

Actions #4

Updated by Andreas Müller about 2 years ago

Actions #5

Updated by Katja Luther almost 2 years ago

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

Updated by Andreas Müller almost 2 years ago

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

Updated by Andreas Müller over 1 year ago

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

Updated by Andreas Müller over 1 year ago

  • Subject changed from Show term details in details view of term editor to Show term details in details view of term tree editor
Actions #9

Updated by Katja Luther over 1 year ago

  • Target version changed from Release 5.22 to Release 5.38
Actions #10

Updated by Katja Luther over 1 year ago

  • Status changed from New to Resolved
  • Assignee changed from Katja Luther to Andreas Müller
  • Target version changed from Release 5.38 to Release 5.25

this should be fixed. Please review.

Actions #11

Updated by Andreas Müller over 1 year ago

  • Tracker changed from bug to feature request
  • Status changed from Resolved to Feedback
  • Assignee changed from Andreas Müller to Katja Luther
  • % Done changed from 0 to 50

The buttons for multi-language editing are still enabled. So it is possble to remove a description for a given language or to open the the translation editor.

Note: Als the Open URI button is enabled even if no URI is given. It should be enabled only if a value exists (in general, not only in context of this ticket).

Actions #12

Updated by Katja Luther over 1 year ago

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

Andreas Müller wrote:

The buttons for multi-language editing are still enabled. So it is possble to remove a description for a given language or to open the the translation editor.

Note: Als the Open URI button is enabled even if no URI is given. It should be enabled only if a value exists (in general, not only in context of this ticket).

This is fixed now, please review.

The URI issue is fixed as well.

Actions #13

Updated by Andreas Müller over 1 year ago

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

Works as expected now and we can close the ticket.

There is only one final issue which is valid for all disabled fields. Is it possible to generally make disabled fields copyable? Currently they only show the text but it is not possble to copy it. At some places this is already implemented. We probably should move this issue to a new ticket.

Actions #14

Updated by Andreas Müller over 1 year ago

See also #7309#note-19 which is maybe related to this ticket.

Actions #15

Updated by Katja Luther over 1 year ago

  • Assignee changed from Katja Luther to Andreas Müller

Andreas Müller wrote:

Works as expected now and we can close the ticket.

There is only one final issue which is valid for all disabled fields. Is it possible to generally make disabled fields copyable? Currently they only show the text but it is not possble to copy it. At some places this is already implemented. We probably should move this issue to a new ticket.

It is possible and I implemented for toggleable and text fields, but now it is possible to enter something, but the changes disappear immediately.

Please have a look whether this is ok.

Actions #16

Updated by Andreas Müller over 1 year ago

  • Assignee changed from Andreas Müller to Katja Luther

It works as expected for the fields in the term tree details view (which are not toggleable).

For toggleable they still set the dirty flag (tested on Person details view with bulk editor). This is unwanted.

I do not yet fully understand why it is not possible to use the same technique as for ordinary text fields in toggleable fields.

Actions #17

Updated by Andreas Müller over 1 year ago

  • Copied to bug #9688: Make disabled fields copyable added
Actions #18

Updated by Katja Luther over 1 year ago

Andreas Müller wrote:

It works as expected for the fields in the term tree details view (which are not toggleable).

For toggleable they still set the dirty flag (tested on Person details view with bulk editor). This is unwanted.

I do not yet fully understand why it is not possible to use the same technique as for ordinary text fields in toggleable fields.

The same technique is used for text fields and toggleable text fields but maybe I need to have a look on the event handling of the toggleable text field.

Actions #19

Updated by Andreas Müller over 1 year ago

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

As there is a followup ticket for the general "copyable" issue we can close this ticket and move discussion on "copyable" to #9688

Actions

Also available in: Atom PDF