This commit is contained in:
2018-09-28 18:58:22 +00:00
parent 1e3ccfcc14
commit fcb61e7ad5
4 changed files with 53 additions and 11 deletions

View File

@@ -35,6 +35,9 @@ REQUIREMENTS
- USE-CASE: Central text search for any match. Can include tags. Can specify a type of object result desired.
- MINIMUM 2 character words only are searchable
- MAXIMUM 255 character words only are indexed (cut off at 255 if longer)
- ? USE-CASE: In-object text search for the typeandid that user is in, e.g. when in Client info form can search on that client.
- This is problematic because it seems to require searching for related objects but that's deprecated to priority 2
- Maybe more ideally is a search that can be something like "search all workorders FOR THIS CLIENT" or search all units "FOR THIS CLIENT"
@@ -68,7 +71,6 @@ REQUIREMENTS
- Coding: break this into separate discrete classes, the old v7 code is very monolithic and in-elegant
//TODO:
- SAMPLE DATA: Need a huge amount of sample data indexed to load test it
- INDEXES: play with it and see what works best

View File

@@ -29,11 +29,8 @@ IMMEDIATE ITEMS:
================
- Search and search text indexing
- Create a test for search that searches the widgets LOREM text
- Test with huge dataset for performance testing
- Need to be able to specify max results, code that shit!
- bugbug: why is the single letter a being indexed? Missing shortness filter, A not in stopwords for english??
- Search and search text indexing
- Can it be sped up with huge data test??
- Update all the other routes to include search indexing (attachments, tags etc, anything with text in it)