User Story #46 (closed)
Opened 18 years ago
Closed 14 years ago
Provided search functionality should be keyed to user's ability/context.
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | Search | Keywords: | n.a. |
| Cc: | jburel | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Whether a user receives a Lucene search box or a HQL search box should be configurable, and possibly based on the user's roles.
Change History (4)
comment:1 Changed 18 years ago by jmoore
- Type changed from defect to User Story
comment:2 Changed 18 years ago by sfrank
comment:3 Changed 17 years ago by jmoore
- Owner changed from sfrank to jmoore
comment:4 Changed 14 years ago by jmoore
- Cc jburel added
- Resolution set to fixed
- Status changed from new to closed
Jean-Marie, this is ticket from early in the search days. I'm closing it, but there may be some value in the text, so I'm CC'ing you. Feel free to re-open.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Can you rephrase that requirement in a way that the user understands (Which is a formulation for: Let the Usability-Guy come up with an idea of how to present this to the user.) We should differentiate between two things:
Or do we need both query modes, to support different use-cases for search. This discussion is a bit theoretical: We should come up with some concrete examples what people are looking for and what's their way to find it. Maybe start with a simplistic gui (a textbox to enter a search-phrase, maybe some checkboxes to limit your results to certain objects like image, dataset, instrument etc.) - and see how far we can get with that.