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

A search endpoint which spans types (e.g. Works, Authors, Subjects) #627

Open
cdrini opened this issue Nov 1, 2017 · 3 comments
Open

A search endpoint which spans types (e.g. Works, Authors, Subjects) #627

cdrini opened this issue Nov 1, 2017 · 3 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

@cdrini
Copy link
Collaborator

cdrini commented Nov 1, 2017

We have a single solr for all our different data types, so why not take advantage of it? This means a user could search for "j k rowling" and get a mix of authors/works(/editions? maybe) back, scored by solr by relevance, rendered differently. This is a little experimental and would be a decent amount of work, but not exceptionally challenging work since a lot of similar code already exists. Candidate for #603 hackathon!

@mekarpeles mekarpeles changed the title Allow for untyped search A search endpoint which spans types (e.g. Works, Authors, Subjects) Nov 1, 2017
@xayhewalo xayhewalo added State: Backlogged 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] Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] labels Oct 24, 2019
@xayhewalo
Copy link
Collaborator

@cdrini @tfmorris This seems like your area of expertise. Are either one of you willing to be assignee? Note, being the assignee doesn't necessarily mean you are responsible for doing the work, just responsible for gathering/providing information to address the issue. From the Wiki.

The assigned owner is not necessarily the person who will fix the issue (it is not necessarily even established, at that point, if or when the issue will be fixed at all), but rather they are the person who will do as much or as little as needed to handle the issue (asking questions, soliciting input, establishing and updating the priority, checking if it is a duplicate, etc).

Once an issue is labeled State: Work In Progress, the owner is the individual doing the work, or leading/coordinating the group that is doing the work.

I've added tags per the issue's context: let me know your thoughts.

@tfmorris
Copy link
Contributor

I think the description is adequate. It's a feature request which is much lower in priority than all the critical bug fixes that are needed, at least from my point of view. Not willing to be the assignee until it bubbles to the top of the priority queue.

@cdrini cdrini self-assigned this Nov 7, 2019
@xayhewalo xayhewalo added the Priority: 3 Issues that we can consider at our leisure. [managed] label Nov 26, 2019
@mekarpeles mekarpeles added the Lead: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] label Dec 18, 2019
@xayhewalo xayhewalo removed the Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] label Dec 24, 2019
@mekarpeles
Copy link
Member

Related to #8740

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

5 participants
@tfmorris @mekarpeles @cdrini @xayhewalo and others