As shown below, FTS search result lists IC/0274/01 without paragraph numbers. Once users click on "Full Case & Analysis," relevant paragraph numbers display. It should be displayed in the FTS result.
Hi
Piyush
, I checked this document and paragraphs. I don't see a case where "challenge" and "nationality" appear in the same paragraph. That's why you don't get paragraphs back.
Notified 4 people
Harsh Parikh,Tech Lead
Hi
Radomir
,
As per video by
Paul
, The parapgh is not listing for particular one document. if the keyword is not matching then why document is coming through API without Paragraph number.
Please see above
Paul
video the word is highlighted in html document's paragraph. but those paragraph of same document is not fetched in FTS.
Cc :
Martin
Notified 4 people
Radomir Mladenovic
Harsh
because document it self matches, probably having the keywords in paragraphs close to each other, but not in the same paragraph. I saw the video but, what's asked for, to return paragraphs 119 and 120, is not doable because paragraphs are indexed separately. If you prefer, we could return paragraphs containing ANY keyword used in the proximity query. That may result in many paragraphs returned where one keyword appears but totally unrelated to the other one - so you get a lot of noise.
Notified 4 people
Paul Moon
Hi
Martin
:
We need to discuss how we can address this type of full text search result, as it will be problematic for other full text search. What
Radomir
is suggesting above does not sound ideal to me, as it does not sound very accurate. Let me know when you can discuss this.
As shown below, FTS search result lists IC/0274/01 without paragraph numbers. Once users click on "Full Case & Analysis," relevant paragraph numbers display. It should be displayed in the FTS result.
Please add to this sprint's unplanned.
Thanks,
Paul
I have added https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1577 to the current sprint.
Thanks,
-Martin
Please looking the above issue. Please find below the document HTML file.
Gambrinus Corporation v. Bolivarian Republic of Venezuela, ICSID Case No. ARB/11/31, Award, 15 June 2015
File:
Request Body:
{
"searchRequest":"challenge w/10 nationality",
"FilterStatement":{
"type":"boolean",
"Operator":"and",
"clauses":[
{
"type":"boolean",
"Operator":"or",
"clauses":[
{
"type":"boolean",
"Operator":"and",
"clauses":[
{
"type":"match",
"field":"DocumentContentTypeId",
"values":[
"13"
]
}
]
},
{
"type":"boolean",
"Operator":"and",
"clauses":[
{
"type":"match",
"field":"DocumentContentTypeId",
"values":[
"37"
]
},
{
"type":"match",
"field":"Field_DocumentTypeId",
"values":[
"1080",
"1078",
"1074",
"1071",
"1070",
"1068",
"1066"
]
}
]
},
{
"type":"boolean",
"Operator":"and",
"clauses":[
{
"type":"match",
"field":"DocumentContentTypeId",
"values":[
"12"
]
}
]
}
]
}
]
},
"SearchType":"Boolean",
"Stemming":true,
"Synonyms":false,
"Fuzzy":true,
"Fuzziness":"1",
"SortField":"hits",
"SortOrder":"desc",
"PageNum":0,
"PageSize":"20"
}
cc:
"challenge" and "nationality" appear in the same paragraph. That's why you don't get paragraphs back.
As per video by
Please see above
Cc :
I saw the video but, what's asked for, to return paragraphs 119 and 120, is not doable because paragraphs are indexed separately. If you prefer, we could return paragraphs containing ANY keyword used in the proximity query. That may result in many paragraphs returned where one keyword appears but totally unrelated to the other one - so you get a lot of noise.
We need to discuss how we can address this type of full text search result, as it will be problematic for other full text search. What
Thanks,
Paul
I think your suggestion might be our best approach.
Thanks,
-Martin
Here is the attached html document which I got from server. Also, I checked and found that there is no tagging data added for this UIN in database.
I see DevOps 1615 is a research item, but do we need a separate item to incorporate an interim solution below?
Thanks,
Paul
We have set "Click on Full Case & Analysis" link while there is no paragraph list on app.islg and staging. islg. Please check and confirm.
https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1577
cc:
Paul