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

Improve UX to configure resource-instance dt nodes #10666

Closed
whatisgalen opened this issue Mar 7, 2024 · 1 comment · Fixed by #10667
Closed

Improve UX to configure resource-instance dt nodes #10666

whatisgalen opened this issue Mar 7, 2024 · 1 comment · Fixed by #10667

Comments

@whatisgalen
Copy link
Member

Currently the UI for a node of datatype resource-instance looks like this:

Screenshot 2024-03-07 at 2 25 27 PM

Given that there's no visual cue to click on it in order to do something, I would assume many users (like myself) are unaware there's a relationship configuration UI hidden behind it. An improvement in UX might look like adding a button or icon in order to visually prompt the user to configure this node.

@chiatt chiatt added this to pipeline Mar 7, 2024
@whatisgalen whatisgalen changed the title Improve UX to condfigure resource-instance dt nodes Improve UX to configure resource-instance dt nodes Mar 7, 2024
whatisgalen added a commit that referenced this issue Mar 8, 2024
@jacobtylerwalls jacobtylerwalls linked a pull request Mar 8, 2024 that will close this issue
6 tasks
@jacobtylerwalls jacobtylerwalls moved this to 👀 In Review in pipeline Mar 8, 2024
whatisgalen added a commit that referenced this issue Apr 17, 2024
…de check for relatedResource.ontologyProperty as proxy for relatable, re #10666
whatisgalen added a commit that referenced this issue May 7, 2024
@jacobtylerwalls
Copy link
Member

Fixed in #10667

@github-project-automation github-project-automation bot moved this from 👀 In Review to ✅ Done in pipeline May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants