Re: [WebERP-developers] Script changes to enhance inventory description search regardless of keyword order

[Phil D. <ph...@lo...>]

You may need to sit Tim ... I agree with 1 and 3 completely!

If we could pass a series of parameters for the search and return a 
recordset then it could be possible to make it into an 
SQL_CommonFunctions.inc function that we could re-use everywhere. I even 
though so at the time I made some of the later scripts realising I was 
duplicating work with cut and paste, I just never got around to it. I 
would hate to add too much complexity to item searches but it would be 
wonderful to have them all consistent and using the same code - removing 
a chunk out of all those scripts Debi has highlighted.

Phil

Phil Daintree
Logic Works Ltd - +64 (0)275 567890
http://www.logicworks.co.nz

On 22/11/11 21:17, Tim Schofield wrote:
> Hi Debi,
>
> I really like the idea of expanding on the search methods. A few thoughts:
>
> 1 Could we follow the search engine method by allowing boolean
> operators in the search, and aggregating phrases such as
>
> "9/16 Hex" PS
>
> for a search string?
>
> 2 I have wanted for a long time to implement a soundex
> (http://en.wikipedia.org/wiki/Soundex) algorithm into our search. A
> lot of our users in warehouses tend to type in descriptions
> phonetically, and it would be really great to have it. I'm sure I
> found some PHP implementations of it before.
>
> 3 I know Phil will hate this, but can't we take the item search
> facility out into a separate function so that it can be reused
> identically throughout webERP? As Debi points out a change to the
> search algorithm affects so many parts of webERP and we now have a
> situation where the implementations of item search are not consistent.
>
> Thanks
> Tim
>
>
> On 22 November 2011 01:39, DebiCates<deb...@ya...>  wrote:
>> Klaus, now that you mention it, I can envision the possible unexpected
>> headache this change might cause for current users. It would be best
>> included as an option.
>>
>> For example, two parts with descriptions
>> 5/16 HEX SL PS SCREW 9/16 SS BAND
>> 9/16 HEX SL PS SCREW 3/32 SS BAND
>>
>> Under the current search query, the user could rely that entering 9/16 SCREW
>> will find only the second item. With my change, of course it finds both. For
>> us, the limitation of keyword order (often netting NO results) was more
>> frustrating than too many. I figured there might be others with the same
>> issue.
>>
>> It would be nice to devise a solution that would accommodate both types of
>> search. Perhaps entering *9/16 SCREW* could signify an in-order search like
>> it works now. A literal search signifier would be undoubtedly expected then,
>> too. And a NOT signifier too. Then allowing the user to mix them up in one
>> search would be an interesting challenge. Like,
>>
>> *9/16 SCREW* "SS BAND" #SL# PS
>>
>> And it would be even better to use a table to dictate the characters used
>> for each type of search signifier. Oh, and lastly to include instructions in
>> the manual! ;)
>>
>> This is something I might commit to do. Any other thoughts out there?
>>
>>
>>
>> --
>> View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Script-changes-to-enhance-inventory-description-search-regardless-of-keyword-order-tp4091940p4094151.html
>> Sent from the web-ERP-developers mailing list archive at Nabble.com.
>>
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure
>> contains a definitive record of customers, application performance,
>> security threats, fraudulent activity, and more. Splunk takes this
>> data and makes sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-novd2d
>> _______________________________________________
>> Web-erp-developers mailing list
>> Web...@li...
>> https://lists.sourceforge.net/lists/listinfo/web-erp-developers
>>
>
>
>