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

Search should indicate if the result is from a removed object #5407

Closed
ozyx opened this issue Jun 28, 2022 · 7 comments
Closed

Search should indicate if the result is from a removed object #5407

ozyx opened this issue Jun 28, 2022 · 7 comments

Comments

@ozyx
Copy link
Member

ozyx commented Jun 28, 2022

The object and tag search can bring up results from objects which have been removed. This is fine, but there is currently no visual indication of this. This can potentially lead to some confusing search results.

This is most apparent with tags:
image

...but can also be confusing with objects:
image

Especially if they have the same name:
image

@charlesh88 charlesh88 self-assigned this Jun 29, 2022
@charlesh88
Copy link
Contributor

charlesh88 commented Jun 29, 2022

This is a good candidate as we move forward on the search capability. By default, we should not include removed objects in the results, with an option in an Advanced search UI to enable searching for removed objects. Result items should also include a designator when an object has been removed. If we do this, removed objects should also be allowed to be restored via a UI gesture.

In the short-term, I'd argue we should not include removed objects at all in order to avoid confusion as noted, but I'm open to arguments to the contrary.

@scottbell
Copy link
Contributor

This is a good candidate as we move forward on the search capability. By default, we should not include removed objects in the results, with an option in an Advanced search UI to enable searching for removed objects. Result items should also include a designator when an object has been removed. If we do this, removed objects should also be allowed to be restored via a UI gesture.

In the short-term, I'd argue we should not include removed objects at all in order to avoid confusion as noted, but I'm open to arguments to the contrary.

Agree regarding removed items in search, but we'll need a good way to designate them "deleted". We used to rely on them no longer being reachable in the network graph, but this doesn't work for annotations. One idea to do this:
Have objects that are deleted (like annotations) designated with a deleted boolean attribute. When deleted is present and true, don't index the item.

@scottbell
Copy link
Contributor

@akhenry Thinking about this more, another idea is index all the regular domain objects first (i.e., non-annotations), and then index all the annotations. We could then only index annotations that have "reachable" targets, namely annotations that have an indexed domain object target.

@jvigliotta
Copy link
Contributor

jvigliotta commented Aug 3, 2022

This is related, but possibly moot if we don't show the objects in search. Although, if you know the id, you could still navigate to it. #5603

Seems like there's a bigger issue of just what to do with items that have been removed.

@scottbell
Copy link
Contributor

Orphaned objects should not be returned anymore in search

@khalidadil
Copy link
Contributor

khalidadil commented Aug 4, 2022

I'm still seeing objects that are missing in the tree. I think @jvigliotta did some digging on this.

Edit: It looks like this issue is specific to our banner setup and how we lost/restored some data.

@khalidadil
Copy link
Contributor

When I create an object and then delete it, it no longer shows up in the search. There may be some other search issues, but this seems to be fixed. Verified Fixed in Testathon on 08/04/22

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

No branches or pull requests

6 participants