Task #752 (closed)
Implement standalone lucene search
| Reported by: | jamoore | Owned by: | w.moore@… |
|---|---|---|---|
| Priority: | minor | Milestone: | 3.0-Beta3.1 |
| Component: | Search | Version: | 3.0-Beta1 |
| Keywords: | n.a. | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
As a starting point for Lucene-based search, it's important to get a feeling for what fields/columns should be included in the index.
See Search tickets for more information.
As discussed on OMERO Day
Change History (3)
comment:1 Changed 16 years ago by cxallan
- Milestone changed from 3.0-Beta3 to 3.0-Beta3.1
comment:2 Changed 16 years ago by wmoore
- Resolution set to fixed
- Status changed from new to closed
comment:3 Changed 16 years ago by wmoore
This has been implemented since Beta3.0 in OMERO.editor.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
XML files have been indexed using standard Lucene tokenizer and analyzer, which seems to work pretty well for key-word searching.
XML structure and punctuation is ignored when building Lucene index, as expected for a free-text search.