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

Library Home - Free text search within a Library #1165

Closed
jmakowski1123 opened this issue Jul 17, 2024 · 12 comments
Closed

Library Home - Free text search within a Library #1165

jmakowski1123 opened this issue Jul 17, 2024 · 12 comments

Comments

@jmakowski1123
Copy link

jmakowski1123 commented Jul 17, 2024

  • Users can conduct free-text keyword searches within a Library.

  • Result sets are limited to content that lives in the Library.

  • Results are displayed with most relevant by default.

  • Users can refine search results by tag or by content type.

  • Users can sort search results by

a. Title, A-Z
b. Title, Z-A
c. newest
d. oldest
e. recently published
f. recently modified

Image

@kdmccormick kdmccormick transferred this issue from openedx-unsupported/frontend-app-library-authoring Jul 18, 2024
@bradenmacdonald bradenmacdonald moved this from Backlog to Ready for AC testing in Libraries Overhaul Jul 25, 2024
@bradenmacdonald
Copy link
Contributor

@jmakowski1123 This is ready for acceptance testing on the sandbox.

@jmakowski1123
Copy link
Author

Couple things:

  1. Is there supposed to be an exit option out of the search dropdown once all of the tags have been selected as part of the search? Currently, I just click outside of the search box and it auto-closes the box. I can't remember what the parallel experience is in the Studio search, and search seems to be down at the moment so I can't readily check it. @ali-hugo do you remember? Either way, it needs to be the same experience in Studio search and in Library search.
Screen Shot 2024-07-29 at 2 51 28 PM
  1. Results don't seem to be responsive when I type in the free-text search field?
Screen Shot 2024-07-29 at 2 52 09 PM

@ali-hugo
Copy link

ali-hugo commented Jul 30, 2024

@jmakowski1123

Currently, I just click outside of the search box and it auto-closes the box.

This sounds correct to me. After the user selects tags from the dropdown, the "Tags" button should update accordingly (either with the name of the first tag they selected, or with the name of the first tag and the number of additional tags selected). The selections are saved when the user clicks anywhere outside of the dropdown.

I hope that answers your question.

The sandbox doesn't seem to be running anymore, but I did find this video showing the early stages of the UX. Maybe it will help. You can watch from about halfway:

content.tagging.video.mov

@jmakowski1123
Copy link
Author

Thanks @ali-hugo !

@jmakowski1123
Copy link
Author

So @ChrisChV, the outstanding comment on this one is that the free-text typing doesn't produce responsive results. For example, I know that there are two things tagged for "english" here, but when I start typing "english", the results don't show up dynamically

Image

@bradenmacdonald
Copy link
Contributor

@jmakowski1123 The field you're typing in is for finding tags, not for the free-text search. If you type in the free-text search box above, the results are responsive and immediate:

Responsive.Free.Text.Search.mov

@jmakowski1123
Copy link
Author

Right, searching for tags. But in Studio search, searching for tags is also responsive, so I think it's good to be consistent and have the same experience in Libraries?

@bradenmacdonald
Copy link
Contributor

@jmakowski1123 It does work exactly the same way. I think it's hard to tell because there's only one tag applied to items in that library. Try using the Studio search in a course and see how the tag text search works, and it's exactly the same in this library view. We can test this again once we're able to edit the tags and apply more tags.

@jmakowski1123
Copy link
Author

Ok, I added the re-testing label.

@lizc577
Copy link

lizc577 commented Aug 16, 2024

Is it intentional that the recently modified section is not responding to free form text search?

@jmakowski1123
Copy link
Author

Is it intentional that the recently modified section is not responding to free form text search?

@lizc577 I think this point will be rendered mute once the simplified library home page is implemented, right?

@jmakowski1123
Copy link
Author

This is working now with the additions of the tagging feature - shifting to done.

@jmakowski1123 jmakowski1123 moved this from Ready for AC testing to Done in Libraries Overhaul Oct 17, 2024
@jmakowski1123 jmakowski1123 closed this as completed by moving to Done in Libraries Overhaul Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

4 participants