-
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
Explore page #28
Comments
@Grizzly127 - there is a lot of good stuff going on here (I really like the sidebar for all the filtering actions!). But I think it might be easier to have a meeting to go over the details and then chunk up this issue into smaller ones. Afterwards, I would advise to not show both Kompakkt & Semantic Kompakkt solutions in Github going forward, because here we should only be discussing the Kompakkt solutions & then in Gitlab we should have the Semantic Kompakkt solutions, that way we keep the actions for the dev team more clearly defined, but we have the Figma files as source of truth for both teams. |
@Grizzly127 - sorry I didn't have a chance to review yesterday. I think this is already making great progress in terms of visual style, but I suggest we park it for now until we complete the higher priority edits on the Nav & Action toolbars, the Upload process, etc. Would be great to comeback to this in the spring when you're back with the team. I think we still need to address parts of my comments here: #26 (comment) - such as where to add the additional icons (not just remove them). The object "badges" look great, but we still need to think (& test with users) what other actions on top of the object cards would be useful. I also think the 'Options' - Annotable (not an English word) or Annotated, etc. - that are on the side are still not really clear. I think we need to do some more work there on identifying what types of filtering options users can really benefit from. The design is a lot better, but we now need to think on functionality for users. |
Heavily agree. The names of the filter options are too technical and probably do not make sense for users not associated with Kompakkt internals. Just for reference, so we can talk about possible changes to options, here is what they mean:
I could imagine that splitting the options into groups would allow users to make more informed choices. As an example (imagine these as dropdown menus, radio buttons, or a similar input type where only one of the options can be chosen): Category:
Media type:
Annotations:
(with an additional checkbox?)
Access (these are separated on purpose):
This is just an idea though |
@Grizzly127 a lot of good questions! I'll try to list my comments below in order:
Sort by > [Popularity] - There is already a default option chosen here, we don't have a selection description, like we have in "Select media types" for instance. Should we keep it like this, or come up with a description, like "Select display order" ? Filter by > [Select objects or collections] - Here we should maybe include 'Select' for consistency and we could also include institutions as an option? So dropdown shows:
Media types > [Select media types] - this is fine as is Annotation options > [Select annotation options] - Use Select instead of Choose for consistency. I don't think we should add an extra option here, items i can annotate will be visible from my profile page anyway, and it's a bit complicated to explain to users via a single dropdown what's the difference between "Open for annotation" and "Open only to me" - technically everything can be annotated, just depends how it's viewed in the end - i.e. within a collection, or not. Access options > [Select access options] - This is also a bit tricky, what's Private? Private objects are managed better via the profile page. I do think there is a need to filter by license maybe and downloadability. So maybe on Explore we show only public objects anyway, but allow users to filter by License types & downloadability:
(NB: under Open License we can combine all CC license variations)
Items per page: 30 | 1 - 30 of infinity < > Infinity should actually be a number, so "1 - 30 of 175"; and if the number is under 30, it should be "1-15 of 15" (for example), I think that would be simplest, so we only estimate one number for all filters that are applied. |
@Grizzly127 OK, then let's keep it so, indeed sorting is different operation from filtering, so probably fine to be treating it differently with regards to default values.
I think it's fine if we consider institutions to be just a form of collecting, to make it extra clear we could also have the options like so:
I think it's better to keep the title "Filter by" because it's more clear than "Category", first we have sorting and below it we have filters. Also the filter options could change depending on what users select in terms of objects vs collections. For example, collections maybe don't need annotation and access options, because these only work on the object level, not the collection level, or am i wrong @ZetOE? In such cases, we could grey out these options if users filter only for collections. I think it's fine to keep the Search bar as it is because again it makes it more clear that we're searching through both types of content. |
I added "Category" as the title for the "Objects and Collections" filter option, because all other filters have an extra title as well, and "filter by" is the title for all filter options. Theoretically we need both here: I think it looks a bit weird like this. That's why I removed the "Filter by" title and just kept the title for the particular filter options. |
here is a new design for the explore page (in combination with the new navbar #27 and the object display #26 (here we can decide better if pink/orange or blue is better)
Explanation:
Now you can filter the objects on the left side: Categories, Media Types and Options
on the top you can search for a specific object or collection, you can look at your history and you can sort the objects by name, popularity, etc.
I think here is a good place for the buttons to add a new object or collection (maybe also in the user profile where you can see your objects and collections), so I would remove it from the navigation bar.
@HeyItsBATMAN @ZetOE @lozanaross
The text was updated successfully, but these errors were encountered: