search

cvisionai / tator

Video analytics web platform
https://tator.io
GNU Affero General Public License v3.0
104 stars 34 forks source link

Built-in Attribute Visibility Toggle #752

Open sbatchelder opened 2 years ago

sbatchelder commented 2 years ago

User Attributes on Localisations have a toggle field named Visible that affects whether that attribute is displayed in the Annotation and Analytics and Filter views. Consider creating a user-accessible Visible toggle field for built-in attributes.

The User Attributes are found under Project Settings -> Localisations -> MyLocalisation on the right-hand side-panel/frame. A seconds "Built-in Attributes" frame could be situated below the User Attributes one. These would not be editable, but you could set one or more display properties for each one like for User Localisations.

This issue is related to issue cvisionai/tator#746 where my users require _modified_by built-in attribute filter access. We have to wait for a version-update-cycle to get access to it. The fulfillment of this enhancement would add a lot of flexibility for users to adjust their interface to best work with their particular workflows.

jrtcppv commented 2 years ago

We will work on this one, will be a post 0.2.19 update.

ermbutler commented 1 year ago

This feels related to personalization which is mentioned in #854 ---- I like the suggestion that "built in" attributes are shown by type, while in 854 it was considered project-level. I like the idea of a second box to control modified by visibility, but would it be for all attributes + built in? And would affect what is viewable in right side panel AND on cards, or it could be two toggles?

For built-ins, we could add an attribute box on the Project page that is all the available built ins and modal has 2 value "show on cards", and "show in side panel" --->

Or potentially... for customizability, do some sort of mapping of built ins --> So if the user really wants modified by to be prominent for localization type, they click to "+ Add attribute" and they just assign a built in value. For example "Reviewed By" -> Maps to modified by, and is now prominent for localization-type "box"... I feel like it could be pontentially pretty cool to have a calculated field in this way like Attribute C and distance between, and it is B-A.... Or time since upload is "today" - "created_date"

Part two - updating what's in the filterable list is interesting there are other requests to show all available here, and I sort of think that should be its own issue. All custom attributes are shown, so potentially if the user creates a new attribute mapped to a built in that would automatically add it.

sbatchelder commented 1 year ago

mapping of built-ins as custom/calculated attributes sounds promising. Being able to sort and filter by eg: "size" (width*height built in attributes) is something my users would immediately make use of. Direct mapping would be useful too, eg: "_modified_by".