Project

General

Profile

Actions

Feature #989

closed

Improved display of value types in forms

Added by Stefan Eichert about 5 years ago. Updated over 3 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
UI
Target version:
-
Start date:
2019-02-07
Estimated time:

Description

When entering for example an entry for finds, the value types are listed one after the other in one column in the UI. It would be better if they were selectable like other types in a hierarchical manner.
Tested on chrome


Files

screenshot.jpg (200 KB) screenshot.jpg Stefan Eichert, 2019-02-07 17:09

Related issues 1 (0 open1 closed)

Is duplicate of OpenAtlas - Feature #1285: Improved value types displayClosedAndreas Olschnögger2020-11-23Actions
Actions #1

Updated by Alexander Watzinger about 5 years ago

  • Tracker changed from Bug to Feature
  • Subject changed from Value Types not ordered hierarchically to Improved display of value types in forms
  • Status changed from New to Acknowledged
  • Target version set to Wishlist

I assume the ticket is more about the display (clearer indentation and/or opening/closing nodes with jsTree) rather than the order, which is correct (ordered hierarchical and then alphabetically on same level), so I changed this ticket to an acknowledged feature and adapted the subject. Please comment if I misunderstood the issue.

We already talked about the display in forms a few month ago when the value types were implemented and decided together that it is good enough for now.

However, I fully understand the desire for a better display solution. Deciding how to do this and implenting it is not a trival task.

Two approaches I can think of are:

  • Identation for lower levels. This would make the viewing/editing easier but the list can still be a long one
  • Using jsTree like in type overview. But we would have to think about how to present it with open/closed nodes for already entered data (so it doesn't get overlooked). Also using jsTree could be problematic itself (e.g. see reported bug #987) and integrating it in forms with dynamic generated types could get quite tricky.

Maybe we can take a look at it when redesigning the frontend.

Actions #2

Updated by Alexander Watzinger over 3 years ago

  • Is duplicate of Feature #1285: Improved value types display added
Actions #3

Updated by Alexander Watzinger over 3 years ago

  • Status changed from Acknowledged to Duplicate
  • Target version deleted (Wishlist)
Actions

Also available in: Atom PDF