-
Notifications
You must be signed in to change notification settings - Fork 2
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
Filter options explore page/insitutional page #54
Comments
I strongly prefer the route of users always being able to press the annotate button. When they press it, they get a list of collections.
If this does not fit into a list, it might make sense to create this as a modal/dialog instead. ExampleCollection: Foo
Collection: Bar
Collection: Baz
|
objects/collections/institutionsWe thought about filtering between objects, collections and institutions: I thought about reorganizing it on the users/institutional profile more like on sketchfab/pinterest/instagram (other platforms with collections): On the explore page we could make searching for users/institutions at the explore page could look like this: |
@HeyItsBATMAN |
Here are my first ideas:
![]() ![]() Let me know if this makes sense to you and what can be improved. |
Annotation options
We thought about filtering the objects after annotation options:

We got the feedback from users that it is a bit confusing and maybe not even a use case.
Users can always annotate objects in their collections.
The information if it is already annotated is not something that the user would look for, it is more an information that is displayed looking at the object. Therefore I suggest removing this as a filter option.
What is sometimes not clear to the user is that objects can only be annotated if they are in a collection, therefore we should address this more clearly.

We could directly show the users collections here. The button is blue, because the user is able to annotate, but only needs to add the object to a collection.
Right now the tooltip for objects that are not annotable only says:

We should make it more clear why the user is not able to annotate and maybe add (or something else, I am not sure how it is organized right now):

@lozanaross @ZetOE @HeyItsBATMAN
The text was updated successfully, but these errors were encountered: