You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I understand the logic right, I think whatever is in 'fields' of 'item' is converted to string, cleaned, and all the composing words are returned in an array.
If this is correct (not too sure if I understood correctly though), I don't see the value of allowing item['fields'] to be a dictionary and not simply restricting it to a list.
The text was updated successfully, but these errors were encountered:
@minottic : you are correct. The field "fields" can be a string or a dictionary.
I decided to leave it up to the user how to provide it to the system.
My thinking is that some users (like you) would like to pass in a string (maybe preprocessed in some way or filtered) some others (like me) would like to maintain the structure of the information that is used to score.
The system accept both. I would like to keep it that way, but I understand that it might be confusing when reading the documentation.
If you have any suggestion on how changes that would clarify how it works, please do let me know
If I understand the logic right, I think whatever is in 'fields' of 'item' is converted to string, cleaned, and all the composing words are returned in an array.
panosc-search-scoring/app/ml/preprocessItemsText.py
Lines 96 to 119 in 5d35342
If this is correct (not too sure if I understood correctly though), I don't see the value of allowing item['fields'] to be a dictionary and not simply restricting it to a list.
The text was updated successfully, but these errors were encountered: