Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standard Properties - Promote the use of shared properties so we can make richer UI for custom types. #1005

Closed
Polleps opened this issue Oct 29, 2024 · 2 comments · Fixed by #1017
Labels

Comments

@Polleps
Copy link
Member

Polleps commented Oct 29, 2024

We expect users to use the name and description properties in their own classes so we can show them in the UI. But except for the docs we don't actually tell them they should. How do we promote the use of these properties.

Option 1

Straight up tell them somewhere in the app.
Not very nice UX but easy

Option 2

Add them to classes by default. When making a new class in the ontology editor, add them to the list of recommended or required by default. (This makes more sense for name but not really for description.)
It also doesn't really tell the user why they should actually do this.

Option 3

Label them as something like 'Standard Properties' in the resource selector UI.
When the user has not typed anything in the searchbox we show a list of resources of that type. We could sort these standard properties to the top and maybe even give them their own category separated with a divider.

@joepio
Copy link
Member

joepio commented Oct 30, 2024

Something like option 3 seems best IMO.

@joepio
Copy link
Member

joepio commented Nov 11, 2024

Don't show AtomicData.dev properties, except for a few recommended hardcoded ones (name, description)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants