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

Improvements to the Advanced Search Page #2673

Open
BrittanyBunk opened this issue Nov 29, 2019 · 11 comments
Open

Improvements to the Advanced Search Page #2673

BrittanyBunk opened this issue Nov 29, 2019 · 11 comments
Labels
Lead: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] Priority: 3 Issues that we can consider at our leisure. [managed] Theme: Search Issues related to search UI and backend. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed]

Comments

@BrittanyBunk
Copy link
Contributor

BrittanyBunk commented Nov 29, 2019

Related to #541, #2099.

Now that I use the Advanced Search feature more, I realize it's not adequate enough to look for works/editions. Here's my proposal to add:
image

*I didn't add this one to the picture (ran out of space), but "list" and "OCLC" should be fields too.

I took out some that I felt aren't as important, but it's ok to keep them. I'm hoping these additions will help someone who has some information about a book (but not a lot, and it's not covered in the current Advanced Search layout) to be able to take the multiple bits of limited info that they have to group it together into a search that helps them find what they're looking for. The ones I added in are what I feel would help me out, but if there's something that would help people more, don't feel limited by what I posted - it's ok to add in.

@BrittanyBunk BrittanyBunk added the Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed] label Nov 29, 2019
@xayhewalo xayhewalo added Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] Priority: 3 Issues that we can consider at our leisure. [managed] State: Backlogged Theme: Search Issues related to search UI and backend. [managed] labels Nov 29, 2019
@jessamynwest
Copy link
Collaborator

Speaking as someone who has interacted with a lot of Advanced Search fields in library catalogs, and would like to see one on OL, I think this could benefit more refinement. If you're offering more options for search I think OL people should think more about search strategy generally and about how people look for more information.

Right now, as a counterpoint, the Advanced Search on the Internet Archive basically dissuades people from searching because so much of it is inside baseball for IA superfans. Additionally search results pages are super confusing, limiting only sort of works and there are two kinds of searches (i.e. for a known item and for a general idea that are undifferentiated

We want to offer a good searching experience for users and some of these criterion are a lot more important than others (plus, really big search boxes are more friendly to more users). So, within this example

  • collapse # of pages and pagination into one (with a max/min setting)
  • allow subtitle to be searched within title (no reason not to,most people don't care about the difference)
  • what is search by image supposed to do?
  • needs to differentiate between controlled vocabulary (i.e. author, language) and not (location, publisher) because you can do fuzzy match with non-controlled vocabulary but controlled vocabulary should drop a user into a list
  • is text "full text" here? If not, how does this differ from the current full text search (which right now goes to results from IA and not OL)
  • when people are entering multiple values will the result AND them or OR them (this is crucial, users should be able to choose either which also means limiting to fewer fields so that it doesn't just grind away at server resources)

Many if these can be lumped into a really strong/effective "keyword" search which is how library and database catalogs do it. Or an iterative search strategy where you have a user do a search and then limit the results by the facets that are available.

tl;dr OL needs to have a mapped out Search strategy before getting too deep into building an advanced search.

@BrittanyBunk
Copy link
Contributor Author

BrittanyBunk commented Dec 1, 2019

@jessamynwest Baseball?

  • search by image is when you have an image that looks like the cover, but isn't, and you don't know the name of the book.
  • Yes, full text. It differentiates, because someone can combine another field with the full text together instead of alone. Like combining text with year would help a lot.
  • I don't think we need the iterative (as those are clunky - and I have trouble getting to the info quickly enough. The best is to go back and remove info from the search), just effective keywords.
  • yes, it would need condensing, but I wanted to lay it all out there first before we chisel away at it. I mean all the #'s could just be one box.

@BrittanyBunk
Copy link
Contributor Author

@LeadSongDog I have to scroll down and it takes up space/clutters my view. I don't feel they're really necessary, but if it's there, ok. Some websites take too long to load with them too - plus having them on mobile is even harder.

@BrittanyBunk
Copy link
Contributor Author

@jessamynwest alright, now that @LeadSongDog helped me understand, I could answer properly. It's ok to have an advanced search. Maybe for the IA superfans, we could have a 'see more', so it doesn't dissuade most people, but still allows for the superfans. Google does that and I don't see people searching less than before on there, but probably more than ever. So for that, I think it really helps. A lot of people don't use certain search engines because they're lacking (like Ecosia), so I think it's overall beneficial for everyone for it to be really capable.

@jessamynwest
Copy link
Collaborator

Great -- I am in favor of advanced search in general but it really needs to be part of OL's general strategy because if it doesn't work the way it's supposed it, it will be worse than nothing. Most users aren't advanced searchers. I suggest getting statistics from OL that looks at how many times overall people are using anything but the basic search and what they are looking for, maybe that can help us craft a strategy.

@LeadSongDog
Copy link

@jessamynwest If it is possible to obtain, stats on sequential basic searches (refine and retry attempts) would also be of interest.

@BrittanyBunk
Copy link
Contributor Author

BrittanyBunk commented Dec 5, 2019

@jessamynwest that actually wouldn't be accurate, because if there's something not available on the advanced search, then they won't have stats on it (as people won't use what's not there). The better way is to look at websites that do have stats on it - like search engines like Google - and see how many people use those. Would that help?

@tfmorris
Copy link
Contributor

tfmorris commented Dec 6, 2019

I suggest getting statistics from OL

Data driven decision making? Love it!

@jessamynwest
Copy link
Collaborator

@jessamynwest that actually wouldn't be accurate... The better way is to look at websites that do have stats on it - like search engines like Google - and see how many people use those. Would that help?

I don't think so. Google isn't a library. We need stats from library catalogs because OL has a very specific kind of item which people will look for in a certain way. This is especially true for items with authority control (things like Author names where there is one canonical name in the system in an optimal situation) and Google has nothing like that.

I suggest getting statistics from OL

Data driven decision making? Love it!

I can dream.

@BrittanyBunk
Copy link
Contributor Author

@jessamynwest I'm not stopping you from getting them if that's what you feel will help you. I just don't see how it's going to help me - as it would be misleading for me - so I personally won't - unless you really want me to.

@mekarpeles mekarpeles removed the Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] label Apr 20, 2020
@mekarpeles mekarpeles added Lead: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] and removed Needs: Lead labels Jun 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Lead: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] Priority: 3 Issues that we can consider at our leisure. [managed] Theme: Search Issues related to search UI and backend. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed]
Projects
None yet
Development

No branches or pull requests

7 participants